Hello all,
The MIDI part of Siren is progressing nicely. The C-level scheduler and virtual channel map work, and I have a rudimentary patch editor that's a gas to use with QT musical instruments. I'm also hoping that the new primitive interface will be more portable than the first cut--most of the code (scheduler included) is quite portable (I believe), and there's a machine-dependent driver that has a simple API (thanks to Tobias Kunze of Stanford).
My question today is about sending MIDI over sockets. I plan to open a socket as one of the "standard" MIDI ports on start-up, and I assume that someone has already built applications that pass MIDI over sockets. Do any of you know of such work, what socket number was used, and if there were any special aspects to the MIDI packets that were transmitted? I think it would be great for Squeak to be able to be a network-based MIDI synthesizer!
stp
_ Stephen Travis Pope _ Center for Research in Electronic Art Technology (CREATE) _ Dept. of Music, Univ. of California, Santa Barbara (UCSB) _ stp@create.ucsb.edu, http://www.create.ucsb.edu/~stp/
(Did this get through before?)
Cool!
I don't know of any opinion on this issue by RFCs, but I've been running MIDI servers which listen for clients on port 7777 (in honor of a certain Urantian friend of mine :), and for other servers (it's a relay architecture) on port 6666 (servers do all the evil stuff :).
I don't know of any other related work that's open and/or public.
I've been meaning to be a more active collaborator on Siren since you announced it a few weeks ago, but I've had my hands full with demos demos demos at work... I should get some isolated free time on the 14th. It sounds like things are very interesting! :)
-C
-- Craig Latta composer and computer scientist craig.latta@netjam.org www.netjam.org latta@interval.com Smalltalkers do: [:it | All with: Class, (And love: it)]
squeak-dev@lists.squeakfoundation.org