My plan is simply never to make any incompatible change if I can help it - so midiout is there for good.
I don't see the need for any 'sysexout' object - 'midiout' does sysex and/or whatever else you want to throw at it. On linux you can even use it to output incorrectly formed MIDI if you want - for instance to stress-test MIDI input devices. cheers Miller On Thu, Jul 28, 2016 at 03:11:47PM +0200, Christof Ressi wrote: > Hi, > > what's the current status of the [midiout] object? there have been warnings > in the past and the help patch doesn't say much about it. > for example i found this old thread in the list archives: > > https://lists.puredata.info/pipermail/pd-list/2010-02/076074.html > > here Martin says: > > >> Shouldn't [midiout] be renamed to [sysexout]? It only does sysex, you > >> can't send any other kind of MIDI message with [midiout]. > > I'm on Win7 and [midiout] works like a charm. I can send both channel and > system messages (though I have only tried system common and system realtime > so far, still have to test sysex). I can easily play MIDI files with > [mrpeach/midifile] -> [drip] -> [midiout] on my old Roland D110 :-). > > my question is: have all those supposed issues with [midiout] been fixed? > does it work the same way on all systems? are there any pitfalls I have to > consider beforehand? > > @Miller: would you mind adding a note to the helpfile that [midiout] only > accepts single characters as floats but no lists? it took me some time to > figure that out... or even better: adding a list method? ;-) > > Christof > > _______________________________________________ > [email protected] mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
