X-Touch Mini Jumpy Encoder Behaviour

[BlippyBob]

Layer A of the X-touch mini will not smoothly go from one value to the next one in sequence.

It will jump to unconnected values in a repeating pattern. This behavior stops as soon as the script no longer controls the device, only layer A turn encoders are affected.

I'm experiencing this issue on Bitwig version 4.2.3 running on Windows 10, X-touch mini had the latest firmware (1.08).

This behavior can be reproduced by enabling the controller in settings automatically or manually and then using layer A to control any parameter.

https://user-images.githubusercontent.com/105938508/169578412-a5f42d6d-acee-4f4c-920f-b4288178a07f.mp4

I have tried deleting and reinstalling the scripts both by re-extracting the zip and downloading new zips and extracting those. Versions 2.3.1 and 2.3.0 both had this issue.

[larspohlmann]

I experience the same issue.

[justlep]

From the described behavior, I'd suppose that the X-Touch Mini script is not used/configured at all in your controller settings.

Instead, it looks like you're manually assigning parameters in Bitwig to the raw X-Touch rotaries (which wouldn't be necessary with the script, since the script handles all that for you).

I have added a documentation page for the X-Touch Mini script: https://github.com/justlep/bitwig/tree/master/doc/Behringer%20X-Touch%20Mini

Please check if your "Controllers" section looks similar as in the picture: https://raw.githubusercontent.com/justlep/bitwig/master/doc/Behringer%20X-Touch%20Mini/img/controller-setting.jpg

Let me know if the problem persists.

[BlippyBob]

I have checked, and my configuration looks identical to the picture, but the problem still occurs.

When I enable the script in Bitwig's settings, I manually select the x-touch mini (with Lennart Pegel as author) script under "Behringer". According to the installation instructions on the stable versions Github page.

Also, manually assigning "tool's" volume parameter to a rotary was just to show that the issue happens no matter how the parameter was assigned. The script automatically assigned the pan, effect send, and volume parameters of the channel strip. Sorry if this caused any confusion.

The issue doesn't occur if the script isn't on or the x-touch mini is configured as a generic controller.

If you need any information, logs, etc. please let me know.

[brianmartinux]

Hello everyone, I did try the same steps and am experiencing the same issue. Any updates on getting this working?

Also able to provide logs, more information, testing. Thank you so much (Windows 11, good PC)

[vodin26]

Hi! Same problem: Bitwig 4.4, win10 end Linux

[justlep]

Hi all,

I have finally managed to re-flush my Mini using the latest X-Touch Editor 1.21 and finally were able to reproduce the issue.

It should be fixed now with release v2.3.2 which I just published.

Please give it a try & let me know.

To be on the safe side, I have re-uploaded my working version of the Layer A preset. You may want to dump it to your Mini, too, just in case it doesn't work immediately.

Hope it's all good now.

Cheers.

[vodin26]

Thanks to the indifferent author, after the update everything worked as it should and my controller began to live a new life)