Greetings..
I'm running Cobalt 7.1.1 on a Congo Kid. I've noticed that when I [seq+]/[seq-], if there are parameter changes, the entire console basically locks up and stops responding until those parameters finish moving. This can make using Seq+/Seq- to step through a cue sequence which includes attribute changes extremely maddening. Even worse -- all other cue related functions are paused until its finished.. So if I [seq-] and then need to hit [Go] before the parameter is finished moving, the console won't respond to the go until the Seq- is fully finished.
Is this behavior configurable somewhere? My hunch is that Cobalt is trying not to snap parameters around for fixtures that have moving parts (though ultimately, that should be up to the fixture to protect itself against).
What's going on here, and how do other folks get around it without going mad? :-)
Thanks!
