• State Not Answered
  • Date
    madorangepanda
  • Date
  • Replies 7 replies
  • Subscribers 185 subscribers
  • Views 6362 views
  • Users 0 members are here

ION: Making some simple Cyc fades.

Hello, I'm new to the ION console and would like some help to do the following.

I have a groundrow and flown row each consisting of 6 4 cell cyc battens. It can be assumed that they only use 8 different dimmer channels (1 per colour)

I would like to create some very slow fading sky colours for Dawn, Day, Dusk and Night skys.

As the show progresses most of the time I would like the cyc to continue it's fade, irrespective of the rest of the lighting state. Then on certain cues I would like the cyc to rapidly progress to the next state I.e. Dawn into Daytime.

Any useful info appreciated.

 



[edited by: madorangepanda at 6:05 PM (GMT -6) on Sun, Feb 21 2010]
  • 0

    Howdy,

    I think the easiest way would be to create a second cue list triggered off of the main list. 

    So for example. You main list has all of your programming other than the cyc. 

    Your second cue list (2/) would contain several long cyc cues. 

    Set your main list to execute the secondary cue list when needed. So [Cue] [n] {Execute} [2][/][m][Enter] where n is the cue number in the first list and m is the cue number in the second list.

    When you press go for cue n, it will trigger cue m on your second list. Each consecutive go on your main list will not effect your second list until you put in another Execute command unless of course you give your cyc channels a value in your main list. Doing it this way, your cue numbers between your cue list do not have to relate. Cue 1 can trigger cue 2/27. Cue 100 can trigger 2/9 etc...

    Another option which I prefer as its less thinking in my head in term of when to trigger a cue, is to make thetwo lists cue numbers line up when needed and just set the 2nd cue list to follow the first. Rather than [Cue] [n] {Execute} [2][/][m], just leave out the last [m]. Do this on the first cue in your main list, and the rest will trigger automatically

    For example... list 1 has cues 1-100 sequentially. list two only has Q 1, 27, 39, and 40. 

    When you run cue 27 on your main list, your second list will fire as well. Just remember that with this method, if you want your second list to have cues that run internally (links/loops/follows) make sure to make them with cue numbers that don't exist in your main list.

     

    Does that make any sense?

     

  • 0 in reply to travisres

    That makes sense, will give it a try and post back if I have any problems.

  • 0

    In theory you could do it off one cue list, maybe using multipart cues as the desk keeps long cues running in 'background', but using a second cue list for the cyc makes most sense, as it makes it easier to work out why the cyc is doing something unexpected during the tech.

    Remember to Assert the cues where you want a rapid fade just to be safe.

    Cheers

    Richard

     

  • 0

    I personally think that if you are referring to a cued show in which all actions occur in the same order everytime, a single cue list is simplest and easiest.  Just make sure that your cyc channels are not in the cues in between the cyc changes.

    There are numerous valid methods of doing things on the ion/eos.  Many people are inclined toward multiple cue lists out of preference.  The only time that a second cue list would be necessary is when then all of your cues are not expected to be in the same order each time. 

    2 cents, and welcome to the forum,  B 

  • 0 in reply to RichardJ

    I second Richard's suggestion, but using discrete times on the long-fade channels, rather than parts - it works a charm. A five-minute fade on them continues uninterrupted by subsequent cues. For those spots when you want your cyc to jump to a level, I think that simply putting manual values in that cue will work, but Assert is definitely a good idea there.

     

    John

  • 0 in reply to jmusarra

    Question for the crowd...

    With 2 cue lists, during tech if somebody calls a hold, you will have to press stop/back on your second list (assuming you have it mapped to a wing), so that you can attempt to keep the cyc look in time with the rest of the show.

    Using discreet timing or parts... when you press stop / back with background channels running, do they stop as well, or only the channels from the most recent cue?

    Just curious as I don't think I've ever run across it, or paid enough attention to background channels. But I do totally agree with Brent and John. If the show is called 100% the same there, keeping it down to 1 cue list is simpler depending on your tech style and if the background channels do stop with a Stop/Back command.

  • 0 in reply to travisres

    Benjamin,  That was a good question that I didn't know the answer to, so I checked it out.

    In one cue list, the first press of the Stop/back key stops all channels from that list.  At that point a press of the Go button resumes all moves in the correct timing.  A second press of the stop/Back key will dump you into the last executed cue overiding any incompleted moves.  I confess that I wouldn't know how to resume a long, half-finished background fade from that point. 

Related

www.etcconnect.com