Fader Status Display Issue in v2.5

Hi there,

We do a number of shows using simple submasters with programmed fade times mapped to faders on our Ion, with playback using bump buttons. Previously, both the fader wing displays and the fader page view of the main PSD would show the live intensity of the submaster as it was fading (0-100%). Since updating to Eos 2.5, this reading jumps immediately to 100% or 0%, even though the fade executes correctly in the programmed time. I am experiencing this behaviour on Nomad for Mac as well. Is there something I might be missing?

Thanks!

Doug Cox

  • Hi Doug,

    Could you tell me what version you were updating from? I just checked the behavior in v2.3.3 - 2.5.0 and it's consistently doing as you say - the content of the sub fades, but the fader indicators and screens jump to the final position.
  • Hi Matt,

    We updated from 2.4.1. I'll roll back our console when I have a moment tomorrow and try to replicate this, but I'm quite certain that we were seeing the fades previously. I personally can't see why it would be desired operation to see something other than live data in this scenario — are you suggesting that this jump is the intended behaviour?

    Thanks!
    Doug
  • Hi Matt,

    I second this. We have the same issue here and the yellow fader level indicator jumps to 0 or 100. Output from the desk follows the time of the fader. And yes this was definitely working in the last version of 2.4. 

    Could this get fixed please...

  • Hello Doug,

    I apologize, I misunderstood your comment about "playback with the bump buttons".  One of our developers realized that you meant assigning time to the Sub, then pressing the Bump button to get that Sub to play back in time.

    On Tab 28, you see this indicator:

    That was added in v2.4.   It will go up and down as a timed fade from a Bump of a Sub is occurring.

    In v2.5, it's jumping to the end position.  It also gets confused when there are effects in the Sub.

    We have an SCR 39829 for both of those behaviors.  We're looking to get it fixed in the next software release.

Related