Re: MIDI parser source (bytestream->MIDI messages)

Matthijs Hollemans wrote:
> Truthfully, I'd like to get rid of libmidi2 altogether and replace it=20
> with something better (libmidi3!). The idea of having multiple MIDI nod=
es=20
> that can send and/or receive data is great, but the rest of the kit has=
=20
> many problems. Some you have already ran into, others you will soon :-)

Thanks for the encouragement. ;-) But I already realized that coding for=20
Midi2 can be... interesting. Is there a list of known bugs/problems?

> I put some design notes on my website once, but took that down when I=20
> moved to another ISP. That stuff will also find a new home on the new=20
> OpenBeOS website some day.

Let us know when you put it up, I'd be interested in reading your ideas.

> However, I am not a big MIDI expert and, to be honest, have no interest=
=20
> in developing a new Midi Kit. So if you feel like making your own super=
=20
> API, here's your chance :-) There is no reason why one couldn't write a=
=20
> new Midi Kit as a replacement for the current one, because the kit is=20
> completely isolated from the rest of the operating system.

I'll have to do much more MIDI programming on BeOS before I'll be able to=
=20
do API design, currently I can't really judge what should be done=20
better/differently. Well, I'll just wait 'til you post your ideas, maybe=20
inspiration will hit me when reading them. :)

Bye,
Chris