Multiple MIDI ports?

Question

I decided to put my thoughts towards making a 16-channel version of 'Mickie', my MCU-compatible Layout...

What I've realised is that addressing more than 8 DAW channels under the MCU protocol is the result of the sending device presenting multiple MIDI ports to the receiver. In Cubase, this would be achieved by having two MCU remotes defined, and each receive from a separate MIDI port. Cubase determines that two MCU remotes are actually a master and an extender and magically begins working in banks of 16. I guess that other DAWs will do something similar.

I can create multiple ports in WinRtp, and I could presumably simultaneously connect to these ports in MD, but there's no option to determine which port an individual MD control sends to - I guess it would currently send to both.

And then I also began to see that if MD *could* separately address multiple ports then there's the potential for Layouts interfacing with multiple target devices. How about a Layout that controls five or six synths, achieved by appending Layouts and defining the port for each appended page/bank? An entire rig under one MD Layout!

At a lower level, if an individual MD control had the ability to target the port with which it is associated, then my 16-channel (or 24, or 32!) Mickie becomes a possibility.

I realise I'm probably asking for the moon on a stick, but... Maybe a consideration for the future? Or am I just talking nonsense?

Answer 1

Sort of a duplicate of 9662.  Going to add this as a reference for that user request in the database.

Request is to behave more like Ableton (for example), where you target input / output to a particular port as well as channel.

Trying to think how to deal with legacy layouts.  By default - all ports enabled for all controls?  Port control is an advanced feature?  Other ideas?

And the reverse problem - as soon as you start configuring to be very specific on ports, then you have the reconfigure problem if the interface changes - if you use Ableton or Logic for example, you know about having to reconfigure when plugging in a new device.  For example, my Jupiter X layout doesn't care which port the Jupe is on.  But if I have to specify, it could be found on:

• Jupiter Xm MIDI Out 1 / In 1
• Jupiter Xm Bluetooth
• via WIDI DIN adapter
• via a multi-unit adapter (iConnect Audio 4+, in my case)
• via a generic DIN adapter

Images

Ableton port example

Comments

Yep, I don't have all the answers. Just asking the question.

I don't use Ableton Live, so can't compare it. Cubase lets me know if a port is missing and I can choose an alternative port, either temporarily, or permanently.

Yep, I know I'm asking for something fundamental and seismic. Just thought I'd throw it out for consideration.

---

(BTW, what is '9662', and how would I find it?)

---

Hint - this post is 9991.

midiDr.com/qa/9662

---

Gotcha. I was thinking it was a reference I should be able to see in the forum posts.

---

Thought I'd bump this with a further thought that maybe an output port could be defined for a page (as opposed to individual controls) basis?

---

Pages are a problem because controls can be on multiple pages

While they rarely are, it's a bit of a mess...

Could probably do something like forcing all controls on a page to a certain port ;)

---

Yes, that's exactly what I'm thinking. That way it avoids having to set properties for every control, yet two sides of a Layout would be able to address two separate ports. I think that may be a good compromise.

Answer 2

Sort of a duplicate of 9662.  Going to add this as a reference for that user request in the database.

Request is to behave more like Ableton (for example), where you target input / output to a particular port as well as channel.

Trying to think how to deal with legacy layouts.  By default - all ports enabled for all controls?  Port control is an advanced feature?  Other ideas?

And the reverse problem - as soon as you start configuring to be very specific on ports, then you have the reconfigure problem if the interface changes - if you use Ableton or Logic for example, you know about having to reconfigure when plugging in a new device.  For example, my Jupiter X layout doesn't care which port the Jupe is on.  But if I have to specify, it could be found on:

• Jupiter Xm MIDI Out 1 / In 1
• Jupiter Xm Bluetooth
• via WIDI DIN adapter
• via a multi-unit adapter (iConnect Audio 4+, in my case)
• via a generic DIN adapter

Images

Ableton port example