• State Verified Answer
  • Date
    MB-C
  • Date
  • Replies 4 replies
  • Subscribers 184 subscribers
  • Views 3429 views
  • Users 0 members are here

GIO loop cues sneaking manual/Int Palette

Hello all,

our theatre has had a Gio for about 4 months now, and one thing that we have only just noticed which we would like explained to us if anyone would be kind enough to, is this:

When we create a looped cue why does it sneak out manual changes or palettes when it returns to the top of the loop?

Our "for example" is that we had h/lights in and out using an IP on a macro that was active over a few looped cues for a presentation, which needed to dim and light for a projection hence the looped cues, and then have H/Ls up for questions. To solve it for the event we just put H/L on a fader but when testing we found that regardless of whether it was looping from cue 3 back to 2 or 2 back to 1 it would sneak out the IP or manual settings but it would keep the IP or manual change in from 1 to 2 or 2 to 3.

Any explanations would be great.

cheers,

M

Parents
  • 0

    Do you have a level for your house lights stored in cue 1? If you have set manual values for channels and the units are not either selected or captured they will return to the level stored in a cue when it is run. When you're moving forward through your cue list they are not getting a move instruction, but my guess is your cue 1 has a level so they return to that level when it runs.

    Does that help at all?

    Dan

  • 0 in reply to dsmurfin

    Hey thanks for replying,

    unfortunately no I don't think that is the issue as non of the house lights have recorded levels in the cues, not as zero or anything but as totally untouched channels.

    The only things that have any commands for them are the Intensity palette and the macro that uses the IntPal (plus when we tried putting them in manually afterwords).

    We've been trying even more today for example if we want to loop from cue 20 back to cue 1 or 5 or anything it still seems to sneak them out on the return loop but still keeps them in from 1 through to 20.

     

    Cheers,

    M



    [edited by: MB-C at 11:57 AM (GMT -6) on Wed, Jul 10 2013]
  • 0 in reply to MB-C

    Hi!  There are two different rules for linked cues that might be helpful for you.

    A linked cue is considered "out-of-sequence" and follows all of the rules of such a cue.  These rules are:  

       1)  Replay the entire state of the cue, including tracks.

       2)  Restore all manual overrides to home, unless those manual overrides are to other playback content (i.e., another cue list or a sub).

    The reason for that is to get back to the just the content of the cue you stored and are returning to, and not have "dangly bits" around that you have to manually clean up.

    A linked/looped sequence is NOT considered out of sequence.  So if from cue 20 you link to 10 and provide a loop value (loop is the counter that says how many times you want the loop value to be read... a common one is Loop 0, which says "continue until I break out of the sequence") - only the move instructions in cue 10 will be replayed on the link back, and manual values are not affected.    If you want cue 10 to be replayed completely (including tracks) you can assert it...but manual values will still be left alone.

    If you want to link back (but for some reason not provide a loop), but not have manual values impacted, you can capture them.  But if these are houselights, is there some reason you don't put them on a shielded sub?   That way they will not be impacted by ANY playback and will never be stored in cues.  

    Just a thought?

    a

     



    [edited by: Anne Valentino at 4:16 PM (GMT -6) on Wed, Jul 10 2013]
Reply
  • 0 in reply to MB-C

    Hi!  There are two different rules for linked cues that might be helpful for you.

    A linked cue is considered "out-of-sequence" and follows all of the rules of such a cue.  These rules are:  

       1)  Replay the entire state of the cue, including tracks.

       2)  Restore all manual overrides to home, unless those manual overrides are to other playback content (i.e., another cue list or a sub).

    The reason for that is to get back to the just the content of the cue you stored and are returning to, and not have "dangly bits" around that you have to manually clean up.

    A linked/looped sequence is NOT considered out of sequence.  So if from cue 20 you link to 10 and provide a loop value (loop is the counter that says how many times you want the loop value to be read... a common one is Loop 0, which says "continue until I break out of the sequence") - only the move instructions in cue 10 will be replayed on the link back, and manual values are not affected.    If you want cue 10 to be replayed completely (including tracks) you can assert it...but manual values will still be left alone.

    If you want to link back (but for some reason not provide a loop), but not have manual values impacted, you can capture them.  But if these are houselights, is there some reason you don't put them on a shielded sub?   That way they will not be impacted by ANY playback and will never be stored in cues.  

    Just a thought?

    a

     



    [edited by: Anne Valentino at 4:16 PM (GMT -6) on Wed, Jul 10 2013]
Children
  • 0 in reply to Anne Valentino

    Thanks Anne,

    That would seem to be the best explanation thanks for that.

    A quick answer for the sub is just because we didn't want to at that point, but that's what we used as a quick solution for the actual event, we just wanted to know the reason that we couldn't do what we wanted to.

    So just to clarify: If we add a loop number to our linked cues then because it isn't "out of sequence" it won't take out the manual additions?

    I think i understand that now, thanks a lot.

    M

    P.S. i've verified your answer as it definitely seems that you are correct



    [edited by: MB-C at 4:05 PM (GMT -6) on Wed, Jul 10 2013]
Related

www.etcconnect.com