[midiin] is supposed to output all kinds of midi messages. also, the object [sysexin] is actually derived from [midiout].
Gesendet: Sonntag, 31. Juli 2016 um 22:04 Uhr Von: "Alexandre Torres Porres" <[email protected]> An: "Christof Ressi" <[email protected]> Cc: Pd-List <[email protected]> Betreff: Re: [PD] current status of [midiout] another question, does [midiin] receive sysex messages? cheers 2016-07-29 6:53 GMT-03:00 Christof Ressi <[email protected]>:I think there seems to be a misunderstanding. I never advocated to rename [midiout] to [sysexout] - on the contrary! I used an old post by Martin to show that in the past [midiout] used to be broken on some systems or behave differently. For example, Martin apparantly could only send sysex, but no channel messages. For me on Win7 [midiout] works fine in a way that I can send *all* kind of valid MIDI messages. I just wanted to make sure that this is now the case for all major systems. regarding a list method for [midiout]: since all popular objects for streaming bytes [netsend -b], [udpsend], [comport], etc. accept lists, it is somewhat counterintuitive that this is not the case for [midiout]. if you want to keep this kind of special behaviour, it would be cool to make it clear in the help patch - to prevent future users from tearing their hair out :-) Christof > Gesendet: Freitag, 29. Juli 2016 um 02:11 Uhr > Von: "Miller Puckette" <[email protected][[email protected]]> > An: "Christof Ressi" <[email protected][[email protected]]> > Cc: Pd-List <[email protected][[email protected]]> > Betreff: Re: [PD] current status of [midiout] > > 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[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][[email protected]] mailing list > > UNSUBSCRIBE and account-management -> > > https://lists.puredata.info/listinfo/pd-list[https://lists.puredata.info/listinfo/pd-list] > _______________________________________________ [email protected][[email protected]] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list[https://lists.puredata.info/listinfo/pd-list] _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
