New and Changed Features in SCS 11.10.6
- The testing of a Level Change Cue in the Editor has been simplified. This includes the removal of the 'Play at Required New Level and Pan' checkbox as this is no longer deemed useful.
- The DMX Display window has been optimized by removing the options to hide the grid lines and to change the background color. This enables you to reduce the width of the DMX Display window, which is especially useful when viewing fixture values.
- Lighting Cues using 'DMX Items' as the Entry Type were not applying selected fade times.
- Activating 'Stop All' (eg by pressing Esc) twice may 'Complete' Video/Image or Playlist sub-cues that are currently 'Not Loaded'.
- In Production Properties / Lighting Devices, the combo-boxes of Fixture Types were not reloaded if another SCS Cue File (.scs11 file) was opened in the same session.
- Inserting a new Fixture in a Lighting Device in Production Properties could cause a memory error when applying the device change.
- If a Level Change sub-cue is adjusting the audio level of the target sub-cue, and then a second Level Change sub-cue for that same target sub-cue is activated, then the two Level Change sub-cues would compete. The latter Level Change sub-cue now takes control.
- In Options / Remote App Interface, if you click on 'IP Info' then the 'IP Info' window would omit displaying the final or only IPv4 entry, which typically resulted in the window being blank.
- If a Time Based Cue (TBC) did not have a start time set for every time profile then changing the start time for an entry could cause a duplicated entry and the new time to be ignored.
- If a TBC has other cues set to auto-start directly or indirectly after the TBC then these auto-start cues would not be marked as Complete if at the time of starting SCS the TBC was immediately marker as Complete as its start time had already expired. A related but opposite condition also occurred if the TBC time was reset in the editor to a future time.
- On starting a cue, the next manual cue to be started (as displayed in the GO button) could then incorrectly point to an earlier cue.
- If a Cue Control Device was set to MIDI and a fader control (eg Master Fader) was set to respond to MIDI pitch bend messages, then the LSB field should have been omitted from the display as this will contain the runtime value for the fader. The pitch bend message is sent by some remote devices such as the PreSonus ioSTATION24c.
- When 'Stop All' is activated, eg by pressing ESC, then stopping and resetting cues would ignore disabled cues. However, it is possible that a cue was started and then made disabled whilst still running. 'Stop All' now stops and resets all running cues, regardless of their current enabled state.
- Audio file sub-cues with short fade-in times could sometimes not fade in smoothly.
