Motif 1 vs Pad conflict (SOLVED)

[WaltCollinsMusic]

I think I've resolved this issue. In my settings for the MIDI output channels for each part in the NDLR, I had originally set them up as:

• Pad - USB 1, channel 1
  
• Drone - USB 1, channel 2
  
• Motif 1 - USB 1, channel 3
  
• Motif 2 - USB 1, channel 4
  

... which is the way I've set up many other pieces of multitimbral gear in the past.

But as I watched the MIDI notes come into the MPC from the various parts on the NDLR, if a note was the same as any other part, that part's sustain would terminate immediately, i.e. the MIDI "note off" message was being received by ALL channels, not just the one that sent it. This seems like a bug to me. Shouldn't "note off" messages (and presumably other MIDI messages as well) be restricted to the MIDI channel that sent them?

So that's when I thought about the purpose of having the virtual ports for USB 2, USB 3, and USB 4, since there's only a single physical USB port. Maybe they need to be manually isolated from each other in my settings? Yes, that seems to be the case.

Now I've got my ports configured like this:

• Pad - USB 1, channel 1
  
• Drone - USB 2, channel 1
  
• Motif 1 - USB 3, channel 1
  
• Motif 2 - USB 4, channel 1
  

... and everything now seems to work fine. Problem solved. This is what I presume others must be doing, but this is not what I would have expected based on my experience with other gear. To be honest, I consider this more of a workaround, not a solution.

Normally when using either a MIDI DIN or USB port, if you put a part on a different MIDI channel, it should not interfere in any way with messages sent over the same port, but which use a different MIDI channel. They should be isolated by default, and thus there should be no need for NDLR's virtual USB ports 2, 3, and 4.

Unless this is possibly by design? Maybe there's some reason why one would want MIDI "note off" messages to span across all channels. But I can't think of one.