Yahoo Groups archive

Disklavier

Index last updated: 2026-04-28 23:20 UTC

Thread

OT: RTP MIDI standard

OT: RTP MIDI standard

2007-01-21 by James Fry

The question of whether it is possible to send MIDI over a TCP/IP 
network has been asked on the disklavier lists several times over the 
last couple of years, with no real concrete answers (although the RTP 
MIDI standard has been around in draft form for some time).

In November, the IETF formally issued the proposed standard for RTP MIDI 
as an RFC - details are available here 
http://www.cs.berkeley.edu/~lazzaro/rtpmidi/index.html

OSX already supports this protocol for its MIDI network driver. If we 
can find one for Windows, and a mechanism for Linux we could see an 
explosion of new MIDI tools.

Re: [disklavier] OT: RTP MIDI standard

2007-01-21 by George F. Litterst

Good morning, everyone.

There are both Macintosh and Windows solutions for MIDI over  
ethernet. However, they require a computer at the receiving end. This  
means that if you want to send MIDI to your Disklavier over ethernet  
from a computer in another part of your house, you need a computer  
connected to your Disklavier to receive the data and then pass it on  
to the Disklavier.

Regards,
PianoBench
Show quoted textHide quoted text
On Jan 21, 2007, at 1:44 PM, James Fry wrote:

> The question of whether it is possible to send MIDI over a TCP/IP
> network has been asked on the disklavier lists several times over the
> last couple of years, with no real concrete answers (although the RTP
> MIDI standard has been around in draft form for some time).
>
> In November, the IETF formally issued the proposed standard for RTP  
> MIDI
> as an RFC - details are available here
> http://www.cs.berkeley.edu/~lazzaro/rtpmidi/index.html
>
> OSX already supports this protocol for its MIDI network driver. If we
> can find one for Windows, and a mechanism for Linux we could see an
> explosion of new MIDI tools.

Re: [disklavier] OT: RTP MIDI standard

2007-01-21 by James Fry

Hello PianoBench,

Do these require ethernet or just tcp/ip? The latter is much more 
interesting (in my opinion) as I can run TCP/IP over more things than 
ethernet.

Do you have any links for the software do this? The ones I have found so 
far all use their own protocols (like the one I wrote) or aren't that 
easy to hook together with standard apps. For example, it would be nice 
to use Cubase upstairs with the disklavier downstairs, using a virtual 
midi driver (I can run long balanced mic cables to my piano, but MIDI is 
harder as long cable lengths don't work so well - using a network 
connection would be much easier).

The best so far to me look to be the ones based on this RTP standard.

Cheers,

James





George F. Litterst wrote:
Show quoted textHide quoted text
>
> Good morning, everyone.
>
> There are both Macintosh and Windows solutions for MIDI over
> ethernet. However, they require a computer at the receiving end. This
> means that if you want to send MIDI to your Disklavier over ethernet
> from a computer in another part of your house, you need a computer
> connected to your Disklavier to receive the data and then pass it on
> to the Disklavier.
>
> Regards,
> PianoBench
>
> On Jan 21, 2007, at 1:44 PM, James Fry wrote:
>
> > The question of whether it is possible to send MIDI over a TCP/IP
> > network has been asked on the disklavier lists several times over the
> > last couple of years, with no real concrete answers (although the RTP
> > MIDI standard has been around in draft form for some time).
> >
> > In November, the IETF formally issued the proposed standard for RTP
> > MIDI
> > as an RFC - details are available here
> > http://www.cs.berkeley.edu/~lazzaro/rtpmidi/index.html 
> <http://www.cs.berkeley.edu/%7Elazzaro/rtpmidi/index.html>
> >
> > OSX already supports this protocol for its MIDI network driver. If we
> > can find one for Windows, and a mechanism for Linux we could see an
> > explosion of new MIDI tools.
>
>

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.