Files not being marked dirty with changes

[Bruce Richardson]

Dear Mike,

Thanks for the emails as I was getting signed up and licensed. Much appreciated.

I'm in tech on my first show on SCS. Things are going well, but I've noticed some bugs/issues that I'll post to separate topics.

This one regards making changes to the cue list, or to cues within it, and not being given the opportunity to save. In other words, I make a change, and the "save" command remains greyed out. Some changes do not appear to be marking the file "dirty."

I'm not remembering exact specifics. Some fades, renaming fade cues, etc., to my memory, but even some fairly substantial operations. My workaround has been to add and delete an audio cue. That usually manages to trigger the file dirty, and allow me to save.

Best regards,
Bruce

[Mike Daniell]

Bruce,

I did find an issue like this pre-10.3.0. What I found was that if you changed a field (enabling the Save button), saved your changes (disabling the Save button) and then made another change to the same field, then the Save button was not re-enabled until some other field was changed. This was fixed in 10.3.0, so could you check the version you are using? The version number is displayed on the splash screen when you start SCS, and can also be seen under Help / About.

If you are not using the latest version (10.3.2) please download and install that. Then if you still find situations where the Save button is not enabled when you have made a change, please let me know which field(s) can cause this.

Note that with some numeric fields it is necessary to tab out of the field (or just click on another field) for SCS to check for a change and validate the new value.

[Bruce Richardson]

Hi Mike,

It was 10.3.1. I will probably not update the running show machine until the show is down (3 weeks from Saturday), but I will be building another show in the studio, so I'll update there and pay close attention to the situations.

B.