With "Force MPE" or "Use MPE" BW takes the midi data and converts it to BW Expression data (Velocity, Timbre, Gain & pan), these can then be edited in the expression editor. For PB you get the advantage that the expression data maps nicely to actual pitch in the editor. If I move a note then the expression data moves with it, if I delete a note the expression data gets deleted.Tj Shredder wrote:But what is the difference between “force MPE” and the standard setting. What does it do to the information contained in my Midi information. Why are there two different modes at all???ThomasHelzle wrote: You can use it like Ardour if you want. Use a generic script that is letting everything through and it just works in 2.4.
Whatever It adds to Midi when I edit a sequence, I don’t see any need to trash information, it could simply keep it...
With these off it just stores the midi as automation data. You can then edit it in the midi automation editor. I may be wrong but unlike other DAWs that allow you to edit by channel, deleting notes or moving them in BW will not affect the data such as PB or brightness as it doesn't link this data to the notes. Also deleting a clip in session mode will not delete any of this data it is left hanging around.
So as it stands for just recording and playing back multichannel data turning MPE off works perfectly. If you want to edit the data, or use session view to record over the location of a deleted clip it isn't much use.
With MPE on currently there is a problem with the channels being remapped, if this is not a problem for you then this mode works the best. You can easily edit the expression data and the notes that contain it, deleting stuff works fine as well.