MIDI Network - Revision history

Riban: /* QmidiNet (IP Multicast) */

2023-04-18T06:25:00Z

QmidiNet (IP Multicast)

Jofemodo: /* Zynthian Network Configuration */

2020-04-07T01:00:21Z

Zynthian Network Configuration

Jofemodo: Created page with "The Zynthian can be controlled remotely via 2 different MIDI network protocols: ==RTP-MIDI== RTP-MIDI (IETF RFC 6295) is a specification for sending/receiving standard "MIDI..."

2020-04-07T00:58:59Z

Created page with "The Zynthian can be controlled remotely via 2 different MIDI network protocols: ==RTP-MIDI== RTP-MIDI (IETF RFC 6295) is a specification for sending/receiving standard "MIDI..."

New page

The Zynthian can be controlled remotely via 2 different MIDI network protocols:

==RTP-MIDI==

RTP-MIDI (IETF RFC 6295) is a specification for sending/receiving standard "MIDI 1.0" messages using standard networking protocols ("Real Time Protocol" and "Internet Protocol"). RTP-MIDI includes a data recovery mechanism (MIDI event journaling) to address packet loss that can occur on networks, eliminating the need for packet retransmission (which would increase latency and reduce throughput)

==QmidiNet (IP Multicast)==
[[File:Qmidinet-about.png|430px|right]]
[[File:Qmidinet-cli.png|400px|right]]
[[File:Webconf-midinetwork.png|430px|right]]

QmidiNet is a MIDI network gateway application that sends and receives MIDI data (ALSA Sequencer and/or JACK MIDI) over the network, using UDP/IP multicast. Inspired by multimidicast (https://llg.cubic.org/tools) and designed to be compatible with ipMIDI for Windows (https://nerds.de).

Once the network has been started on the zynthian, then you can communicate with it via tools like QMidiNet running in this case on a Linux desktop.

ANY MIDI event generated on ANY MIDI Channel that subscribes to the QmidiNet local network will be transferred to ALL other machines on that channel.

So in the above case the notes pressed on the remote zynthian machine ( connected by an ethernet cable to the laptop) appear as events on ALSA channel as displayed by an aseqdump terminal that has been connected to the QMIDINet instance running on the laptop, using aconnect to make the connection. This can all be examined using aconnect -l

This means that you have a high speed ( faster than original wired MIDI!) linking the two devices so you have no need of MIDI-USB or 5pin MIDI leads or any of that sort of physical stuff, all that is needed is an Ethernet connection between the devices.
Maybe a little different but as soon as you get a few devices on the network then you really start getting dividends. Remember the Network Traffic cis visible in the MIDI status as a BLUe M and can be examined using the MIDI Network display in the MII Log webconf section . .

But it's actually much simpler than that . . .

You can simply plug two zynthians together with an Ethernet Cable ( Raspberry Pi's can do this without needing a router), select Qmidinet to on on both devices and both will be able to play each other, or one can simply act as the MIDI controller for the other.
So you can have a MIDI KEyboard on stage plugged into a Zynthian and this can control a MIDI socket on another Zynthian up to a 100 Metres away . .

----

Why bring audio on to stage if you don't have too?

Simply connect two zynthians with an Ethernet cable!

==Zynthian Network Configuration==

They can be enabled and disabled as shown below.

The GUI ...
[[File:Networks.png|430px|right]]

Or The Webconf...
[[File:Webconf-networks.png|430px|right]]

and The MIDI Data flowing into a Zynthian can be confirmed by a Blue M in the status area and examined using the Webconf MIDI -logging display.

@@ Line 12: / Line 12: @@
 QmidiNet is a MIDI network gateway application that sends and receives MIDI data (ALSA Sequencer and/or JACK MIDI) over the network, using UDP/IP multicast. Inspired by multimidicast (https://llg.cubic.org/tools) and designed to be compatible with ipMIDI for Windows (https://nerds.de).
-Once the network has been started on the zynthian, then you can communicate with it via tools like QMidiNet running in this case on a Linux desktop.
+Once the network has been started on the Zynthian, then you can communicate with it via tools like QMidiNet running in this case on a Linux desktop.
 ANY MIDI event generated on ANY MIDI Channel that subscribes to the QmidiNet local network will be transferred to ALL other machines on that channel.
-So in the above case the notes pressed on the remote zynthian machine ( connected by an ethernet cable to the laptop) appear as events on ALSA channel as displayed by an aseqdump terminal that has been connected to the QMIDINet instance running on the laptop, using aconnect to make the connection. This can all be examined using aconnect -l
+So in the above case the notes pressed on the remote Zynthian machine (connected by an Ethernet cable to the laptop) appear as events on ALSA channel as displayed by an aseqdump terminal that has been connected to the QMIDINet instance running on the laptop, using aconnect to make the connection. This can all be examined using aconnect -l
-This means that you have a high speed ( faster than original wired MIDI!) linking the two devices so you have no need of MIDI-USB or 5pin MIDI leads or any of that sort of physical stuff, all that is needed is an Ethernet connection between the devices.
+This means that you have a high speed (faster than original wired MIDI!) linking the two devices so you have no need of MIDI-USB or 5-pin MIDI leads or any of that sort of physical stuff, all that is needed is an Ethernet connection between the devices.
-Maybe a little different but as soon as you get a few devices on the network then you really start getting dividends. Remember the Network Traffic cis visible in the MIDI status as a BLUe M and can be examined using the MIDI Network display in the MII Log webconf section . .
+Maybe a little different but as soon as you get a few devices on the network then you really start getting dividends. Remember the Network Traffic is visible in the MIDI status as a blue 'M' and can be examined using the MIDI Network display in the MIDI Log webconf section.
-But it's actually much simpler than that . . .
+But it's actually much simpler than that...
-You can simply plug two zynthians together with an Ethernet Cable ( Raspberry Pi's can do this without needing a router), select Qmidinet to on on both devices and both will be able to play each other, or one can simply act as the MIDI controller for the other.
+You can simply plug two Zynthians together with an Ethernet Cable (Raspberry Pi's can do this without needing a router), enable QmidiNet on both devices and both will be able to play each other, or one can simply act as the MIDI controller for the other.
-So you can have a MIDI KEyboard on stage plugged into a Zynthian and this can control a MIDI socket on another Zynthian up to a 100 Metres away . .
+So you can have a MIDI Keyboard on stage plugged into a Zynthian and this can control a MIDI socket on another Zynthian up to a 100 Metres away.
 ----
@@ Line 30: / Line 32: @@
 Why bring audio on to stage if you don't have too?
-Simply connect two zynthians with an Ethernet cable!
+Simply connect two Zynthians with an Ethernet cable!
 ==Zynthian Network Configuration==

@@ Line 36: / Line 36: @@
 They can be enabled and disabled as shown below.
-The GUI ...
+From the Zynthian-UI ...
 [[File:Networks.png|430px|right]]
-Or The Webconf...
+From the Webconf ...
 [[File:Webconf-networks.png|430px|right]]
-and The MIDI Data flowing into a Zynthian can be confirmed by a Blue M in the status area and examined using the Webconf MIDI -logging display.
+and the MIDI Data flowing into a Zynthian can be confirmed by a Blue M in the status area and examined using the Webconf MIDI-logger.