Hej everybody,
I do not know if this is a question or should be started as a discussion. Probably this has already been discussed but I didn´t find it.
It´s about what I call Darkmove.
On EOS there can be much unnecessary movement when it programming wasn´t that clean and/or many cues have been copied around.
I´m regularly programming in Q-Only
For example:
Movinglight 1 is in Pr.1 in Q1-10, dimmer on
in Q11 dimmer goes to zero
in Q12 dimmer stays off but (for whatever reason) position changes to Pr. 2
in Q13 dimmer stays the same but position changes back to Pr. 1
in Q14 dimmer goes full an Pr. 1 is the correct position
no blocking ´n stuff
In my scenario position change was an accident but the the console is telling the fixture to go to that position(even if it´s not necessary) anyway.
These days I´m working on a Transtechnik Console where the Darkmove is working completely different but that desk ignores position changes if dimmer stays off all the time.
Next desks here to come will probably be EOS/Gio but people here are concerned about that unecessary movement.
I know that much of that movement can be avoided an I love tracklist for easy cleaning that stuff but we still have to do it for sometimes 50-60 Movers, up to 20 Yokes and several scrollers. Biggest problem is the noise and for the yokes (with barndoors ´n stuff) the slow movement can be a problem as well.
My questions are now:
Is the behavior unavoidable as part of how EOS handles marking/darkmove?
Has that stuff already been discussed and if so how is ETCs look on that?
Is there any effort/will to change the behavior to something similar to my description?
How do you other operators see that? Should we (here in Salzburg) just be more accurate during programming or would you like the desk to do more of your work as well?
So, no offense here just want to know what I can expect/what you think about that.
Cheers
Paul
