• State Verified Answer
  • +1 person also asked this people also asked this
  • Date
    3perf
  • Date
  • Replies 4 replies
  • Subscribers 187 subscribers
  • Views 1521 views
  • Users 0 members are here

Manual time on fader: missing and incorrect level feedback via OSC

Hi,
I believe I've come across a bug in EOS (Nomad) when a Manual Time fader is involved.

Usually, all fader position updates are sent out via OSC. But when a fader is set to "Man Time", this doesn't happen.
If I move a fader on Tab28, no updates get sent out -- except for:

/eos/fader/1/5, Double: 1

or

/eos/fader/1/5, Double: 0

And that's only when the fader goes to zero, or transitions from zero to something else. 

Other types of faders (Cue lists, subs etc) immediately send out fader values (and correct ones) when a fader on Tab28 is moved.

When the faders are driven externally (from Luminosus), after about half a second of the fader having come to a stop, EOS feeds back "0" or "1" again. So with motor faders, putting the fader anywhere other than zero, it'll jump to 100% after letting go of it.

Discovered initially on Nomad v2.8.3 (Windows). Retested on 2.9.0 (Windows), the problem still exists.
Have checked the 'known issues' part of the release notes, but I don't think this problem is listed.

Cheers,
Daniel

Parents
  • 0

    Update:

    There's a similar (but not identical) mis-behaviour for FX Size and FX Rate faders. However this is probably an entirely different bug. What happens here:

    Moving the virtual fader on Tab28 does continually update the OSC output. However, the value output is wrong: If the FX Size/Rate range is between 0 and 200, then the value output via OSC is twice as high as it should be. Above a fader position of 50%, the value output via OSC clips at 1.

    You can probably see how I'm working my way through the new video tutorials, level 4 ... ;-)

Reply
  • 0

    Update:

    There's a similar (but not identical) mis-behaviour for FX Size and FX Rate faders. However this is probably an entirely different bug. What happens here:

    Moving the virtual fader on Tab28 does continually update the OSC output. However, the value output is wrong: If the FX Size/Rate range is between 0 and 200, then the value output via OSC is twice as high as it should be. Above a fader position of 50%, the value output via OSC clips at 1.

    You can probably see how I'm working my way through the new video tutorials, level 4 ... ;-)

Children
No Data
Related

www.etcconnect.com