Hi Mike,
I've attached my showfile where the timing of call cues does not work as expected. The show includes two callable cues (P10 & P20) which open / close a curtain. The curtains motor is switched on and 9 seconds later it is switched off, because 9 seconds is the time it needs to close or open the curtain.
In Q20 the cue for closing the curtain is called and a sub cue shall turn on the worklights when the curtain is closed.
But although my setting in the subcue is that it shall be called after end of the previous sub cue, the light is turned on, before the curtain is fully closed. So the 9 seconds within the callable cue P10 isn't considered.
You can also see it in the cue panel, that the curtain cue P10 is immediately finished without lasting at least 9 seconds.
Everything tested with the latest version (11.8.1.2 x64)
Best regards,
Dieter
[Fix 11.8.2] Cue timing does not work as expected
[Fix 11.8.2] Cue timing does not work as expected
- Attachments
-
- Theater.zip
- (6.43 KiB) Downloaded 105 times
-
- Site Admin
- Posts: 3629
- Joined: Sun Jul 24, 2005 8:58 am
- Location: Brisbane, Queensland, Australia. TZ:GMT+10
- Contact:
Re: Cue timing does not work as expected
Dieter,
I've just run a test here using your cue file and pressing '8' to activate a hot key, and the required 9-second delay was applied. Maybe I'm not following exactly what you describe. A log file will have been created and saved in a folder named "SCS Logs" under "Documents", and the name of the file includes a time-stamp indicating when the log started. Please email me the log file from a run in which the work lights came on too soon, and tell me how you activated the relevant cue.
I've just run a test here using your cue file and pressing '8' to activate a hot key, and the required 9-second delay was applied. Maybe I'm not following exactly what you describe. A log file will have been created and saved in a folder named "SCS Logs" under "Documents", and the name of the file includes a time-stamp indicating when the log started. Please email me the log file from a run in which the work lights came on too soon, and tell me how you activated the relevant cue.
Re: Cue timing does not work as expected
Hi Mike,
Nothing wrong with the "curtain close cue" itself you are calling with hotkey 8.
My problem is when Q20 is activated with GO.
There it should call:
LS80 - Blackout Cue
P10 - Close Curtain Cue (after end of LS80) <- this needs at least 9 seconds to be finished!!!
LS70 - Worklight Cue (after end of P10)
as P10 consists of two cues where the last one is executed 9 seconds after the first, LS70 should not be fired before at least 9 seconds have passed...
Now LS70 is immediately fired after P10 has been called and does not wait for P10 to be finished.
Find the log file attached.
Nothing wrong with the "curtain close cue" itself you are calling with hotkey 8.
My problem is when Q20 is activated with GO.
There it should call:
LS80 - Blackout Cue
P10 - Close Curtain Cue (after end of LS80) <- this needs at least 9 seconds to be finished!!!
LS70 - Worklight Cue (after end of P10)
as P10 consists of two cues where the last one is executed 9 seconds after the first, LS70 should not be fired before at least 9 seconds have passed...
Now LS70 is immediately fired after P10 has been called and does not wait for P10 to be finished.
Find the log file attached.
- Attachments
-
- scs11_log_20190726_093054.zip
- (68.97 KiB) Downloaded 92 times
-
- Site Admin
- Posts: 3629
- Joined: Sun Jul 24, 2005 8:58 am
- Location: Brisbane, Queensland, Australia. TZ:GMT+10
- Contact:
Re: Cue timing does not work as expected
Thanks for the log and extra info, Dieter. I've found the bug and will email you details of a fixed version.
Re: Cue timing does not work as expected
Hi Mike!
That looks excellent with the version you provided!
Thanks for the quick fix!
Best regards,
Dieter
That looks excellent with the version you provided!
Thanks for the quick fix!
Best regards,
Dieter