Ion Classic running v3.3.0.549 - previous cue has 15 minute x-fade time and next cue has Assert and Block set but hitting Go does not stop the fade. The timer still counts down. Is this a bug or am I not doing it correctly?
TIA.
Roger.
Ion Classic running v3.3.0.549 - previous cue has 15 minute x-fade time and next cue has Assert and Block set but hitting Go does not stop the fade. The timer still counts down. Is this a bug or am I not doing it correctly?
TIA.
Roger.
This feature works correctly when I tested it. My first guess is that it might have to do with when the BLOCK was set on the cue. When in doubt always start with a simple example, so here is a test I would suggest...
Cue 1 -- channel 1 @ 50
Cue 2 -- channel 1 @ FL with a cue time of 15 seconds
Cue 3 -- channel 1 @ 0 with a cue time of 0 second, then also BLOCK & ASSERT on this cue
Start in cue 1, then go cue 2, and then a second into it, go for cue 3 and it should immediately jump to 0, no fading since timing was at zero.
Thank you for reaching out. We're not aware of an Assert bug, but would gladly take a look at your showfile. You can send it to eos(dot)moderator(at)etcconnect(dot)com. Please indicate in your email which cue you were running that didn't correctly terminate.
Thanks. I've sent an email with the showfile attatchment.
Hi, I tried that and works perfectly. I set the Block and Assert after the cue was recorded and wondered whether that makes a difference.
Thank you for the showfile. We can reproduce and will do some more research. It currently looks like this only affects the cue timer not actual channel values.
We'll update here when we know more.
Thank you for the showfile. This is now written up as [EOS-57532] Cosmetic: PSD: A cue that has Assert and Mark will not cause previously fading cues to display as finished
It only seems to affect the Playback Status Display counter. It's been like this since at least v2.9.3.
www.etcconnect.com