I just finished mapping everything on my Presonus Faderport to use it in FL studio. It came out really nice.

Now, I still have a small problem. While I can move the unit fader and the movement looks perfectly smooth on the fader on the screen, when I move the fader on the screen the unit fader acts jerky.

The problem lies in the fact I don't know how to convert Pitch Bend data into MSB LSB data.

If I use MSB only on the feedback going to the unit, I have the fader moving in big steps only...if I activate LSB the inbetween steps happen asynchronously so the fader moves super jerky. So I decided to leave it in "big steps" mode which is not so bad, but not optimal.

I'm sending a slow SAW to the software fader (range 0% to 100%)via internal controller, that makes the software fader to move and therefore send the return position data to the motorized fader.

Depending on how I scale I have:

graph.jpg (90.6 KiB) Viewed 35886 times

And what I try to avoid is that sawtooth motion you see in the middle. I must convert all these sawtooth cycles into one big sawtooth cycle that covers one MSB step so at the end when they're stitch together they all form a straight diagonal line.

That's why I guess I need some kind of counter or logic gating but have no clue about such syntax.

As I can see from the video, FL treats Pitch Bend as a flat 14-bit range from 7F 7F to 00 00 (LSB MSB top to bottom).

Looking at what the FP is sending, it seems a bit arbitrary. Note that it's OK for 14-bit controller messages to omit the MSB part if it is the same as before (that's why you only see occasional B0 00 pp messages). But there are intermittent B0 20 00 messages where they don't make sense.

No scaling necessary! This could be optimized to only send the B0 00 qq whenever qq actually changes, but it should work the same.

If this doesn't work, then the FP has some non-standard stuff for the fader. It seems that either the LSB or the MSB (if your video starts moving from top to bottom) are inverted. You can undo/redo the inversion by inserting such a rule:

In other words the scales don't match. around 8% on the software fader moves the physical fader all the way up.

If I move the software fader ultra slow I can see the translated messages are right as I can see how the LSB little steps move in the right way, is just the scale that is not right.

Any ideas on how to do that? I could divide MSB, by 14 seems to work and I see the fader doing big steps, but the LSB data is a bit more complicated (I guess) to scale. You can see in the graphic above how it behaves.

The funny thing is, that when I move the physical fader with my hand, the values are scaled 1:1 to the software fader...so it works perfectly when sending from FP to FL but the scale is small when sending from FL to FP

So first, rr is calculated, a smooth value that will get values from 0 (bottom) to 16383 (top). The line "rr=rr/14" is the scaling. You may need to experiment a bit here. Then, qq and pp are derived from the scaled rr.

Thanks for writing back. I downloaded your file last night, I haven't played around with it yet because I only have the classic version of MT. I'm downloading the Presonus Studio One Demo right now I'll let you know how it goes. I have also ordered an Alphatrack online hopefully should be here any day now. Just thought I'd go through the motions of learning how to program something in case I ever run into some non-native control surfaces again.

I managed to find one on ebay and it looks like it's in REALLY good condition!

I bought the Alphatrack just in case I couldn't get the Faderport running properly. I'm having serious trouble so far.

I've bought hardware before ie: Arturia KeyLab49, that wasn't a great control surface out of the box in Reason. But each time I've managed to find a way to make it work using some bloatware or someone else has posted a decent configuration somewhere. I use some of the Re-Touch Control Surfaces to link Maschine and Kong together in Reason.

The Faderport though, like I said, I'm not even receiving a response from the Fader or top couple of buttons. If it doesn't work in Studio One, which I'm pretty sure it will, I'll just take it back to the store I bought it from.

I did try and download a demo for ProTools the other week and use it with that but the demo just became way too much work with piracy protection ignition key type setups that I didn't end up following it through.

