[Record Only] Help

[Record Only] stores only manual data, so it's a convenient way to prevent storing unwanted parameters or channels into a record target. [Record] stores the state of every parameter. Both [Record] and [Record Only] can be used to create a new cue list so there's no difference there.

In your example, if you made the focus and color parameters manual then both would be saved using [Record Only]. If only the color changed then only the color move would be saved using [Record Only].

As to which is better, it depends on your programming style and how much you embrace the move-fade philosophy. I tend to use [Record] for the first cue in a show and [Record Only] almost exclusively thereafter. [Record] is great if you can work from start to finish building a cue list and never change your mind. I'm not that organized. So I jump around, sketch in cues and rework them later, often several times during the tech process. [Record Only] helps me cut down on cleaning up unwanted moves and unexpected consequences, like watching a mover change position or a scroller zip for no good reason, only to move again on the next [Go].

Many threads have accumulated over the years about record, record only, update, selective storing, and the relative merits of each.
community.etcconnect.com/search

Wow, you were looking over my shoulder when that ML beam skittered across stage! Nice answer, though can you expand a bit on  manual versus none manual data. Is it only 'stuff' in palettes that is none manual.

For historical reasons we always run ELE2 in Cue Only which may alter what you said a bit. But, totally agree. We start off putting some ball park 'looks' (like upstage, downstage etc.) onto Subs which we pull up, modify and save as a very early cue. We then add or subtract from that and save as a new cue etc. Then, when we  go through blocking the cues are constantly visited changed and updated. We run 'linear' plays and musicals several times a year.

I'll add to this by including; you might be interested in flexing your record/record only muscles by making use of Filters. Filters allow for drilling down even further beyond the base levels of record/record only to specify that you want to {Record Only} [Color] Data, or {Beam} {Focus} {Intensity}, utilizing filters can be a great way of saving time and identifying specific data to record. A great way in busking to quickly create palettes, presets and sub playlists is to use Macro Record filters to record next in a list or palette group to be able to quickly capture and recall specific data from a look.

Anything in red on the channel display is manual data. That is, anything you touched and have yet to record into a target.
Your rig includes more than conventional lighting. Do yourself a favour. Embrace the move-fade philosophy and turn off Cue Only mode. It will greatly speed up your programming once you've crossed the chasm.

As for your question of what is manual data: 
"manual" is all data you changed, ie all the values displayed in red on the screen (Channel view). Do not confuse referenced data with non-manual data (you were asking if only data in palettes are non-manual).

Record only can be helpful for example to record a sub whilst you are in sitting in a cue without having all the cue data. Let's say you are sitting in cue xxx and you decide you want only your channel yy on a sub. Since you haven't set any values other than the cue, you type (for example): yy at 80 enter. then: record only sub 11 enter. 

that records only channel yy in sub 11.

As for creating a multiple cuelists: you type either record or record only cue x/y. That stores cue number y on cue list x. (x being numbers obviously). There is an online training happening on multiple cuelist on Thursday 16th October by the way (if I am not mistaken).

hope that helps.

OK OK. I know, I know and meeting these consoles for the first time last year I would have gone along with tracking. I have 3 or 4 guys who used an Expression 3 in Cue only for more than 20 years! They never went beyond putting on legacy lights and saving cues so MLs are anathema to them. I am considering starting the next show file when Oliver is over as "Tracking" but even as I think about it I'm trying to work out how it might effect one of them and what sort of call can I expect of an evening when they are blocking. A good excuse would be to remind them are no longer using just (simple 1 to 1) legacy lights. 

One point (just to show off a little) you mention Tracking can speed up programming. Presumably because a change to a channel in a cue will automatically 'go forward' so we won't have to visit subsequent cues. But tell the old boys if they want that change to go forward to use the [Cue only/Track] button.

Are there any other arguments I can use to support the move to tracking?

I mentioned multiple cue lists because they were involved in an earlier answer. I spent some time on a Strand NEO and that was the 1st time I saw multiple cue lists. But to tell you the truth, perhaps because we only do linear plays have very little idea why/how one would use multiple cue lists.

I use multiple lists to separate out parts of my rig, and to do different things:

1. Main Show List
2. MIDI/OSC Cue Triggers
3. Haze
4. Followspots
5. ML Checkout
6. Conv Checkout
7. MIDI Checkout
8. SMPTE Checkout

Are some of the things that I use multiple lists for. In the case of the MIDI/OSC cue triggers, when I am interfacing with another product (d3 video servers) it is easier to put those triggers in a different list so that I can see exactly what information I am sending to them.

I use the Haze list so that I don't see the haze effect number in every cue in my main list.

The followspots are in their own list so that the ALD in charge of them can see what those lights are doing - and so that they don't interact with the main list.

Checkouts are all split up so that multiple people can run checkout at the same time - we can have someone on the console, and two poeple on iPads checking things all at the same time.

Sometimes if I need a specific effect to run in a super specific manner I will split that out into its own list so that I have more control over it. This happens less and less with each update to the effects engine however...

There are a lot of ways for multiple lists to be helpful - it's not necessarily about how the show plays back, but also about how multiple lists can speed up the overall flow of the show.

That certainly explained the multiple list for me very well - thanks. I can see why you would use them. Your setup is like night and day compared to yours so MCLs have never really been needed. Having said that the bit about Hazing I think really bought the message home. Thanks a million - that's one of those background things that have been niggling me since I use the NEO)/. 

You got it! I will typically split the screen with the CIA on it to show me the these additional lists:

And on the spot list I hide the FX number since the label tells me what I need. This is what it looks like without the FX column hidden:

That's not information I need to see it my main list - it just muddies things.

If you are going to look at using multiple lists I'd suggest looking up OOS (Out of Order Sync) and Partitions - they are both great tools that go hand in hand with multiple lists.

Lots to think about here Scott. I will have some time once our "Oliver" is up and running in two weeks to do a lot more reading and experimenting.

So, decision made. Right after "Oliver" I'm going to change the console to tracking. Will spend the time while that show runs to build cues at home and try to see if I can unearth "Gotcha's" before the next show gets going and someone calls me at 11pm to ask what happened! 

Something to keep in mind is that tracking/cue only are not playback functions - they are editing tools. A show programmed in cue only will look the same when played back in tracking and vice versa.

Thanks Scott. I have made two shows with 3 dimmers and 3 MLs in each. One is Tracking and the other Cue only. So a series of identical cues will be made in each and then edited. The same edit being made in both show files. Means a bit of switching but the sACN output table (I have restricted my addresses to 512 to see values),  the Blind Spreadsheet and the Augment3d screens should provide some feedback, Now I just have to design some scenarios whereby different things happen that might surprise the new 'Tracker' user. Allowing for the use of the [Cue Only/Tracking[ key should add some spice! 

Is the OP using ELE2? Therefore there is no options for multiple cue lists. 

Robert452 said:

For historical reasons we always run ELE2 in Cue Only