Things are not so simple with RTP-MIDI. The way it works is very different from classical MIDI approach with the IN/OUT/THRU.
First, you can perfectly build a setup where you have a single KissBox board on one side, and computers on the other. The KissBox modules can talk to each other, but also to computers. So it's not necessary two modules needed (apart if you want to make a MIDIBox talking to another MIDIBox over the network)
Second point : the particularity with RTP-MIDI is that it is based on the concept of session. A session represents a MIDI IN/OUT pair on application side. The difference with "classical" MIDI is that a single session handler can be connected to multiple session handlers in parallel (it's not KissBox specific, this is part of RTP-MIDI itself)
I will try to explain it simply : imagine that you have four RTP-MIDI devices on the network (A, B, C, D). When you want to exchange MIDI data, you need first to open a session (this is part of the firmware or the driver in case of the computer. You do not see it really, it's done transparently).
Let's say that A, B and C open a session with D (inside D sofware, there are "physically" four sessions then, it's not the same session shared between all participants). What is sent by A, B and C is sent automatically to the application, after ebing merged. In the other direction, what is send by application to D is sent automatically to A, B and C. In other terms, with RTP-MIDI, you do not need mergers and splitters, they are implicitely part of the protocol.
But B can also be connected virtually to C for example, etc...
This is called virtual patchbay
The current KissBox firmware supports 8 sessions in parallel so 8 devices (which can be computers, not only other KissBox CPU) can talk with a single MIOS application at the same time. The protocol we use on SPI allows up to 16 cables, so basically we can assume that a single RTP-MIDI node represents 16 MIDI cables at the same time (each of them with 16 MIDI channels of course)
The protocol we use on SPI uses the notion of Cable Number, which allows to identify the session sender. So, simply said, at a given moment, the MIOS application can see up to 8 devices, while there is only one physically connected....
Yes, I know, it's a bit hard to understand since there are many new concepts under RTP-MIDI. If you want, you can take a look on the download page of KissBox website, there are documents which explain more in detail how the configuration process works and what are the possibilities.
Sorry if I am not very clear, I work on RTP-MIDI since 2006, and many things are very clear for me, but not necessarily for newcomers in RTP-MIDI.
If you think that something needs to be explained more in detail, please ask, I will do my best to explain things simply.
(In two words, RTP-MIDI is transporting MIDI over IP networks, to take benefit from high speed from Ethernet, plus other new functionnalities like automatic merging/splitting). RTP-MIDI is completely license free, natively supported by Apple in OS-X and iOS, and there is a free driver for Windows too. It's also Plug&Play thanks to the use of Bonjour.
The concept is based on the use of the KissBox RTP-MIDI OEM board (http://www.kissbox.nl/products_oem.html), which translates the RTP-MIDI protocol into an high speed SPI based protocol (the protocol being simply the one used for USB transfers)
Of course, final users will not need to write their own RTP-MIDI application in the KissBox CPU board, I have written this part (Thorsten included the host part and tested it for the MIDIBox applications)
The first version is in beta state, we are now looking to optimize it, especially the SPI speed.
We will demonstrate the board at NAMM in Anaheim in two weeks, if you want to see it operating (we are located at booth 1088 in Hall E, for those who want to visit us)
If you have any comment or question, they are of course welcome
Benoit
(PS : yes, I am from KissBox, in case you are asking yourself )
I am hard to print pcb with the schema is correct there are some components pngganti like lf 33 I replace with lm3940 low drop regulator but I do not menggunan The KissBox RTP-MIDI OEM board but usb midi not detected dila in pairs in stm32f4 brakout ver221 with rtp midi readi this follows schenaticnya
MIDIbox goes RTP-MIDI...
in Design Concepts
Posted
choose files... Click to choose files
I am hard to print pcb with the schema is correct there are some components pngganti like lf 33 I replace with lm3940 low drop regulator but I do not menggunan The KissBox RTP-MIDI OEM board but usb midi not detected dila in pairs in stm32f4 brakout ver221 with rtp midi readi this follows schenaticnya