You need to put your Faderport in a certain mode, which AFAIK only Studio one does. SO you need Studio One Demo to make it go that mode (you only need to do it once, unless you turn the faderport off, which I don't)

From BMT you need to receive the signal from your faderport and go out thru MT1

In FL you need to setup both In and Out MT1 using port 101 and as an "Frontier design Alphatrack"

I've attached some images showing how it is all hooked up (I took them when I was at v1.7)

Here's an updated version, now you can use the faderport pedal input port to record immediately. Useful when you need both hands to play an instrument. I did this to be able to record guitar more efficiently.

The pedal I'm using is a BOSS FS-5U (is a momentary pedal, not toggle)

Press and hold pedal: Starts record

Lift pedal: Stops record.

There are a couple more translators, one to be able to convert VOL to MOD using my M-Audio keyboard pedal input (using an Ernie Ball VPJR to record string dynamics while playing for example) those you can just ignore if you want, but if you wanna use them the translator uses port BMT 2 (you must enable your keyboard to BMTP first and from BMPT to FL using that port)

You put the Faderport in "Studio One Mode" just by launching Studio One, if the faderport was already configured in the "external devices" inside the options then you're set. If the Faderport wasn't yet added there then you must do it manually (use the template provided by Presonus in that window)

Try making one song in Studio One, if you hit buttons (like play and stop) and Studio One responds then you're set....just close Studio One, wait for some seconds, like 10 (cause for some reason Studio One closes that slow)

Then open BMTP and set ports accordingly, same for FL.

If for some reason things aren't working yet, makes sure the ports you're using are right. Check with my screenshot above.

In the new BMTP version the project default ports are listed in the main window. Here's a screenshot, it should have the ones I've marked with arrows. I'm not sure but I think the new BMTP handles ports differently, they're embedded in the project and you don't need to set them up manually so I guess you must just open the file I gave you, ignore everything that has to do with gear you don't have and all you need to do is to set the ports in FL

28-Dec-15 10-18-26 PM.jpg (66.04 KiB) Viewed 20468 times

Note that in FL you must NOT enable the faderport directly, BMTP is doing that, then you manage the Faderport from FL via the virtual port 1 (BMT1)...these ports can have other names in your system (like Bome MIDI translator virtual port 1) but I'm using "short names" as in the last screenshot.

I think you need to get the full version cause the so called "rules" are not gonna work on the classic version. Rules are common in my faderport implementation, specially on the motorized fader.

Maybe Florian can chime in as I believe the full version 1.8 tries to open the appropriate ports automatically..tho I'm not sure 100%

You should set ports as it suggest in those boxes:

MIDI IN: Faderport
MIDI Out: MT1 (virtual port 1)

and second box:

MIDI In: MT1
MIDI Out: Faderport

I'm not completely sure, as my implementation is complex and also my ports are already set up so BMTP doesn't ask me for those anymore. You should experiment.

If BMTP (or FL) says something about "ports unavailable" or "being used" or "out of memory" is because the ports aren't set in the right order (I suggest you to assign ports in FL first exactly as in the screenshot above to make sure that side is right). Once you have them right everything should work, you should be able to control FL from your Faderport and conversely if you move a fader in the mixer or play in FL you should see the motorized fader moving or transport lights blinking.

Don't worry, it sounds all complicated but once is all set up all will work seamlessly and you'll not need to do it again. (at least until you reinstall windows)...once you got the ports right I suggest you to take more screenshots and have them handy in a future reinstall, that's what I did so I don't have to remember it all.

The "classic" edition is not suitable indeed, you need the Pro edition for this.

The trial version of the Pro edition should be fine, although you do need to restart it after 20 minutes trial time.

jpatterson, I'll contact directly to sort out the purchase problem

handling of MIDI port has not changed much for version 1.8, the settings are just rearranged to better match the logic.

To set up the MIDI ports, the FaderPort alias should be set to the Faderport input and output MIDI ports (just select them from the drop down lists). I'll fix the problem that the alias "FaderPort" appears twice in the list.

Hello everyone.... and thanks to all have posted assistance in getting Faderport to work in FL Studio 12.

I've downloaded the BMTP files and have my Faderport working with FL12, but for whatever reason I cannot move the fader physically and have it move the corresponding fader in FL. However, if I click and drag the fader with the mouse, the Faderport does move. Also, I can't seem to get the pan knob to work. Any further assistance is greatly appreciated and thank you in advance!!!

- Is FL running OR BMTP running with admin privileges? I run both without (also cause it gives problems with FL in other areas). It can happen that is one of them is in admin mode one cannot communicate to the other. Doubt is the problem but worth checking that out.

- In BMTP You can see on the right your MIDI in out ports as well as their aliases. You can try deleting some of them (keep a backup) and close/open MBTP so it asks you to assign the missing ports then you assign the right ones.

- Fixed the Solo button being lit as you mute a track. It works properly as you solo and mute.

It works better as before, however in special cases (going out from ALT solo to Mute) the mute button won't lit and you'll need to click again twice to make it work. I cannot do anything about it in BMTP I believe, all I see is that FL is not sending the required message during a special case in the mixer.

Instead is sending one message that I cannot use on both cases cause there will be a conflict in the two "S/C" (special case) MUTE LIGHT ON and OFF that prevents me from doing it right. I have no idea if a rule can help me given that there seems to be e piece of MIDI information missing from FL'S mixer.

I leaved the dummy extra translators, maybe someone can figure that out.

- As usual keep in mind there are other stuff related to my personal setup (such as the Keystation 88) so feel free to delete/disable those. There is an extra part so you can rescale an expression pedal in your keyboard.

I'm now working to see if I can reset the slider if I double tap on it. (EDIT: No idea...I sort of need an incoming sensor translator that detects a specific MIDI message occured twice within a certain time window)

I can trigger the timer manually although I cannot make the fader reset to the default 0dB position yet, only min or max. Communication is ok between the trigger and reset translators so at least that's working

I can't figure out why he used ga as global variable, where is ga getting his value from, I'm guessing ga=ga+1 but still, I'm not versed on this so I don't know why he uses ga while the receiver message is being used as pp.

Anyway, I think also that video relates to something different than what I need so I shouldn't take those rules to the letter.

If you have follow-on questions, feel free to open a new question on the new forum. I used ga as an arbitrary global variable for the demo. I typically use local variables like pp for things that do not need to be shared between translators. Since there are two translators, involved and variables need to be static. I just chose the first two available ga and gb.