Your shopping cart is empty.
🔥 Lifetime deal! Get Control Surface Studio for Just £67 👉 Click Here To Get It
Time left...
⚠️ Lifetime licenses are ending soon, get yours before they're gone ⚠️
Updating knob position on infinite knobs for Behringer X Touch Mini
Submitted by sam.halimi on Wed, 03/06/2019 - 02:43
Free User
Hi !
I have a problem with the script I installed for my Behringer X-Touch Mini.
The controller looks like this, basically (from top to bottom):
8 infinite knobs with led feedback (like the midi fighter twister)
16 buttons
Essentially I made a matrix of 16 mode selectors, mapped to the 16 buttons
Each mode being a different sampler in a drum rack
That makes it possible to control the 8 macros of the selected sampler
From the 8 infinite knobs
The basic idea works fine,
However, the problem I'm facing is that the LED indicators are not updating with every mode selection, they stay absolutely fix, no matter where the macro parameter is in reality, and they only update when I turn them
So that behaviour makes the parameters jump and make it unusable for performance!!!
For example,
My kick's volume is at -6b
From the kick mode, I make the volume go up to 0db
Then proceed to switch to snare mode
Say the snare is actually at -12db
The updating of the LED feedback does NOT occur
I still wanna change the volume of the snare but then it just jumps to the 0db that was left from controlling my kick!!
Any way I can fix that?
Help!
Thanks in advance
Sam
Topic Category:
Comments
Hi Sam,
It sounds like there could be 2 separate things going on here.
The first is the value jump,
to avoid this set your control's 'Takeover Mode' to either 'pickup' or 'value scaling'. They are probably set to 'None' at the moment. It is strange that you are experiencing this with Endless/limitless Knobs though, can you tell me the Velocity values which they send out when you turn them?
To update the LEDs, you will need to add reactions on each mode for your knobs.
We don't yet have listeners for Devices (which is what you will most likely need), but in the meantime here are some tutorials about them:
https://remotify.io/tutorials/sending-custom-led-feedback-your-midi-cont...
https://remotify.io/product/control-surface-studio/documentation/step-by...
We are working on a reference Doc with full details of Reaction values you can add - coming very soon.
Hi John,
Thanks a lot for the answer! I was able to change the behaviour of the knobs with the takeover mode, which I had never tried before, but it doesn't quite fix the problem.
For the velocity values, they change as I turn the knob from 0 to 127 progressively. Currently my knobs are set to Absolute values. Should I change that?
Also, excited to get documentation for the Reactions, because currently I don't really understand the possible variables of the coding language. When I tried the On/Off tutorial, so that my Mode Selector is lit when On, it just breaks the Mode Selector script altogether.
Sammy
"For the velocity values, they change as I turn the knob from 0 to 127 progressively. Currently my knobs are set to Absolute values. Should I change that?"
If your knob sends velocity values 0 to 127 then yes it should be set to Absolute.
"I was able to change the behaviour of the knobs with the takeover mode, which I had never tried before, but it doesn't quite fix the problem."
Did you try both 'pickup' and 'value scaling'? can you explain the behaviour of your knob with these?
You can find the Reactions Reference Guide here:
https://remotify.io/tutorials/reactions-reference-guide
Hi John,
I tried both pickup and value scaling. Pickup makes it so that when I switch modes, my knobs only start affecting the parameters once it reaches the value where the parameter is set prior to moving the knob. Value scaling makes it move right away, but I lose the speed of the movement, since there's latency in the reaction. I can't, for example, do any pitch bending on a drum sample (which I like to do as an automation).
Also, I noticed today, that overall there's a bug in the way the knobs move versus when I map them the traditional way. The CSS script makes the knobs turn very slowly and often without reaching the 127 value when they should (i.e. when my controller shows me I'm at 127).
"Also, I noticed today, that overall there's a bug in the way the knobs move versus when I map them the traditional way. The CSS script makes the knobs turn very slowly and often without reaching the 127 value when they should (i.e. when my controller shows me I'm at 127)."
I have this same issue with endless encoders. I posted here: https://remotify.io/community/question/endless-encoder-bug but John's solution didn't work for me. If I create the same encoders with the web app, the speed of movement is as expected.
Are there specific Mapping types (Volume, Sends Device Params etc) that you guys have experienced these issues with? (slow turning, not reaching 127).
I will try to recreate the issue.
In my case, I have 8 relative knobs assigned to the first 8 device parameters in Live,. When turning the knobs quickly the parameter in Live appears to "stall and jump", but resumes smooth movement when I slow down the turn.
I use a similar script built with the web app that does have this issue. I don't use a takeover mode in either script as it not the function I would like.
The controller is an Akai MPK261.
Thank you for looking into our issue!