Zebra 3 MPE in Bitwig?

[killmaster]

Hi there,

I posted this to the Zebra 3 thread and thought it might go better here since different DAWs have different ways of handling MPE. Here is my question:

I have some mental block about how to setup Zebra in Bitwig. I want to make sure I'm not missing anything since I just started using MPE alot lately.

Plunk Zebra 3 on a track
Set device header to "Use MPE"
Set track header to "Same"
Set Pitches->Pitch Bend to MPE for Up and Down

Is that it?

Thanks,

Greg

[pdxindy]

Hi there,

I posted this to the Zebra 3 thread and thought it might go better here since different DAWs have different ways of handling MPE. Here is my question:

I have some mental block about how to setup Zebra in Bitwig. I want to make sure I'm not missing anything since I just started using MPE alot lately.

Plunk Zebra 3 on a track
Set device header to "Use MPE"
Set track header to "Same"
Set Pitches->Pitch Bend to MPE for Up and Down

Is that it?

Thanks,

Greg

Why are you using the Zebra 3 VST3 version instead of CLAP?

[killmaster]

Hi there,

I posted this to the Zebra 3 thread and thought it might go better here since different DAWs have different ways of handling MPE. Here is my question:

I have some mental block about how to setup Zebra in Bitwig. I want to make sure I'm not missing anything since I just started using MPE alot lately.

Plunk Zebra 3 on a track
Set device header to "Use MPE"
Set track header to "Same"
Set Pitches->Pitch Bend to MPE for Up and Down

Is that it?

Thanks,

Greg

Why are you using the Zebra 3 VST3 version instead of CLAP?

No reason. Could be ignorance. Why should I use CLAP instead?

[monolithx]

... since different DAWs have different ways of handling MPE...

Why are you using the Zebra 3 VST3 version instead of CLAP?

Being CLAP or not not, MPE is badly documented and poorly configurable in general in audio tools. From my understanding as VST, MPE flag in Bitwig just split channels arbitrary (and maybe does something with channel 1?). If your input is already MPE, they are just 16 midi channels for Bitwig and it's Zebra responsibilty to dispatch things internaly as MPE (-48/+48) setting. So, I think MPE flag is useless in this case. And even could be worst as you have no control on Bitwig MPE channel remapping.

[pdxindy]

Why are you using the Zebra 3 VST3 version instead of CLAP?

No reason. Could be ignorance. Why should I use CLAP instead?

With CLAP, you don't need to configure MPE in Bitwig.

Plus of course Bitwig's Note Expressions and Poly Modulation also works with the CLAP version.

[monolithx]

There are anyway two sides, the device and the player. So customization is important. Is there any doc regarding MPE implementation in Bitwig? I just saw a blackbox MPE button that I never saw any technical explanation about it. I have spend much time monitoring MPE with 3rd party tools in Bitiwig.
If anyone can tell me if MPE button is needed for MPE controllers, I would be happy to see specs and what it does with an MPE input signal?

[Tj Shredder]

The one thing one must understand in Bitwig, is the relations between Midi, expressions and the script for the controller.
If you use a dedicated script for your controller, it will translate MPE to note expressions. But most plugins just deal with Midi. Even those which support MPE. Thus that switch in the instruments inspector for MPE. You also need to set the Midi channel information to all->same…
But U-He CLAP plugins do read note expressions correctly, thus in this case the CLAP version is the one you should use in Bitwig. The VST version needs the above mentioned settings and does not provide the per note modulation of CLAP

[killmaster]

The one thing one must understand in Bitwig, is the relations between Midi, expressions and the script for the controller.
If you use a dedicated script for your controller, it will translate MPE to note expressions. But most plugins just deal with Midi. Even those which support MPE. Thus that switch in the instruments inspector for MPE. You also need to set the Midi channel information to all->same…
But U-He CLAP plugins do read note expressions correctly, thus in this case the CLAP version is the one you should use in Bitwig. The VST version needs the above mentioned settings and does not provide the per note modulation of CLAP

Thanks for this!

[monolithx]

But U-He CLAP plugins do read note expressions correctly

Do you mean that an MPE compatible VST receiving a correct MPE flow (per channel+expression) doesn't read it correctly?

[pdxindy]

But U-He CLAP plugins do read note expressions correctly

Do you mean that an MPE compatible VST receiving a correct MPE flow (per channel+expression) doesn't read it correctly?

VST synths don't support Bitwig's Note Expressions or Poly Modulation. The u-he CLAP synths do.

[BobDog]

Just to get my head around this:

VST3 synths and Bitwig "MPE" should work fine shouldn't they?

VST3 has per note "expression"? Bitwig supports VST3 note "expression"?

CPLAP poly modulation is a different thing?

[Tj Shredder]

The problem is, that Bitwig prevents the conversion of note expressions into Midi MPE when you load a CLAP plugin. If the plugin only reacts on Midi MPE and ignores note expressions, you need to fall back to VST3 to get MPE correctly…
There is simply more than Midi in the plugin world…
Or you use a generic script that keeps Midi as Midi and does not convert MPE to expressions…