Negative fade times
Posted 29 May 2012 - 07:34 PM
We have an ORB XF with Zeros 7.3 (although this also occured at previous versions). We run the desk in none tracking mode and the default fade time is set to 3 second.
If we record a cue using "[Record] [Cue] n [Snapshot] [Enter]" then it correctly records the cue with the default 3 second fade. This is the way I usually record cues in order to include any submasters that are active.
If we specify that we want to use the default time "[Record] [Cue] n [Default times] [Enter]" then it also works correctly.
However, if we record a cue using "[Record] [Cue] n [Enter]" then it records the fade time as 3- and the cue executes as a snap.
Strangely, on switching the desk to tracking mode I find that "[Record] [Cue] n [Snapshot] [Enter]" and "[Record] [Cue] n [Enter]" work. And it is the "[Record] [Cue] n [Default times] [Enter]" syntax that produces the 3- fade times!
Any ideas as to what is going on?
Posted 30 May 2012 - 11:48 AM
I hope this helps,
Product Manager, Entertainment Lighting Controls
JonHole@Eaton.com | www.zero88.com | www.eaton.com
Usk House, Llantarnam Park, Cwmbran, NP44 3HD, UK
Tel: +44 (0)1633 838088 | Mobile: +44 (0)7734 736690 | Fax: +44 (0)1633 867880
Posted 30 May 2012 - 12:53 PM
However last night I recorded six or seven consecutive cues all of which were blackouts (hence no changes between cues) and some had the '-' and some didn't depending on the syntax used to record the cue.
I'm also sure we have in the past had cues that were definately not the same where the second one had a '-' and acted as a snap fade. Editing the fade times manually from '3-' to just '3' resulted in the fade working properly. Unfortunately I'm not at the theatre at the moment so I can't try to recreate that scenario. Next time I'm over there I'll see if I can test this out.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users