SCS 11.8.1 Available
Posted: Tue May 28, 2019 12:10 pm
SCS 11.8.1 is now available on the Download page of the Member Area.
New and Changed Features in SCS 11.8.1
New and Changed Features in SCS 11.8.1
- Time-Based Cues (TBC's) may now have a 'latest time' set, which is useful for TBC's such as pre-show music if you start SCS after the 'time of day' you specified for the cue.
- When creating or editing a Control Send Cue that sends commands to a Behringer X32 Digital or Compact Mixer there is now a 'Capture X32 Info' button available that enables you to set up the Control Send cue as a snapshot of current Mute settings, eg the Mute settings for selected channels.
- The maximum number of messages that may be included in a single Control Send Cue has been increased from 16 to 32.
- In Production Properties - Control Send Devices - Network, the default inter-message delay was previously 100ms. If the Network Protocol is UDP the default inter-message delay is now 0ms (no delay) as UDP preserves message boundaries whereas TCP/Telnet does not.
- Memo Cues directed to the primary screen may now, via a new Production Property, be displayed in one of three ways: (1) in a pop-up window, as in previous version; (2) in a panel to the right of the cue list; (3) in a panel to the right of both the cue list and the cue panels. The new Production Property will apply to all Memo Cues that are directed to the primary screen. The Memo Panels in options (2) and (3) are resizable, as is the pop-up window of option (1).
- When saving a cue file, SCS now detects if the file has been changed by another application since it was opened or last updated by SCS. If the file has been changed, you may choose to overwrite the changed cue file, save as a new cue file, or cancel the operation.
- With some audio interfaces, such as the Presonus Audiobox, initialization can take several seconds per channel when determining WASAPI availability. There is now a new audio driver option in SCS: 'Do NOT use WASAPI' with the tooltip hint 'If you do not need to use WASAPI (eg to access all available speakers) then setting this option can significantly reduce device initialization time'.
- The warning message 'SCS main window currently does not have focus' now flashes once a second.
- The test for 'SCS main window currently does not have focus' is not, by default, active when the Editor is open, but there is now an Editing Option to enable you to override this. This may be useful if you may have the Editor open during rehearsals or live runs.
- When 'Pause All' is active, a warning message will be flashed in the status bar. This is because 'Pause All' not only pauses playing cues, but also pauses any active auto-start countdown timers. This could have unexpected consequences if 'Pause All' is not canceled. 'Pause All' will be canceled by 'Resume All' or 'Stop All'.
- Saved window positions, sizes and splitter bar settings are now saved separately for different display configurations, eg separately for having one screen or two screens connected. This test also takes into consideration display scaling and sizes.
- When editing an Audio File Cue, clicking and dragging a marker on the graph (eg the fade-in marker) no longer auto-changes the selected combobox item that controls what is displayed in the 'Audio Devices' etc panel.
- When selecting a Lighting Cue in the Editor, SCS could take a few seconds to display the Cue due to the time taken to populate the Fixture combo boxes. This process is now only performed if necessary, so the first Lighting Cue you display in the Editor may still take a few seconds to display, but subsequent Lighting Cues selected should display much faster.
- A cue set to auto-start after load may not start if the loading processing takes too long.
- When determining if audio file cues can be played gapless, if an audio file cue contained a looping cue then in gapless mode that could freeze. Audio file cues with loops are now excluded from the gapless test.
- In Production Properties / Devices, when viewing or editing the Control Send or Cue Control devices, and then opening a different cue file and viewing those same device tabs, then the device selection from the first cue file will not have been cleared. For example, if the first cue file used a DMX Cue Control device but the second cue file used a MIDI Cue Control device, then when viewing this second file the DMX Cue Control device settings will not have been cleared.
- When stopping an audio file cue in the editor, resetting the cue position to the start was not handled correctly if the BASS mixer was selected in the Audio Driver Options.
- If the next cue in the main window's cue list is an auto-start cue and the user uses the down-arrow to navigate to this cue then that cue should have had it's 'activation method required' changed to manual start. This is the behavior that already occurs if the user clicks on that next cue.
- If a video/image cue has a fade-in time and after the cue has completed, if the user then uses the up-arrow to navigate back to the cue and then plays it again, the fade-in may not occur.
- When using multiple screens, sometimes the screen numbers detected by the underlying software are not consistent across SCS sessions. This can be due to the order in which external screens (or projectors) are connected. A fix is now included which always orders the screens according to their position (left-to-right, top-to-bottom), apart from the primary screen which is always 'screen 1' regardless of it's relative position.
- A memory error could occur when trying to display the cue panel for a Playlist Cue set up as a placeholder.
- The facility to lock or unlock editing and options changes, which is accessed from the Options window, would hang SCS if the Options window was opened from the Load Production window prior to the main window being opened, eg prior to opening a cue file.
- When editing a Memo Cue, the color selector was not being initialized with the color of the selected item. For example, if you used 'set text color' for text that was currently red, then the color selector was not initialized at red unless that also happened to be the last color selected.
- In Display Options, if the Video Monitor Size was changed then this did not take immediate effect.
- If a cue is set to auto-start 'on cue marker' and the position of the cue marker is changed in the editor, then this position change was not immediately applied to the auto-start cue(s), or to the relevant displayed info for those cues in the main window.
- In Production Properties / Lighting Devices, if you entered a DMX Start Channel on an empty Fixture row, the program would crash.
- In Production Properties / Video Capture Devices, the 'delete', 'move up' and 'move down' buttons did not work properly.
- In Production Properties 'Undo Devices Changes' did not handle video audio or video capture devices.
- With gapless audio streams, if you navigate back through the cue list after the stream had completed, the gapless stream would not be correctly reset, which could result in cues in the stream not playing.
- If you used 'Stop All' (eg Esc) while a gapless stream was playing the second or a later file in the stream, the gapless stream would not be correctly reset, which could result in cues in the stream not playing.
- Continuous Production Property Device tests (eg Test Video Capture) are now canceled if you navigate away from the device properties.
- Various other fixes for Video Capture Devices in Production Properties.
- If a Playlist is being resumed from hibernation and if the next track is to be faded in then a brief burst of sound at the designated level may have been heard before the fade-in starts.
- When a sub-cue is played in the editor, then when it completes any other sub-cues set to auto-start after the end of that sub-cue may be auto-started. This shouldn't have happened for sub-cues started in the editor.
- If the Remote App Interface in SCS is used for controlling SCS from a device other than the official SCSRemote app, and if the Network Protocol is set to UDP, then SCS would crash on trying to echo data to the device.
- If a cue is set to auto-start based on a relative time setting (eg 3 seconds after the start of the previous cue) and this auto-start is subsequently changed to use 'on cue marker', then the cue may be shown as 'complete' immediately the controlling cue is started.
- A Lighting Cue created using a version of SCS pre-11.8.0 would have had any item-specific fade time ignored if the channel was not a dimmable channel, eg items like "L6:13@36f3 // tilt" didn't apply the 3-second fade.
- On "un-maximizing" the SCS main window, the program would crash if the calculated width of the cue panel's progress sliders is negative, which could occur if the calculated slider's label widths are too wide. SCS now suppresses the right or both the left and right labels if necessary to avoid this condition.
- Cue list positions on primary and backup computers can get out-of-sync if a double-click or equivalent occurs on the primary.
- Improved performance of network control send cues.
- In Live Input cues, only the first 8 live input channels were available for SCS Professional users.
- Deleting a Live Input device did not check if the device was included in an Input Group.
- Memo Cues displayed to a panel on the main window could hang SCS on closing the sub-cue.
- If a production contains Video/Image Cues where some output screen numbers are skipped (eg if all Video/Image Cues use Screen 3, meaning Screen 2 is skipped) then previously the 'skipped' screens would be blacked out. That is now fixed, so only the output screens required by the production will be used.
- Fixed some issues related to changes made to Audio Output Device assignments off-site, eg changing a device from stereo to mono on your theatre computer and then just transferring the cue file (the .scs11 file) back to your home computer.