Hi,
I have been using reference marks on my console, marking channels in live, and updating into my cues. When I mark the channel and update, it locks up all of the channel's parameters in the reference cue, and blocks the levels that were tracking from the previous cue. For some reason though, after a bit of programming, those blocked levels lose their references and their blocks and go back to tracking. The parameters that are moving remain marked properly.
Any idea what could be causing this?
Thanks!
Ethan
Eos v1.4.1
Hi Ethan. I haven't used referenced marks, but I just had a play around with them with the Offline Editor.
From what I can gather, the reason that tracked values Autoblocked is so if later in the cuelist you [update trace], these changes will not track back thru the cuelist to the previous block before the mark.
Best suggestion I can offer if you don't want these autoblocks to occur would be to be more selective about what you apply blocks to. eg: if you change the focus and only want focus to mark, then [chan focus mark enter] would be the syntax
The problem is not that marked parameters are getting blocked, it's that they get UNBLOCKED and lose their mark references when I cleanup the cue (to remove other unnecessary partial blocks). I used reference marks on a 500-cue musical on the Ion a few weeks ago, and I never experienced this problem when cleaning up cues. Same software version.
So, I'm assuming it makes sense to you why we automatically block any tracked values associated with lights that you mark? Well, just in case.... we do it to protect the data in the event that you change the tracked value upstream. Also, you can only mark move instructions .... so we automatically convert tracked values to blocks. This then makes the marked cue (M cue), the source of the move instruction.... although the parameter isn't actually moving.... since its already in the place you want it.
If you remove the block, converting the data to a track, the light can no longer mark, as its move instruction is now actually coming from someplace else.
Not sure how else to handle this. We could exclude the marked lights from unblock commands unless you specifically call for it.... ??
We could exclude the marked lights from unblock commands unless you specifically call for it.... ??
That's exactly what I'm suggesting. Kinda like the way Captured Levels are excluded from [SNEAK] [ENTER] commands, unless you specifically type in the captured channel and sneak it out.
We could exclude the marked lights from unblock commands unless you specifically call for it.... ??
That's exactly what I'm suggesting. Kinda like the way Captured Levels are excluded from [SNEAK] [ENTER] commands, unless you specifically type in the captured channel and sneak it out.
