AFAIK the current Linnstrument script in Bitwig is setting the internal value of how it interprets the incomming Pitch Bend to 24 with the line:Roger_Linn wrote:I should have mentioned that my test was conducted while turning off BW's remote control of LinnStrument's settings, which as I understand it is merely remotely setting LinnStrument's Bend Range to 24 and therefore shouldn't make any difference. I don't see the merit in BW setting it remotely because LinnStrument users may prefer a different bend range, especially given that the MPE spec now uses 48 as default. My understanding is that in order to achieve BW's real-pitch editing, all that should be needed is simply to 1) set BW's Input Bend Range in the Track Inspector to the same as your controller, and if using a plug-in synth, also 2) set BW's Output Bend Range in the Synth Inspector to the same as your synth. I don't see the need for anything more than that, or at least it seems that should be BW's main function. Am I missing something?
Code: Select all
noteInput.setUseExpressiveMidi(true, 0, [b]24[/b]);
The Roli Seaboard Script has a settable range, so the user can change it in preferences. This would be rather simple to transplant to the LS Script - or at least it was before 2.4 where Bitwig moved the LS script into the internal code space so it's no longer a user editable Java Script (if you don't copy the one from 2.3.x and give it a new GUID).
As soon as PB data has "entered" BWS this way, as I understand it, the range set in the script is what it uses to calculate the translation like BobDog said. You don't have to set an input range then nor set it to PB->Expression, since the line in the script does that for you. So what you see there isn't a bug but the way they intend it (automagic).
The only thing you need to do is set the VST synth to the range it supports in Inspector (if it doesn't speak automatic MPE).
I had a longer discussion with Support (I don't have a LS, only a Seaboard Block) and their aim is to make it fully automatic with no user intervention.
I personally do not believe in this kind of thing, since
a. Users like you say may prefer other ranges than 24 (which could be solved with a script with settable range like the Roli one)
b. The number of VSTs supporting full MPE with the automagic thing is close to zero and
c. Many users will be more interested in getting stuff not originally intended for MPE to work, so implementing a theoretically perfectly automatic MPE system that isn't flexible enough to deal with the current realities wouldn't be my personal choice.
But I think since Beta 4 almost everything actually works, but there is a LOT of confusion in the community since before it was partly broken, partly not there at all so many people using MPE try the wrong stuff and report things as broken that aren't.
Bitwig really needs to create a clear documentation on how the data flows and how things are intended to work with MPE now, so this confusion comes to an end.
Cheers,
Tom