If the Faderport wasn't yet added there then you must do it manually (use the template provided by Presonus in that window) 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. Is like the fader send some intricate set of data in a specific order and I have no clue on how to translate E0 mm nn pitch bend data into that. When I capture the MIDI coming from the Faderport it shows this: Outgoing: MIDI B0 00 qq B0 20 mm (inverted again, otherwise works even worse)
Translator 5: FADER RETURN (doesn't work well, MSB works fine if I don't send LSB, I need to scale the LSB timing (clock) to match the Pitch expected values, a simple division is not enough) Outgoing: MIDI E0 tt vv (note the inversion here, the other way around doesn't work) Translator 3: FADER OUT (physical fader controlling software fader, it works fine) So probably as you can see here, I just deviced some kind of makeshift to make it "work" but obviously is not the best solution but I have no clue. So I decided to leave it in "big steps" mode which is not so bad, but not optimal. 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.
The problem lies in the fact I don't know how to convert Pitch Bend data into MSB LSB data. 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. I just finished mapping everything on my Presonus Faderport to use it in FL studio.
0 kommentar(er)
