ION Record, Record only, Qonly

Jeff Toussieng said:

Want to make changes in a cue that track through until those channels would have changed anyway.  Example cue 9 has channels 1-5 at 75%, 6-13 at 25%  and all movers at ........  Cue 10 same but channels 1-5 change to 100%.  Cue 11 same as 10 but channels 6-13 change to 55%.  Cue 12 same but movers change to ........ Cue 13 sane but movers change again.  Cue 14 same but channels 1-5 change to 83%.  So channels 1-5 stay at 100% naturally from cue 10 until cue 14 when they make another change to 83%.  Later I decide in cue 11  I want to change channels 1-5 to 76% and that change tracks through to cue 13, then in cue 14, as originally recorded they change to the 83%.  Make the change in cue 10 and use Update Cue?

yes

Jeff Toussieng said:

Want to add a cue that doesn't affect the next cue at all: Record Cue # Qonly Enter ?  At that point what happens to everything that was supposed to track from the last cue to the next cue.  IE: Add cue 3.5 Only.  What happens to tracking from cue 3 to cue 4?

channel 1 is tracked through from q1 to 5 and you don't touch it for q3.5, then it is still tracked. channel 2 is at 30 in q3 and at 40 in q4. you add it at 40 in q3.5 Qonly. you get a blue 40 in q3.5 but the blue 40 in q4 is changed to a white 40 in q4. because there used to be a move instruction which is redundant now, the desk converts the move instruction to a block (autoblock). channel 3 was tracked at 50 from q1 to q5.

Jeff Toussieng said:

Want to add a cue that tracks but not all parameters track into the next cue or later cue which may still apply.  Simplest example: channels 4-6 in cues 3 - 12 would currently track through to cue 12 at 50% but in cue 6 I want to change channels 4-6 to go to 100% then in cue 9 go back to 50% and continue to cue 12 as originally recorded.  There would be other channels as well in those cues doing their thing independant of these channels.  Procedure?

go to blind, reformat as tracksheet. q9 enter, channel 4 thru 6 block enter, q6 enter, select last full enter.

Jeff Toussieng said:

I'm pretty sure I don't want to delete cues since it seems to me that can cause a whole bunch of tracking issues, but is there a way to do it easily in order to eliminate having to do GoToCue # at showtime or is there a command that skips a cue on Go?

you have channel 1 move to 50 in q2 and you track that value to q5. delete q4, no problem. delete q1, problem. the move instruction is gone, so channel 1 is gone. but delete q1 Qonly and the first tracking value after the deleted que is converted to a move instruction.

Jeff Toussieng said:

Record Only.  Still not 100% clear on what that does as opposed to Update.  Examples on when to use it please.

same as record (i.e. record NEW target or overwrite it), but only treats manual values. update is to modify a target with the manual values.

It's late.  Hope it makes sense :-)

Thanks for the reply.  Fine tuning now :-)

You:

channel 1 is tracked through from q1 to 5 and you don't touch it for q3.5, then it is still tracked. channel 2 is at 30 in q3 and at 40 in q4. you add it at 40 in q3.5 Qonly. you get a blue 40 in q3.5 but the blue 40 in q4 is changed to a white 40 in q4. because there used to be a move instruction which is redundant now, the desk converts the move instruction to a block (autoblock). channel 3 was tracked at 50 from q1 to q5.

Me:

So you are agreeing use Qonly to add the cue and explaining what happens to the channels when doing so?  If so, got it and clearer on what white can mean. 

You:

you have channel 1 move to 50 in q2 and you track that value to q5. delete q4, no problem. delete q1, problem. the move instruction is gone, so channel 1 is gone. but delete q1 Qonly and the first tracking value after the deleted que is converted to a move instruction.

Me:

Delete q4 no problem for channel 1.  I see that when the cue being deleted is the first command cue for in this case; channel 1 but what about deleting cues midway?  Do I need to look at the cue being deleted to see if it has any first commands or is it ok practice to use qonly always when deleting?  I realize this can get tricky.

You:

same as record (i.e. record NEW target or overwrite it), but only treats manual values. update is to modify a target with the manual values.

Me:

I think i read you to say use Record Only when recording something new; sub, cue, etc. and want to only record those red or manual channels/values and don't want to record anything else.  Ie; have cue 6 up, modify 4 of the 50 channels in it, which turns them red.  Want to record a cue/sub/etc with only those 4 channels in it?  Otherwise use update when modifying existing?

Jeff Toussieng said:

So you are agreeing use Qonly to add the cue and explaining what happens to the channels when doing so?  If so, got it and clearer on what white can mean. 

