ML Newbie, How to avoid changing 2 cues when updating 1, with ML

 Hi Everyone!

 

I'm new to using ML with the Element. I'm trying to use a Moving Light with cues. I'm in Cue mode Only. I have setup 3 cues (for the exemple)

 

Q8: The ML is pointing forward, and is red, intensity 100%

Q8.9: Blackout Q: The ML dims intensity 0% and then, it moves (MK) to the settings of Q9

Q9: The ML is pointing backward, is blue, intensity 100%

 

This works perfectly fine... The issue I have is, let's say I want to modify Q8 Live, and change to color to Orange... So I do the change in ML Control, then Record-Cue-Enter and it's saved. However, when I replay all this, when I go to 8.9, the colors does not change to be ready for Q9 once intensity is at 0. Channel display of the colors are in blue and stay at a value. Then when I launch Q9, then it will change to to Blue.

The solution that I found was: BLIND - Cue 8.9 @ Enter - Cue 8.9 @ 0 - LIVE: And it works back as before

 

So I would like to know how can I make a live change to Q8 and save it, without having to change Q8.9. I also tried using Update instead of Record Cue but does the same thing (for this)...


Thanks!

 

Parents
  • In general I would strongly recommend using "Tracking" as the default mode on an Eos Family console.

    The main reason for this is that Cue Only is almost always misunderstood.

    Cue Only means:
    "I have Cues 1, 2, 3, 4. When I edit Cue 2, please copy the old values from Cue 2 into Cue 3 onwards. I don't want Cues 3, 4 etc to change."

    It only has any effect when editing out-of-order - if there is no Cue 3 yet, it can't be updated.
    As you've found above, Tracking is often what you actually meant!

    The main thing to remember with Tracking is to Block (and Assert) your blackouts. If you do that, you will be fine!

  • Uhm, no. Cue only means that if you change cue 2 then cue 3 will not change along but stay exactly as it was before. It protects the next cue to still look the same on stage as it did before
  • No Ueli, updating a cue using "Cue Only" updates that cue and the next cue.

    Values that were "null" in the next cue are made manual and updated.
    - This is why your changes don't track into that next cue - the old ones are updated into it.

    That's why I dislike Cue Only mode - it does not do what people think it does, and then you get confused because it has side effects you may not be expecting.

  • I live on the Cue Only continent, I grew up in cue only. Saying it updates the next cue as well is confusing a user even if it technically correct. Yes, I end up with a move instruction where I had a tracked value before, but while the font color changes, the value stays the same, and the value is what counts. This is the reason why cue only people can't be convinced to work in tracking.
  • I ended up trying ueliriegg solution(Update Track) and it worked perfectly. I know there is a big debate Cue Only vs Tracking, but in my case, i feel that Cue Only is much easier and I end up with a lot less errors then tracking mode. Perhaps I just did'nt play around too much with it but for now Cue Only does the job very very well! :) And I totally agree with ueliriegg, I don't really care about what's display or how it's done, the important is the end value, what is sent to the lights..

    Thanks guys for your help! :)
Reply
  • I ended up trying ueliriegg solution(Update Track) and it worked perfectly. I know there is a big debate Cue Only vs Tracking, but in my case, i feel that Cue Only is much easier and I end up with a lot less errors then tracking mode. Perhaps I just did'nt play around too much with it but for now Cue Only does the job very very well! :) And I totally agree with ueliriegg, I don't really care about what's display or how it's done, the important is the end value, what is sent to the lights..

    Thanks guys for your help! :)
Children
No Data
Related