Re: [sc-dev] [approve?] send MIDI clock messages in MIDIOut + sendmidi() cleanup

[Tim Kreger <tkreger@xxxxxxxxxxxxxx>]

Sysex capability would require some major upgrades/additions to the 
sendmidi() function as it currently only really deals with a  3 byte 
max  payload, one of which has to be a status byte.

midiProcessPacket would be more problematic to use for the same reasons 
mentioned  above.

Generally I think implementation of sysex would almost have to be  a 
seperate entity if it were to be done.

Cheers

Tim





On Monday, December 1, 2003, at 08:40  AM, James Harkins wrote:

> While we're at it, it would be very cool if MIDIIn and MIDIOut would 
> work with sysex information. I'd love to be able to read in the 
> heavily customized settings from my MIDI controller and archive them 
> using SuperCollider (and restore them, if need be). I bet I'm not 
> alone in that.
>
> Thanks --
> James
>
> On Sunday, Nov 30, 2003, at 02:44 US/Eastern, Ross Bencina wrote:
>
> > Tim K and I have added MIDI clock send support to MIDIOut, this 
> > required
> > cleaning things up to accomodate non-channel messages. See patch 
> > below. I'll
> > commit if a couple of days if there's no objections.
> ____________________________________
>
> H. James Harkins /// dewdrop_world
> http://www.duke.edu/~jharkins
>
> "If attacked by a lion, thrust your arm down his throat.
> This takes some practice."  -- Cyril Connolly
>
> _______________________________________________
> sc-dev mailing list
> sc-dev@xxxxxxxxxxxxxxx
> http://www.create.ucsb.edu/mailman/listinfo/sc-dev