as long as you're not sure which channels of the following cue contain only magenta values (i.e. tracked ones) and not white, blue or green ones (i.e. blocked or move instructions up/down) i would use Qonly to insert. as an alternative you could Block the following cue before inserting the new one. with Blocking (Cue 4 Block Enter) you turn all values in this cue into hard values, so they wouldn't be influenced by tracking values from the cue that you inserted in front of it afterwards.

Jeff Toussieng said:

Delete q4 no problem for channel 1.  I see that when the cue being deleted is the first command cue for in this case; channel 1 but what about deleting cues midway?  Do I need to look at the cue being deleted to see if it has any first commands or is it ok practice to use qonly always when deleting?  I realize this can get tricky.

to what you call "first commands" we refer to as move instructions. they will always be green or blue. it's not a first command in the sese of this channel having a value for the first time, but rather having _this_ value for the first time. those green and blue values as well as the white ones (blocked) would not be influences by deleting a cue somewhere in front of it (deleting without using Qonly), but when you delete cues, that contain such values and you don't use Qonly, then you would influence other values, the magenta ones (tracking).

so yes, i suggest, you use Delete Qonly.

Jeff Toussieng said:

I think i read you to say use Record Only when recording something new; sub, cue, etc. and want to only record those red or manual channels/values and don't want to record anything else.  Ie; have cue 6 up, modify 4 of the 50 channels in it, which turns them red.  Want to record a cue/sub/etc with only those 4 channels in it?  Otherwise use update when modifying existing?

that's what i'm saying. RecordOnly is a special case of Record. in your example you could either use RecordOnly or you would use a command like Chan 1 + 5 + 11 Record SomeRecordTarget. as long as those three are the only channels with active values (and as long those channels are dimmers), it would do the same as RecordOnly SomeRecordTarget. you need to be aware that RecordOnly decides on parameter level what to record. so, you have a moving light, that has a red value for Cyan, and you do RecordOnly, only this Cyan value would be recorded. if you do Chan 1 Record, you would record this Cyan value, but the rest of the moving light too, whereas Chan 1 Cyan would do the same as the RecordOnly command.

everything more clear now, or less clear? ;)

Jeff Toussieng said:

So you are agreeing use Qonly to add the cue and explaining what happens to the channels when doing so?  If so, got it and clearer on what white can mean. 

as long as you're not sure which channels of the following cue contain only magenta values (i.e. tracked ones) and not white, blue or green ones (i.e. blocked or move instructions up/down) i would use Qonly to insert. as an alternative you could Block the following cue before inserting the new one. with Blocking (Cue 4 Block Enter) you turn all values in this cue into hard values, so they wouldn't be influenced by tracking values from the cue that you inserted in front of it afterwards.

Jeff Toussieng said:

Delete q4 no problem for channel 1.  I see that when the cue being deleted is the first command cue for in this case; channel 1 but what about deleting cues midway?  Do I need to look at the cue being deleted to see if it has any first commands or is it ok practice to use qonly always when deleting?  I realize this can get tricky.

to what you call "first commands" we refer to as move instructions. they will always be green or blue. it's not a first command in the sese of this channel having a value for the first time, but rather having _this_ value for the first time. those green and blue values as well as the white ones (blocked) would not be influences by deleting a cue somewhere in front of it (deleting without using Qonly), but when you delete cues, that contain such values and you don't use Qonly, then you would influence other values, the magenta ones (tracking).

so yes, i suggest, you use Delete Qonly.

Jeff Toussieng said:

I think i read you to say use Record Only when recording something new; sub, cue, etc. and want to only record those red or manual channels/values and don't want to record anything else.  Ie; have cue 6 up, modify 4 of the 50 channels in it, which turns them red.  Want to record a cue/sub/etc with only those 4 channels in it?  Otherwise use update when modifying existing?

that's what i'm saying. RecordOnly is a special case of Record. in your example you could either use RecordOnly or you would use a command like Chan 1 + 5 + 11 Record SomeRecordTarget. as long as those three are the only channels with active values (and as long those channels are dimmers), it would do the same as RecordOnly SomeRecordTarget. you need to be aware that RecordOnly decides on parameter level what to record. so, you have a moving light, that has a red value for Cyan, and you do RecordOnly, only this Cyan value would be recorded. if you do Chan 1 Record, you would record this Cyan value, but the rest of the moving light too, whereas Chan 1 Cyan would do the same as the RecordOnly command.

everything more clear now, or less clear? ;)

much more clear.  Thanks all so much.