• State Suggested Answer
  • Date
    Robert452
  • Date
  • Replies 16 replies
  • Answers 1 answer
  • Subscribers 188 subscribers
  • Views 5813 views
  • Users 0 members are here

[Record Only] Help

The manual tells me this can be use to create a new cue list. (We only ever use one cue list - I ma not even sure why one would use multiple cue lists, maybe because we only run linear plays)  And, it will save only 'manual' values. I'm a bit hazy over the whole issue. If I have a cue that has some refocused MLs and a color change, will [Record Only] save just my color changes? When would I use [Record Only] as opposed to [Record}? Some examples would be appreciated and a comparison of manual and none manual data would help put this one away.

Parents
  • 0

    [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

  • 0 in reply to sk8rs_dad

    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.

Reply
  • 0 in reply to sk8rs_dad

    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.

Children
No Data
Related

www.etcconnect.com