Hey Folks.
I have bi-directional control over Behringer X32 mixer faders from a custom OSC editor via Osculator.
If I control the X32 faders from the editor, sending OSC to the X32, the screen and X32 faders moves very smoothly.
If I send OSC from the X32 faders to the editor, the screen and the X32 faders also move very smoothly.
However, when I have Osculator mapped for Bi-Directional communication, the X32 faders don't move smoothly when physically touched.
They will begin to move and then jerk to a stop but will still move if physically forced.
If I then move the fader very slowly it will move better but with kinda jerky stops along the way.
Is this a port buffer over run situation? Too much data moving back and forth?
I have setup three different mapping configurations in Osculator that I switch between so far to work around this.
1. Editor only control (Show Mode)
2. X32 only control (Programming Mode)
3. Selective Bi-Directional control (Show Mode)
The first two work very well. The third is a little glitchy as stated.
The Bi-Directional glitches don't seem to be a problem for the X32 digital encoders.
It probably happens to them too only they are not mechanical is my guess.
X32 Buttons also seem to work just fine.
Any ideas for a work around or parameter adjustment would be great. Thanks.
Kyra
I have bi-directional control over Behringer X32 mixer faders from a custom OSC editor via Osculator.
If I control the X32 faders from the editor, sending OSC to the X32, the screen and X32 faders moves very smoothly.
If I send OSC from the X32 faders to the editor, the screen and the X32 faders also move very smoothly.
However, when I have Osculator mapped for Bi-Directional communication, the X32 faders don't move smoothly when physically touched.
They will begin to move and then jerk to a stop but will still move if physically forced.
If I then move the fader very slowly it will move better but with kinda jerky stops along the way.
Is this a port buffer over run situation? Too much data moving back and forth?
I have setup three different mapping configurations in Osculator that I switch between so far to work around this.
1. Editor only control (Show Mode)
2. X32 only control (Programming Mode)
3. Selective Bi-Directional control (Show Mode)
The first two work very well. The third is a little glitchy as stated.
The Bi-Directional glitches don't seem to be a problem for the X32 digital encoders.
It probably happens to them too only they are not mechanical is my guess.
X32 Buttons also seem to work just fine.
Any ideas for a work around or parameter adjustment would be great. Thanks.
Kyra
Comment