v1.4.1 bugs/queries and other suggestions

Just to add to the above....

-Occasionally I get a syntax error when lamping off fixtures

-Trace Trace, which as I understand is suppose to trace an update as far back as possible in the cue list, doesn't appear to be functioning

-Iris Mode: I want the iris mode to change 6 seconds into the cue, so I put a delay of 6 on the iris and iris mode parameters, however the Iris mode is still changing at the top of the cue

-Effects: I have a linear effect running on a group of chans.  the effect is set to cascade - fade by size with a grouping of 7.  On its first cycle some of the chans that are grouped together don't come up, or are slow in coming up.  Subsequent cycles, the chans are coming up when they should be.

-Fader Control - Rate: What is the current situation with being able to speed up or slow down a cue?  Last I heard, rate wasn't working correctly.  Also, how does one affect the rate on the master playback pair?  Do you use the rate softkey under "fader control" or is the master pair constantly set to be a rate override (as far as I can tell the latter is the case, but a bit of info would be useful as this caused a show stop this evening)

 Thanks once again!

Cheers 

BrentFJ:

Just to add to the above....

-Occasionally I get a syntax error when lamping off fixtures.   CAN YOU LET US KNOW THE FIXTURE TYPE?  IS IT HAPPENING WHEN YOU HAVE A MIX OF DIFFERENT FIXTURES SELECTED?  OR JUST ONE TYPE?

-Trace Trace, which as I understand is suppose to trace an update as far back as possible in the cue list, doesn't appear to be functioning.   TRACE TRACE IS INTENDED TO ADD A NEW CHANNEL.  SO, IF IN CUE 5, YOU BRING UP CHANNEL 1 FOR THE VERY FIRST TIME, AND YOU MODIFY CHANNEL 2, WHICH WAS A TRACKED LEVEL ALREADY IN THE CUE LIST.  IF YOU UPDATE TRACE - CHANNEL 1 IS ADDED TO CUE 5, BUT NOT TRACKED BACK TO CUE 1, WHILE CHANNEL 2 SHOULD BE "TRACED" BACK TO ITS ORIGINAL MOVE.  IF YOU WANT TO "ADD" CHANNEL 1 TO THE LIST, TRACE, TRACE SHOULD DO THAT.  AGAIN, WILL LOOK AT WHEN AT A DESK, BUT THAT'S THE INTENT.

-Iris Mode: I want the iris mode to change 6 seconds into the cue, so I put a delay of 6 on the iris and iris mode parameters, however the Iris mode is still changing at the top of the cue.  FIXTURE TYPE?  IN GENERAL, MODE CHANGES HAPPEN IMMEDIATELY, AS THEY SIMPLY TOGGLE OTHER BEHAVIOR.  WOULD BE HELPFUL THOUGH TO KNOW THE FIXTURE TYPE.

-Effects: I have a linear effect running on a group of chans.  the effect is set to cascade - fade by size with a grouping of 7.  On its first cycle some of the chans that are grouped together don't come up, or are slow in coming up.  Subsequent cycles, the chans are coming up when they should be.  CAN YOU EMAIL SHOW FILE, IDENTIFY CUE AND EFFECT YOU ARE LOOKING AT?  (THANKS!)

-Fader Control - Rate: What is the current situation with being able to speed up or slow down a cue?  Last I heard, rate wasn't working correctly.  Also, how does one affect the rate on the master playback pair?  Do you use the rate softkey under "fader control" or is the master pair constantly set to be a rate override (as far as I can tell the latter is the case, but a bit of info would be useful as this caused a show stop this evening)  AT THE MOMENT, RATE HAS TO ALWAYS BE ASSIGNED TO THE FADER THAT YOU WANT TO TAKE RATE CONTROL OVER.  AND IT IS RESET TO 100% WHEN THE CUE (OR CUE SEQUENCE) IS COMPLETE.  WE WILL HAVE A WAY TO LOCK RATE CONTROL ON A FADER UNTIL LIFTED (1.5).  AT THE MOMENT, [RATE] + [LOAD] ASSIGNS THE RATE WHEEL TO THAT FADER. ON ION, THIS IS THE LEVEL WHEEL.  THIS IS WHY ON ION THIS IS TRICKY - ONE WHEEL... MORE ON THIS SOON.  THANKS!!  A 

 Thanks once again!

Cheers 

Anne Valentino:

BrentFJ:

Just to add to the above....

-Occasionally I get a syntax error when lamping off fixtures.   CAN YOU LET US KNOW THE FIXTURE TYPE?  IS IT HAPPENING WHEN YOU HAVE A MIX OF DIFFERENT FIXTURES SELECTED?  OR JUST ONE TYPE? one type of fixture - Studio Spot 575 CMY.  The syntax i usually enter is [chans 3 > 5 enter][more sk][lamp ctrls][lamp off].  Sometimes I get the syntax error, sometimes I don't.  Work-around is [select last][lamp off].  Haven't recieved any syntax errors when using select last.

