updating presets fail

Hi,

What you describe is just one option available when updating a cue which references a Preset. Depending on the update style you have as your default, or the option you choose as you make the update you can modify this behaviour.

At the moment you probably have 'Update All' as your default behavior. This means the console will try to update as far back in the chain as it can. So any Presets referenced by the cue will be updated. If you don't want this behaviour you can change your Update Mode in setup to Update 'Make Absolute'. This will place absolute data in your cue and not affect your presets. Alternatively you can choose this option in the update window which pops up when you hit the update key - this will then default back to 'All' for the next update.

Update is a very powerful tool which can cause unexpected results if you are not aware of all the options available.

Let us know if you have more questions on the subject.

At the moment Locked Presets are not available, but Locked Palettes are.

Hope that goes some way to answering your question...

Graham

It does help.  I've changed it in setup.  I'm on a movie so its live programming all the time.. And its my first week with the desk.   While I have you.  If I grab all channels,{make man} [update] [make abs] (or have it engaged in setup) I can give hard values to the whole output of the desk?

I just tried this and it only works for modified or default levels, not tracked or untouched

I saw your other discussion about this. As Andrew mentioned, we probably need to know a bit more about what you are trying to achieve. At one point you mentioned recording the output into a second cue list. At other times it seems like you simply want to Block a cue.

I'll try to offer a few words of wisdom.

Eos/Ion are tracking consoles. You can't put them in 'non-tracking mode'. They can be put in Cue Only mode, which changes the default behaviour of an update or record action.

If you give a channel a manual value and update it in a cue this will be recorded as a hard value, unless it happens to be the same value as the previous cue, in which case it will left as a tracked value. If you then want to avoid tracking a change through this cue you need to block the cue. This will turn all tracked values white (blocked) effectively giving them 'hard' commands.

Using the Record key without any channel selections before it will record the whole output of the console. The same rule applies though: if the levels are the same as the previous cue they will appear as tracked values.

Update and Record Only functions are only looking at manual (red) values. So Record Only is similar to recording the contents of the Programmer on a Hog - anything that you have manually modified.

Make Manual is really just a way of making channels availble to be included in Record Only or Update actions.

Perhaps you could give us a scenario which describes your question, that might help us to understand what you wish to achieve.

Graham

Thank you for your reply. 

On a hog, and a Ma, if I grab a tracked channel and give it a level (even the same level tracked) and record it in the cue it becomes a hard value.  Moving or deleting cues prior to that cue will not affect the hard recorded values. There are also feedback colors to tell me whther its tracked, hard or belonging to another cue list.     As I work more with the Ion I realize that as long as [go to cue] brings in the tracked levels I will not lose levels unknowingly.  That is what I'm trying to prevent: the lose of channel levels because a tracked item loses its reference.   Working with the other 2 consoles I'm very aware of how levels can be lost due to bring up a cue with out its reference information.  I'm getting used to it, but I don't have as much control over the tracking aspects of the console as I would on a hog.  I can't change a tracked value to a hard value.  The console is choosing to track if the level is unchanged. 

On another issue:  Is there a way to look at the dmx output of the console, per universe?   In both Hog and Ma there is an output display that gives me the dmx values going out to the channels (here addresses)?  Now that I have my presets built for my luma panels and kinos I can manipulate their attributes...however the level reading pr 1 or pr  4 is really not reassuring especially since there's a chance I might unknowingly update a preset by accident.  ( I have changed the desk to {make abs} by default.

The scenario I have is I'm running 240 dimmers, 238 channels of flourescent tubes in luma panels, and 258 channels of kino flo on a movies set.   We record cues as records of what is done, not for playback.  I playback cues only when the Gaffer wants to go back in time or bring a previous look up as a similar camera angle.  Its all live programming in that nature.  Because the desk is a tracking desk I just need to know that the looks that I bring up are complete.  [go to cue]  brings in tracked channels.so, so far, its all ok.

meatpopsicle said:

The scenario I have is I'm running 240 dimmers, 238 channels of flourescent tubes in luma panels, and 258 channels of kino flo on a movies set.   We record cues as records of what is done, not for playback.  I playback cues only when the Gaffer wants to go back in time or bring a previous look up as a similar camera angle.  Its all live programming in that nature.  Because the desk is a tracking desk I just need to know that the looks that I bring up are complete.  [go to cue]  brings in tracked channels.so, so far, its all ok.

If you are just storing "looks" and aren't planning on running them as a sequence of cues, you might be better served by recording each look as a preset.  That way there is no tracking issues to trip you up.

Just a thought.

-Steve Martin

way too much channel editing for that.   And, now and again, we do have to re-play a series.  I've set up 20 or 30 presets to deal with my lumas and kinos.  There's no way I would treat the whole rig that way.   Better I learn to manipulate the desk instead of it manipulating me.

Thanks for thinking outside the box though.

The block function seems to be what you are looking for.  We don't automatically convert tracked values (when matched) to blocks unless you tell us to.  

We are adding an output column to patch by address in an upcoming build.  In the meantime, you can see the DMX output under about.

Hope that helps!

a

meatpopsicle said:

On another issue:  Is there a way to look at the dmx output of the console, per universe?   In both Hog and Ma there is an output display that gives me the dmx values going out to the channels (here addresses)?  Now that I have my presets built for my luma panels and kinos I can manipulate their attributes...however the level reading pr 1 or pr  4 is really not reassuring especially since there's a chance I might unknowingly update a preset by accident.  ( I have changed the desk to {make abs} by default.

If you hold down the Data key, that will show you the data behind presets and paletts.  If you're dealing with multiparameter channels, you will have to expand them in table view to see the raw data.  Also, FYI, holding down Label will toggle between preset/palette numbers and their labels.

[Go to cue] always reliably reproduces the look of any cue, including any tracked values.  Recall From does as well, which might be quite useful in your situation.

-Josh

Thank you, and Anne.  I'm re reading my displays chapter now!  ;D

The data hint is awesome but I would still like to visualize the outgoing data levels in a channel table.  So when that is instituted

Thank you, and Anne.  I'm re reading my displays chapter now!  ;D

The data hint is awesome but I would still like to visualize the outgoing data levels in a channel table.  So when that is instituted