I have just finished my first show with SCS - it was the most complex sound plot I have ever done with over 200 cues, 7 output channels and many simultaneous actions. SCS coped with everything I threw at it and did everything I needed it to. I am generally very impressed.
I ran a backup on a 1GB memory stick (the files wouldnlt fit on a CD) and swapped easily between my laptop for off-site editing and the Theatre PC for performances and rehearsals. This all worked really well.
I had a couple of minor issues: In edit mode, the software doesn't recognise the use of the 'return' key to say ' i've finished changing this value - please accept it'. I have to click on another field, and sometimes the software doesn't recognise that a value has changed and enable the 'save changes' button. I had this quite a few times when editing and tweaking in rehearsals.
I also got occasional error windows (will try and re-create them and post the errors) when editing. They sometimes came up 2 or 3 times when 'ok'd and went away, but no actual problems seemed to occur.
The fade/level adjustment bar does seem to do very little at the 'top' end, and drop off the cliff at the bottom end. This makes fine adjustments of quiet cues tricky.
I look forward to further feature enhancements of this really great software.
Keep up the good work.
Comments after first show
Re: Comments after first show
I imagine you get a 'beep' to indicate that it is not an acceptable key. I have found that the most reliable way to get the change recognised is to Tab away from the field.I had a couple of minor issues: In edit mode, the software doesn't recognise the use of the 'return' key to say ' i've finished changing this value - please accept it'. I have to click on another field, and sometimes the software doesn't recognise that a value has changed and enable the 'save changes' button. I had this quite a few times when editing and tweaking in rehearsals.
Mike will certainly find those helpful.I also got occasional error windows (will try and re-create them and post the errors) when editing. They sometimes came up 2 or 3 times when 'ok'd and went away, but no actual problems seemed to occur.
This is a known issue. See this thread.The fade/level adjustment bar does seem to do very little at the 'top' end, and drop off the cliff at the bottom end. This makes fine adjustments of quiet cues tricky.
Malcolm
-
- Site Admin
- Posts: 3629
- Joined: Sun Jul 24, 2005 8:58 am
- Location: Brisbane, Queensland, Australia. TZ:GMT+10
- Contact:
Thanks, Malcolm, for your responses. Just a few more comments:
This has been brought up before but the issue is one of which 'standard' to follow. The 'standard' I am following is that a window may have a default button and a cancel button. The default button is activated if you hit Return, and the cancel button is activated if you hit Escape. Thus the Return key doesn't just mean I've finished changing this value, it also means I've finished with this window. The Tab key is what this 'standard' uses for stepping thru the fields. The Options window in SCS, for example, has an OK button defined as the default button and a Cancel button defined as the cancel button. The Editor doesn't have either a default button or a cancel button.In edit mode, the software doesn't recognise the use of the 'return' key to say ' i've finished changing this value - please accept it'.
I am looking into changes in this area. In 9.4 there will be a trim control which can give you more of the fader to play with on low-level cues. For SCS 10 the fader has been completely re-calibrated and re-scaled, as well as retaining the new trim control.The fade/level adjustment bar does seem to do very little at the 'top' end, and drop off the cliff at the bottom end. This makes fine adjustments of quiet cues tricky.