[openbeos-midi] Re: MIDI parser source (bytestream->MIDI messages)

  • From: "Martijn Sipkema" <msipkema@xxxxxxxxxxxxxxxxxxx>
  • To: <openbeos-midi@xxxxxxxxxxxxx>
  • Date: Tue, 27 Jan 2004 18:42:07 +0100

I've attached the code that I remember working (in 2001 I think)...
You may use the code in any way you like and remove my copyright
notices. I hope it may be of some help.


----- Original Message ----- 
From: "Martijn Sipkema" <msipkema@xxxxxxxxxxxxxxxxxxx>
To: <openbeos-midi@xxxxxxxxxxxxx>
Sent: Tuesday, January 27, 2004 17:46
Subject: [openbeos-midi] Re: MIDI parser source (bytestream->MIDI messages)

Why not write a midi2 kit client for this. I once write one for the
AMT8/Unitor8 (or any other (multiport) serial interface). One
could write a kernel module for it I suppose, but I don't think
a seperate process should hurt performance that bad for it to
be an issue. And for multiport (using 0xf5) you will have to parse
and I don't think that should be in the kernel when it is not
necessary. I will try to find the code for the application and if I do
you can have the copyright as I'll most likely be ashamed of it :)


----- Original Message ----- 
From: "Matthijs Hollemans" <matthijs@xxxxxxxxxxxxxxxxxxx>
To: <openbeos-midi@xxxxxxxxxxxxx>
Sent: Tuesday, January 27, 2004 15:02
Subject: [openbeos-midi] Re: MIDI parser source (bytestream->MIDI messages)

Jerome wrote:
> If Matthijs are ok we can add that features in midi_server : not create
> only MidiEndpoint for Midiport of soundcard but with serial port too.

I don't think this should be in midi_server, but in a driver (from
/dev/midi). The driver would then read the bytes from the serial port, and
the midi_server would turn these bytes into MIDI messages, just like it does
for any other driver. There is no reason to make a special case for the
serial port, as far as I can see.

> PS : Happy new year

You too!


-- Binary/unsupported file stripped by Ecartis --
-- Type: application/x-compressed
-- File: unitor_server.zip

Other related posts: