Does anyone use endless encoders in FL Studio?

I bought EN16, and after finally receiving it I quickly realized that FL Studio doesn’t natively support relative inputs. It has to be done via a MIDI Script written in Python, but I don’t know where to start even.

The encoders are way too slow to use as an absolute pot, so I am stuck immediately after trying it out. :frowning:

Welcome to the forum!

I do have copy of FL Studio but I’ve never used it so I can’t help you there. However, you should take a look at the encoder_velocity() function as you can certainly tweak the velocity to make the encoders more usable in absolute mode:

Thanks for the welcome!

I will check out the velocity function, thanks for reminding me about that.

1 Like

Since last post I was looking around documentations to try to let FL Studio know it’s an increment control.

There’s an unintuitive problem on their side where telling it the midi signal is increment makes the value unusably big.

I threw a question on the forum but I got no responses, and it seems like there were some people who experienced the same problem and yet no solutions were found.

I am kind of frustrated…

I ended up making a script that’s working for FL Studio.
It converts the encoders into absolute encoders without the ends. And any adjustment made inside FL Studio is not causing the encoders to jump.

With FL Studio’s code not being able to properly handle relative encoders, I think this is the best second method one can have.

Here’s a link to the code, and how to set it up for use: FL Studio can’t process endless encoders. Here’s a fallback making them into absolute encoders.

I hope this helps.

1 Like