-Trace Trace, which as I understand is suppose to trace an update as far back as possible in the cue list, doesn't appear to be functioning.   TRACE TRACE IS INTENDED TO ADD A NEW CHANNEL.  SO, IF IN CUE 5, YOU BRING UP CHANNEL 1 FOR THE VERY FIRST TIME, AND YOU MODIFY CHANNEL 2, WHICH WAS A TRACKED LEVEL ALREADY IN THE CUE LIST.  IF YOU UPDATE TRACE - CHANNEL 1 IS ADDED TO CUE 5, BUT NOT TRACKED BACK TO CUE 1, WHILE CHANNEL 2 SHOULD BE "TRACED" BACK TO ITS ORIGINAL MOVE.  IF YOU WANT TO "ADD" CHANNEL 1 TO THE LIST, TRACE, TRACE SHOULD DO THAT.  AGAIN, WILL LOOK AT WHEN AT A DESK, BUT THAT'S THE INTENT. That was the kind of situation I was trying (i think??)  If adding a new chan will TRACE TRACE track back to the start of the cuelist or only back to the next block?  I was trying this half way through a cue list and the chan only traced back until it reached a block.

-Iris Mode: I want the iris mode to change 6 seconds into the cue, so I put a delay of 6 on the iris and iris mode parameters, however the Iris mode is still changing at the top of the cue.  FIXTURE TYPE?  IN GENERAL, MODE CHANGES HAPPEN IMMEDIATELY, AS THEY SIMPLY TOGGLE OTHER BEHAVIOR.  WOULD BE HELPFUL THOUGH TO KNOW THE FIXTURE TYPE.  Studio Spot 575 CMY.  So I'm assuming the work around to delay the mode change would be to make a new cue with the change there and have it follow/hang from the previous cue? To add to this as well, It doesn't seem possible to alter variable speeds in the Iris Mode.  eg IRIS RAMP OPEN - it is not possible to alter the speed of the ramp open.

-Effects: I have a linear effect running on a group of chans.  the effect is set to cascade - fade by size with a grouping of 7.  On its first cycle some of the chans that are grouped together don't come up, or are slow in coming up.  Subsequent cycles, the chans are coming up when they should be.  CAN YOU EMAIL SHOW FILE, IDENTIFY CUE AND EFFECT YOU ARE LOOKING AT?  (THANKS!) Showfile to follow shortly...

-Fader Control - Rate: What is the current situation with being able to speed up or slow down a cue?  Last I heard, rate wasn't working correctly.  Also, how does one affect the rate on the master playback pair?  Do you use the rate softkey under "fader control" or is the master pair constantly set to be a rate override (as far as I can tell the latter is the case, but a bit of info would be useful as this caused a show stop this evening)  AT THE MOMENT, RATE HAS TO ALWAYS BE ASSIGNED TO THE FADER THAT YOU WANT TO TAKE RATE CONTROL OVER.  AND IT IS RESET TO 100% WHEN THE CUE (OR CUE SEQUENCE) IS COMPLETE.  WE WILL HAVE A WAY TO LOCK RATE CONTROL ON A FADER UNTIL LIFTED (1.5).  AT THE MOMENT, [RATE] + [LOAD] ASSIGNS THE RATE WHEEL TO THAT FADER. ON ION, THIS IS THE LEVEL WHEEL.  THIS IS WHY ON ION THIS IS TRICKY - ONE WHEEL... MORE ON THIS SOON.  THANKS!!  A This is still not consistent with the current behavior.  Enabling rate on the master pair, the wheel does not make any changes to the rate.  Is the master pair FADERS suppose to override cue transition at the moment, as this is the behavior I am seeing...

Thanks muchly!! 

Cheers 

Hi Jay

Don't mean to be rude, but I'm struggling to understand what you are trying to say in your post.  Any chance of getting a clearer explination?

Cheers 

not rude, it's confusing perhaps.  

Cue 1-3 is preset.  Cue 5-20 is scene 1.

Cyc is lit in scene 1.  While in cue 15 I forgot that I had added a cloud template (channel 101 which was previously out) and want it to be in scene 1.  I put it at the level that I want it and I want it through that scene.  I update trace the new channel in.  It should add that channel into the block and to the next block.

I also have put run lights through the board and need to cue them in.  I put channel 300 @ 20 and update trace trace to put them into the entire show ignoring blocks.

This is what I think should happen.  Is this true?  Like I said i don't have a light board in front of me these days.  

Thanks

Jay 

