• Date
    elvisbus81525
  • Date
  • Replies 4 replies
  • Subscribers 185 subscribers
  • Views 5839 views
  • Users 0 members are here

LTP, Ion tracking or Record only?

  New to the Ion and learning as I go, which sometimes leaves me gripped with fear when I try new things. Recently I did a show with a good sized selection of conventional fixtures and a small amount of moving heads. I used the movers for simple cyc looks with gobo movement and slow color moves. I put separate looks on faders and used, Record Sub, not Record Only. After recording the Sub I hit Out and cleared the command line so I was sure not to hold anything inside the programer.

   The problems occurred when I would be pushing a Par look up on a Sub and adding a moving light Sub at the same time. Or if I had a moving light Sub up and bumped some Par wash's. Sometimes the entire moving light look (on a different Sub) would be pulled from its position and color to a home position. I would have to pull the moving light fader down and back up or try a different cyc look to get things back on track. This reaction seemed unpredictable and I have to admit is was tough to negotiate a smooth progression of changes. I found if I did one thing at a time and faded up to 100% before I added moving light looks I was cool but honestly I'm not sure if it was tracking, LTP or something with Record Only?

   Thanks in advance!

Elvisbus     

Parents

  • Elvisbus,

    This definitely seems to be an LTP-related occurrence, or perhaps even an HTP related, depending on how you've configured your subs.  The Ion really doesn't have a programmer like you see on the Hog or other consoles.  The Ion deals a lot with manual data, which behaves slightly differently.  From your description, it sounds like you've recorded moving light parameters in submasters that you didn't want, even if they were at home values.

    First, to fix this, there are a few quick and easy solutions.  The one I recommend would be to go into [Blind] [Sub] ## and look at the data you've recorded.  Take data you don't want in there out by selecting the channel (or parameters about that channel), and press [At] [Enter].  (Remember, you can get refined in this command by using the tiles in the CIA -- [1] {Intensity} {Color Select} {Zoom} [At] [Enter] will remove information about those parameters only).  

    Second, to resolve this when you record other submasters, be careful of what you have active and/or manual.  Using Record will store information from a lot of different input sources, including active cues, submasters, manual data, and others.  By using the Record Only command, you will only store what is manual data -- i.e., the channels that have a level in red.  Another great feature is the selective store -- selecting only the channels that you want recorded in the same command line. With a very similar syntax as the [At] [Enter] scheme above, you can specify exactly what you want the console to store.  By typing [1] [Color] [Record] [Sub] [1], you will only record the color data from channel one and nothing else in the rig.

    Both are powerful ways to edit the information you're storing and change how you're storing it.  That said, cue lists are definitely designed for the smooth transitions of moving light looks without the anomalies of submaster interaction.  Shows all have different requirements, though, and submasters are definitely a great tool on the desk.

  • in reply to Hans.Hinrichsen

    One thing to add -- while mastering selective storing would be the most efficient solution, clearing the slate requires Goto Out.  Just taking the channels you recorded Out leaves the zeroed levels manual as well as has no effect on NIPs.

    -Josh

  • in reply to jbenghiat

    Do you mean [Goto Cue] [Out]? Where is [Goto]? 

  • in reply to elvisbus81525

    I believe he did mean to say [Go To Cue] [Out].  There isn't a [Goto] button.

    [Go To Cue] is directly above the [+] key.  The [+] key is directly above [7].

Reply Children
No Data
Related

www.etcconnect.com