Yes, I am having it too. However, at least now you can make it work and don't get "robbed" of of 50% of pitch bend ranges for any software that doesn't support 48, like you did before. So it would be nice if they fix it, but it's just an irritant to me at this point.
I must say, as I've been working with Bitwig these last few days I have been really impressed by it's overall feature set. The touch implementation, for instance, is remarkable. I am seriously considering ditching 4 of my midi knob/slider controllers and going with touch all the way. I know it's not for everybody, but I never had a love affair with knobs anyway so I'm going to give it a go.
Bitwig 2.4 MPE fixed?
-
- KVRAF
- 1907 posts since 2 Apr, 2015
If everyone that is experiencing this could email BitWig about it maybe we can get it fixed: beta@bitwig.com
-
- KVRAF
- 2724 posts since 8 Jun, 2010
- Roger Linn Design
I haven't yet heard back from Bitwig but I think it's important to understand why they're doing what they're doing with Pitch Bend Range.
If I understand it correctly, Bitwig needs to know the Bend Range being used in order to implement what I think is a wonderful feature: In their editing screen, Pitch Bend editing is shown in real pitches and is associated with the affected note, instead of arbitrary Pitch Bend values as in other DAWs.
This also allows Bitwig to intelligently transpose and scale Bend data, and possibly affects the usefulness of other features that use Bend data.
So I like that Bitwig does this, but I find it difficult to work around their implementation when it doesn't meet my needs. So when they get back to me, I'll try to help them tweak their implementation so it's more flexible. Or at least once I understand better what they're doing under the hood, I can write a page explaining how to better work around it in special use cases.
If I understand it correctly, Bitwig needs to know the Bend Range being used in order to implement what I think is a wonderful feature: In their editing screen, Pitch Bend editing is shown in real pitches and is associated with the affected note, instead of arbitrary Pitch Bend values as in other DAWs.
This also allows Bitwig to intelligently transpose and scale Bend data, and possibly affects the usefulness of other features that use Bend data.
So I like that Bitwig does this, but I find it difficult to work around their implementation when it doesn't meet my needs. So when they get back to me, I'll try to help them tweak their implementation so it's more flexible. Or at least once I understand better what they're doing under the hood, I can write a page explaining how to better work around it in special use cases.
-
- KVRAF
- 1907 posts since 2 Apr, 2015
The strange thing is though all that nice stuff doesn't work at 48 or at 12.
With everything set at 48 BW sees half the range, with everything set at 12 it sees double the range. You can see this on the recorded clip. So basically something somewhere in BW is stuck at 24.
Setting everything to 24 makes it all work perfectly though, including the editing screen.
So the current "fix" is to just run everything at 24.
With everything set at 48 BW sees half the range, with everything set at 12 it sees double the range. You can see this on the recorded clip. So basically something somewhere in BW is stuck at 24.
Setting everything to 24 makes it all work perfectly though, including the editing screen.
So the current "fix" is to just run everything at 24.
-
- KVRAF
- 2724 posts since 8 Jun, 2010
- Roger Linn Design
Yes, it doesn’t work yet. It seems to internally force a bend range of 24 when LinnStrument s recognized as the controller. And if you connect LinnStrument through DIN MIDI so it can’t be identified, things get weirder.
Stay tuned and hopefully I’ll be able to help them improve the implementation and report good news.
Stay tuned and hopefully I’ll be able to help them improve the implementation and report good news.
-
- KVRAF
- 2724 posts since 8 Jun, 2010
- Roger Linn Design
Yes, it still seems to be problematic with any instrument due to the odd things going on under the hood.
-
- KVRAF
- 1907 posts since 2 Apr, 2015
Just did another test with a midi guitar, it is actually different to what we see with the Linnstrument, it is much worse, just seemingly random behaviour.
I also tried just using a normal midi keyboard, the pitchbend is screwed on that on playback as well. I think it is basically a bit broken!
I also tried just using a normal midi keyboard, the pitchbend is screwed on that on playback as well. I think it is basically a bit broken!
-
- KVRAF
- 1907 posts since 2 Apr, 2015
I have just done a series of tests with the Linnstrument, a Kronos as a controller and a Godin TriplePlay midi guitar.
If you use the BW synth devices everything works fine with pitchbend with all three input devices.
If you use a synth plugin then it isn't so good, the linnstrument seems to work when everything is set to 24, the Kronos recorded pitchbend is wrong on playback and the midi guitar is just madly all over the place, after a while the pitchbend starts oscillating, very weird.
So really for me with this version we are where we always have been, BW is ok if you use the inbuilt device and not so good with plugins.
Lets hope they sort it out and it's not another year waiting for this sort of stuff to work.
If you use the BW synth devices everything works fine with pitchbend with all three input devices.
If you use a synth plugin then it isn't so good, the linnstrument seems to work when everything is set to 24, the Kronos recorded pitchbend is wrong on playback and the midi guitar is just madly all over the place, after a while the pitchbend starts oscillating, very weird.
So really for me with this version we are where we always have been, BW is ok if you use the inbuilt device and not so good with plugins.
Lets hope they sort it out and it's not another year waiting for this sort of stuff to work.
-
- KVRAF
- 26985 posts since 3 Feb, 2005 from in the wilds
Yes, there is something odd going on... but just leave your Linnstrument at 24. There is no reason to change it. Even the bigger Linnstrument cannot quite do a 2 octave bend so higher values have no meaning.BobDog wrote:The strange thing is though all that nice stuff doesn't work at 48 or at 12.
With everything set at 48 BW sees half the range, with everything set at 12 it sees double the range. You can see this on the recorded clip. So basically something somewhere in BW is stuck at 24.
Setting everything to 24 makes it all work perfectly though, including the editing screen.
So the current "fix" is to just run everything at 24.
My MPE VST's are working fine for recording, editing and playback as long as the synth pitch range and device setting are the same...
-
- KVRAF
- 26985 posts since 3 Feb, 2005 from in the wilds
Ahh... yes, I have no experience with other controllers and Bitwig 2.4 beta. My Push doesn't work with the beta unless I download the latest beta script from Moss... my only other keyboard is packed up atm.BobDog wrote:Yeah I’m happy with 24, that’s not really a problem, I tend to use 12 but can get used to 24.
My problem is with other devices really, PB seems a little messed up in general.
What is the problem you are having with the Kronos?
-
- KVRAF
- 1907 posts since 2 Apr, 2015
When recording PB sounds fine, when playing back PB is halved so a 1 octave PB is turned into a 1/2 octave pitchbend. (this was with a 12 range)pdxindy wrote:Ahh... yes, I have no experience with other controllers and Bitwig 2.4 beta. My Push doesn't work with the beta unless I download the latest beta script from Moss... my only other keyboard is packed up atm.BobDog wrote:Yeah I’m happy with 24, that’s not really a problem, I tend to use 12 but can get used to 24.
My problem is with other devices really, PB seems a little messed up in general.
What is the problem you are having with the Kronos?
I need to spend some more time testing things out with different pitchbend ranges, maybe it''s like the linnstrument when only one range works correctly...
-
- KVRAF
- 1907 posts since 2 Apr, 2015
Hi Roger,
I have been having email correspondence with BW support about this issue, I think I have found the problem. Whatever value you set the BW MPE PB to it always records a 24 PB range into the clip.
You can test this out to see.
I am having some difficulty getting this fact over to them though, maybe it would be better coming from you as they just keep telling me it works. I am guessing they do not have a linnstrument available for testing.
Cheers
Andy
I have been having email correspondence with BW support about this issue, I think I have found the problem. Whatever value you set the BW MPE PB to it always records a 24 PB range into the clip.
You can test this out to see.
I am having some difficulty getting this fact over to them though, maybe it would be better coming from you as they just keep telling me it works. I am guessing they do not have a linnstrument available for testing.
Cheers
Andy