And then I remembered that it runs native on Mac OS (thanks) and I checked.  Trace trace, just goes into the block on a new cue, not past.  I feel like it does the exact same thing as trace does, only with a channel from zero, that seems poor.  If I changed my whole cyc in cue 18 to accomodate the new clouds (101) I should update trace and the whole scene should've changed.  Now I need to go back and figure out where 101 is supposed to go in, like the olden days.

 Again sorry for the confusion.

Hope this helps.

Jay 

Jay,

On the occasions, that I've wanted to put something like running lights throughout the show, not knowwing about trace trace, I've used Update cue x(first cue) thru cue Y (last cue.)

Jay:

Trace trace, just goes into the block on a new cue, not past.  I feel like it does the exact same thing as trace does, only with a channel from zero, that seems poor.  If I changed my whole cyc in cue 18 to accomodate the new clouds (101) I should update trace and the whole scene should've changed.  

Hi Jay

If you adjust the level on your cyc and then [update trace] the new value should be applied backwards through the cuelist to the last move instruction or the last block.

I've tried using [trace trace] and my understanding is if you are bringing up a channel for the first time in the show, lets say in Q20, and you want to update this to be in from the start of the show, update trace trace should trace the update back to the start of the cuelist.

Is anyone from ETC able to shed some light on exactly how [trace trace] functions...?

Also, as BSmith posted, if you want to update a chan for the entire show, or a large chunck of the show, ]update cue n thru n] works a treat!

Cheers

The story about trace....

 Right now, in 1.4.1, [Trace] and [Trace] [Trace] work as follows.

If you are (for example) in cue 5.  You make a change to a light that was in a tracked state (and lets say that this channel received its move instructions in Cue 2) and you add a light that was not previously used (new channel, not included in the cue list up until this stage).  If you [Update] [Trace] - the tracked channel will be modified all the way back to the source of its tracked value (Cue 2) and the new channel will be stored as a move instruction in cue 5.  If you wanted to add that new channel all the way back to the beginning.... [Trace] [Trace] will do that.  So, that new channel would now appear as a track, with a move instruction in your first cue.  

Make sense?... somewhat useful.

Moving on... in 1.4.2 (due end of month), we will treat a tracked zero (the light is off), just like we would treat a new light.  So, if a light has been inactive (zero) and you want to turn it on, and you want the fact that it is now on to go back through the cue list to the place that you turned it off... you'll do that with [Trace] [Trace].   

Trace works in live recording, and it can also be appended to a channel instruction in blind.  With all things tracking related, if this is confusing for you, I'd recommend you go into blind spreadsheet and play around with trace, trace trace, cue only/track to make sure you fully understand how the data is being impacted.  

Hope this helps guys!

a 

The story about trace....

 Right now, in 1.4.1, [Trace] and [Trace] [Trace] work as follows.

If you are (for example) in cue 5.  You make a change to a light that was in a tracked state (and lets say that this channel received its move instructions in Cue 2) and you add a light that was not previously used (new channel, not included in the cue list up until this stage).  If you [Update] [Trace] - the tracked channel will be modified all the way back to the source of its tracked value (Cue 2) and the new channel will be stored as a move instruction in cue 5.  If you wanted to add that new channel all the way back to the beginning.... [Trace] [Trace] will do that.  So, that new channel would now appear as a track, with a move instruction in your first cue.  

Make sense?... somewhat useful.

Moving on... in 1.4.2 (due end of month), we will treat a tracked zero (the light is off), just like we would treat a new light.  So, if a light has been inactive (zero) and you want to turn it on, and you want the fact that it is now on to go back through the cue list to the place that you turned it off... you'll do that with [Trace] [Trace].   

Trace works in live recording, and it can also be appended to a channel instruction in blind.  With all things tracking related, if this is confusing for you, I'd recommend you go into blind spreadsheet and play around with trace, trace trace, cue only/track to make sure you fully understand how the data is being impacted.  

Hope this helps guys!

a 

Brent... as a follow on... we've tracked down the effects problem (as you know).  Thanks so much.

Regarding Highlight.  This function is now working to spec.  And the way it currently works is something of a jump ball --- which we debated quite a bit.  When you are in highlight mode, whenever you deselect a channel, the changes that you made to it are manually maintained, but the remainder of the light returns to its non highlight state.    The alternative is to leave channels in highlight as you add new ones.  But, if your intensity highlight state is full (the default), if we leave the highlight state on... you'd need to manually return to a lower level to isolate the next fixture you are working with.  

 The best way to get the behavior you are looking for is to select all of the channels that you want in highlight mode, and then by hitting next/last, work with each individually.   Does that make sense? 

Thanks!

a

Hi Anne.

 Thanks for the info on Highlight and Trace Trace. All makes good sense

Cheers