[pknopf]

I don't know how it would be if they are switching from 8 bit to 32 bit.

I imagine most devices that come with MIDI 2.0 will have an option to run in either 1 or 2.

[Rochus]

The physical layer is completely different; Midi 1.0 was a current loop with DIN five-pin connectors; Midi 2.0 uses Ethernet and Wifi.

[LegitShady]

The physical layer is the easiest thing to get an adapter for. It's the logic and processing that is hard to make cross/back compatible.

[romwell]

>The physical layer is the easiest thing to get an adapter for

Oh really? Riddle me this, then: a MIDI controller has a USB port. A synth has a USB port.

Connect the two without using an external power source for the adapter (Hint: you can't).

[LegitShady]

You're actually proving my point, rather than disproving it. Thanks, I guess?

[romwell]

What's your point? (And how do you define the physical layer?)

The data transmitted over MIDI and USB MIDI is the same, it's not the problem. It's the same protocol.

The problem is that MIDI OUT on a MIDI controller supplies power, and USB midi out on a device DOES NOT, because it's a slave device.

This a physical layer problem no matter how you slice it.

Now go and read the question I asked again.

[LegitShady]

You're talking like what you say isn't the same thing I already said. Maybe re-read what I said that you replied to from the beginning.

[Rochus]

I don't think that the new 32 bit packet based protocol will run over the 31kBit/s current loop.