MPE with Hardware Synths

[BobDog]

I have recently been in conversation with BW support about the 24PB limitation with the linnstrument(any other range doesn't work), its like banging your head against the wall!

All they said (repeatedly) was it works there. I offered to make a video to send them showing the issue (after sending images that showed the problem) and have heard nothing since then.

Maybe I'm not talking to the guy that listens!

[Hez]

They've fixed that now though! Are you using the latest beta? You can set any pitch bend range between 12 semitones and 96 when sending MPE to VSTs. I can now leave my Linnstrument set on 24 semitones and configure it for whatever quickly with one click + drag in Bitwig.

[BobDog]

I have found possible bug that also makes testing this quite hard.

Record a clip with PB info in it, then delete the clip.

PB (And CC) automation data is left on the track.

The next time you record a new clip onto the track the existing automation is also played as well as the new automation being recorded, this leads to garbage being sent out.

Is this a bug or am I missing some setting somewhere?

[BobDog]

After deleting clip:

[pdxindy]

I have recently been in conversation with BW support about the 24PB limitation with the linnstrument(any other range doesn't work), its like banging your head against the wall!

All they said (repeatedly) was it works there. I offered to make a video to send them showing the issue (after sending images that showed the problem) and have heard nothing since then.

Maybe I'm not talking to the guy that listens!

You are spending more time arguing why you aren't going to send in bug reports than it takes to send in the bug reports!!

[BobDog]

And another rather serious bug, anyone can test this?

Use any midi controller with a pitch bend.

Add a midi track to BW and turn off "PB->Expression" so it records the PB.

Now record and gradually move the pitchbend wheel or whatever up, BW reaches full 100% PB when the PB sent by the device is only 4096 anything over half way is ignored, so 4097 to 8192 is all treated as 100%.

That is a pretty serious bug!

[BobDog]

I have recently been in conversation with BW support about the 24PB limitation with the linnstrument(any other range doesn't work), its like banging your head against the wall!

All they said (repeatedly) was it works there. I offered to make a video to send them showing the issue (after sending images that showed the problem) and have heard nothing since then.

Maybe I'm not talking to the guy that listens!

You are spending more time arguing why you aren't going to send in bug reports than it takes to send in the bug reports!!

Don't worry I am going to send them a document will all these findings. To be honest it is so buggy I'm sure they know of the problems and thats from someone that has worked in software development for over 30 years.

[pdxindy]

I have recently been in conversation with BW support about the 24PB limitation with the linnstrument(any other range doesn't work), its like banging your head against the wall!

All they said (repeatedly) was it works there. I offered to make a video to send them showing the issue (after sending images that showed the problem) and have heard nothing since then.

Maybe I'm not talking to the guy that listens!

You are spending more time arguing why you aren't going to send in bug reports than it takes to send in the bug reports!!

Don't worry I am going to send them a document will all these findings. To be honest it is so buggy I'm sure they know of the problems and thats from someone that has worked in software development for over 30 years.

I don't disagree with what you are saying... however, the more people who mention it, increases the chances of it being corrected sooner rather than later!

[Hez]

And another rather serious bug, anyone can test this?

Use any midi controller with a pitch bend.

Add a midi track to BW and turn off "PB->Expression" so it records the PB.

Now record and gradually move the pitchbend wheel or whatever up, BW reaches full 100% PB when the PB sent by the device is only 4096 anything over half way is ignored, so 4097 to 8192 is all treated as 100%.

That is a pretty serious bug!

I can't reproduce this - working fine with a Nektar Panorama P4 using the controller script.

[Hez]

I have found possible bug that also makes testing this quite hard.

Record a clip with PB info in it, then delete the clip.

PB (And CC) automation data is left on the track.

The next time you record a new clip onto the track the existing automation is also played as well as the new automation being recorded, this leads to garbage being sent out.

Is this a bug or am I missing some setting somewhere?

Yeah this is a bit peculiar.

1.) I can't remember whether Bitwig always left automation in place when you delete a clip? I think it always did tbh, which can be annoying in some situations but useful in others.

2.) It correctly overwrites the previous MIDI CC if you record over the existing automation, however, while you're recording it seems to try to play back the previous MIDI CC as it's overwriting it which is kinda irritating.

EDIT: The overdub behaviour definitely feels a bit strange in this release, yes.

[BobDog]

And another rather serious bug, anyone can test this?

Use any midi controller with a pitch bend.

Add a midi track to BW and turn off "PB->Expression" so it records the PB.

Now record and gradually move the pitchbend wheel or whatever up, BW reaches full 100% PB when the PB sent by the device is only 4096 anything over half way is ignored, so 4097 to 8192 is all treated as 100%.

That is a pretty serious bug!

I can't reproduce this - working fine with a Nektar Panorama P4 using the controller script.

Hi Hez,

Thanks for checking.

I Know it's a pain but could you remove the P4 controller script and add your P4 as a "Keyboard + 8 device knobs" and then test again, this will tell us if it is script related or something with my setup here.

[BobDog]

I have found possible bug that also makes testing this quite hard.

Record a clip with PB info in it, then delete the clip.

PB (And CC) automation data is left on the track.

The next time you record a new clip onto the track the existing automation is also played as well as the new automation being recorded, this leads to garbage being sent out.

Is this a bug or am I missing some setting somewhere?

Yeah this is a bit peculiar.

1.) I can't remember whether Bitwig always left automation in place when you delete a clip? I think it always did tbh, which can be annoying in some situations but useful in others.

2.) It correctly overwrites the previous MIDI CC if you record over the existing automation, however, while you're recording it seems to try to play back the previous MIDI CC as it's overwriting it which is kinda irritating.

EDIT: The overdub behaviour definitely feels a bit strange in this release, yes.

Yep that is what I seeing as well so for the PB it sends out the old value, then the currently recording value, so it oscillates between the two.

[Hez]

And another rather serious bug, anyone can test this?

Use any midi controller with a pitch bend.

Add a midi track to BW and turn off "PB->Expression" so it records the PB.

Now record and gradually move the pitchbend wheel or whatever up, BW reaches full 100% PB when the PB sent by the device is only 4096 anything over half way is ignored, so 4097 to 8192 is all treated as 100%.

That is a pretty serious bug!

I can't reproduce this - working fine with a Nektar Panorama P4 using the controller script.

Hi Hez,

Thanks for checking.

I Know it's a pain but could you remove the P4 controller script and add your P4 as a "Keyboard + 8 device knobs" and then test again, this will tell us if it is script related or something with my setup here.

No worries. Just deactivated the panorama script and used the generic one for it and pitch bend still working fine for me.

[BobDog]

Hi Hez, thanks for that.

Are you on a PC, Mac or Linux?

Do you have Max/MSP by any chance, I have a patch I have been using for testing that you could try?

Cheers

Andy

[BobDog]

I made a video for BW showing the problem, you can see it here:

The top right is the MAX Patch with a slider to control pitchbend, underneath that is a MidiMonitor application showing the pitchbend coming out of the patch and into bitwig.