MeldaProduction

goldglob · Post by **goldglob** » Sat Jun 30, 2018 9:50 pm

Thanks for the update. How strange, I guess Bitwig will need to look at this now.

frizzbee · Post by **frizzbee** » Sat Jun 30, 2018 9:55 pm

mevla wrote:Vojtech has found ... that Bitwig is sending the improper channel number. Bitwig sends the channel number + 1.

Don't you think this would already have attracted the attention of many other devs? I can say that there are no problems here regarding midi channels with Bitwig Demo and some of the synths (some of them show the channel & command of the input in a readout) I have in use...

mevla · Post by **mevla** » Sat Jun 30, 2018 10:40 pm

There's no problem with Vojtech's Bitwig install also. What I could be suspecting is the Bitwig/jackd/ALSA interaction, maybe. This is Linux. Bitwig uses ALSA for MIDI while it is configured for using jackd for audio. But jackd also does MIDI although Bitwig is not using it for MIDI, for some reason. There might be some problem there. Maybe. How many people are running MDrummer in Linux Bitwig ? Maybe not that much at all.

Here it is clear. When MDrummer is on Rhythm channel 1 the C-1 MIDI has no effect, when it is on channel 2, it works as expected. I tried on channel 3 and it does not work but then, I think now that's me who got to learn how to work with multiple channels.

Cheers.

MeldaProduction · Post by **MeldaProduction** » Sat Jun 30, 2018 10:57 pm

When a plugin receives channel 1 on one system and channel 2 on a different system while using the same project, it becomes all pretty fishy

. Anyways I'm not so surprised, MIDI standard is superold and these channels are a bit obscure, so my guess is that Bitwig devs just didn't get the convention used by the Linux drivers and/or got confused by the classic "all" channel, which doesn't really exist, it's just input filtering concept. MIDI defines channels from 0 to 15, while this is displayed as 1 to 16 to the users, so it's quite easy to get lost in that.

Btw. as usual, you probably don't see problems with other plugins, because most plugins don't really use channel at all.

DarkStar · Post by **DarkStar** » Sun Jul 01, 2018 2:32 pm

MIDI Spec, by J Glatt wrote:2.1.1 Voice Messages

NOTE: Although the MIDI Status byte counts the 16 MIDI channels as numbers 0 to F (i.e., 15), all MIDI gear (including computer software) displays a channel number to the musician as 1 to 16. So, a Status byte sent on MIDI channel 0 is considered to be on "channel 1" as far as the musician is concerned.

This discrepancy between the status byte's channel number, and what channel the musician "believes" that a MIDI message is on, is accepted because most humans start counting things from 1, rather than 0.

MeldaProduction · Post by **MeldaProduction** » Sun Jul 01, 2018 6:03 pm

That's exactly it

. The truth is, pretty much every indexing in software is done on 0 to cnt-1 basis, simply because it is more efficient. And then you need to decide what to preset to the users, usually index+1.

DarkStar · Post by **DarkStar** » Mon Jul 02, 2018 12:57 pm

And, in the MIDI messages themselves, you can store 0-15 values in 4 bits.

mevla · Post by **mevla** » Wed Sep 05, 2018 4:13 pm

It turns out that the issue was due to Bitwig's MPE feature enabled by default.

With MPE disabled, MDrummer (and Sample Tank 3) are now working properly.

All other synth plugins do not care about this, but MDrummer and ST3 are sensible to MIDI channels.

Cheers.

mevla · Post by **mevla** » Wed Sep 05, 2018 4:13 pm

It turns out that the issue was due to Bitwig's MPE feature enabled by default.

With MPE disabled, MDrummer (and Sample Tank 3) are now working properly.

Cheers.

MeldaProduction

KVR Audio

[SOLVED] MDrummer and Bitwig : MIDI commands broken ?