ION: Making some simple Cyc fades.

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?

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?