faderboard parameter resolution

[pieterhu]

We're using a Coolux faderboard to control the opacity of several live cameras. The faders are in WD assigned to the opacity of the layers.
In the WD fader board menu the actual value implies the resolution is higher than 8 bit and according to this readout it's quite precise. However, when moving the fader, the opacity is not changing smoothly and several jumps between values (and in the intensity of the projected image) are noticeable.

Is there an option to get the fader movement translated in the 8-bit value more accurate?

[Markus Zeppenfeld]

Hi Pieter,

this seems to be a readout issue at the moment.
The 16bit values are not represented each single. These are jumping as well, so there is no way around it.
As a workaround you could hook up a damping node in between the fader extension node and a layer control output.
We will improve that readout...

Within Pandoras Box you will get a better result of pushing the fader. Is there a chance to assign the live inputs to a separate timeline each?

Thanks for reporting.
Markus

[pieterhu]

Hi Markus,

Is there already a solution for the faderboard resolution in the newer software version or should we use the damping (prediction?) node for our upcoming production?

Pieter

[Christopher Fluegel]

Hi,

which WD revision do you use? For me in WD rev 418 and PB rev 8071 it looks smooth without jumping values. Both ways, the faderboard input node and the faderboard configuration panel (under tools > keyboard input), work fine.

If not for you a solution could be, as Markus has already written, to assign your live inputs to different sequences and assign the faderboard to this sequences from within PB itself or damping timed node in the node chain. (faderboard input node > range node > damping timed > layer control).

Hope that helps.

[Markus Zeppenfeld]

Hi Pieter,

within Rev430 (Beta) the issue has been fixed. It now behaves correctly with 256 steps per fader.

Markus