three bug conditions confirmed (#3 fixed in 10.4.0)

[Bruce Richardson]

Hi Mike,

Three bug conditions I reported earlier are confirmed on another machine now.

1) SCS (10.3.2) will occasionally enter a state where it ceases "dirtying" the file for save. I notice this when changing the parameters in existing audio subcues, mostly, although it is not limited to this. Closing SCS and restarting it resolves the problem. More often than not, closing SCS when it has entered this state results in a crash dialog from Windows (XP pro).

2) After editing and saving a cue containing multiple subcues with delays, and returning to the playlist, the delayed portions of the cue do not trigger--unless one either double selects the cue or selects another cue then reselects. The playlist does not seem to be dynamically updating.

3) Playlists will enter a state (more often than not) where I can only assign two discrete output dropdowns. The rest remain greyed out. Closing and reopening does not generally solve this. I literally just open the playlist now and then, and when it is NOT misbehaving, I assign more outputs.

I have the top-tier license. If you are aware of any workaround for the latter issue, it would be of great value to me. I will seek one as well, and report back if I find it.

Best regards,
Bruce

[Mike Daniell]

1) SCS (10.3.2) will occasionally enter a state where it ceases "dirtying" the file for save. I notice this when changing the parameters in existing audio subcues, mostly, although it is not limited to this.

Bruce, next time this happens, could you tell me what properties you change do not "dirty" the file for save? I've probably mentioned this before, but with numeric fields such as fade times, you will need to tab or click out of the field before SCS will validate the change.

I'll try to reproduce the other two issues.

[Bruce Richardson]

Hi Mike,

Usually fade times, etc. Once the file is in this state, the only way to return it to proper function is to close SCS and reopen.

I'll try to pay attention. I'm in tech, so, it's both good and bad for bug reporting, as you know...

B.

[Mike Daniell]

3) Playlists will enter a state (more often than not) where I can only assign two discrete output dropdowns. The rest remain greyed out.

Found the cause of this. Fix ready for the next release.

[Mike Daniell]

2) After editing and saving a cue containing multiple subcues with delays, and returning to the playlist, the delayed portions of the cue do not trigger--unless one either double selects the cue or selects another cue then reselects. The playlist does not seem to be dynamically updating.

Not having any luck(?) in reproducing this error, Bruce. I set up a cue with 8 sub-cues with various relative start times. 7 of the sub-cues were audio files and one of them was a level change. I then closed the editor, hit the Go button on the Run Screen, and the whole cue played as specified. It also works OK if I leave the Editor open and just switch back to the Run Screen and start the cue. Finally, I re-entered the Editor, changed the relative start time of one sub-cue, saved the change and returned to the Run Screen. The changed relative start-time took effect as specified without having to select the cue or anything like that.

When a cue is started using the 'Go' button or equivalent, all the sub-cues in that cue should either start immediately or be set to a count-down state. So if you have 'show sub-cues in cue panels' turned on in the Display Options, what do you see as that state of the sub-cues of the cue you start? Have you found a scenario that will definitely cause delayed start sub-cues not to start when they should?