Oh, the max length of input sysex messages for PD is actually more like 100 bytes for alsa and 120 for portmidi at least when I did my investigation a while ago. Still too small.
-Alex On Wed, Feb 3, 2010 at 10:25 AM, Alex <[email protected]> wrote: > I had sysex input and output working on my linux machine but I've had > a harddrive failure since then and haven't tried with the latest pd > build. > > I think I used [midiout] and I needed to use the ALSA midi instead of > portmidi, or something.. It has been a little while. > > One thing to note is that the size of the sysex input buffer is > limited to something like 23 bytes, I submitted a change to this but I > got little response as far as I can remember. It was just another > hard-coded higher limit though, the small limit makes PD pretty much > useless for parsing most midi sysex dumps like patch dumps from synths > [which is what I was trying to do, make a patch editor for the dave > smith instrument's evolver]. > > -Alex > > On Wed, Feb 3, 2010 at 10:04 AM, <[email protected]> wrote: >> I don't think sysex works on linux either; at least I'm trying to send using >> [midiout] using alsa midi and nothing is going through the interface, >> whereas [noteout] works fine. On Pd 0.42.5-extended2010105 debian lenny. >> I think I should be able to send a list like: >> >> [240 88 123 247( >> | >> [midiout] >> >> ...but it won't. >> >> Martin >> >> >>> Date: Wed, 3 Feb 2010 09:38:16 -0800 >>> From: [email protected] >>> To: [email protected]; [email protected] >>> Subject: Re: [PD] midiout / sysex on windows >>> >>> BTW, he is using pd 0.41.4-extended >>> >>> -Alex >>> >>> >>> On Tue, Feb 2, 2010 at 7:46 PM, Alex <[email protected]> wrote: >>> > I just tried this myself on a friend's windows machine running a >>> > relatively recent version of pd extended, though I'm not exactly sure >>> > which one.. >>> > it gave me an error >>> > MidiOut Error 1 >>> > whenever I tried to send a sysex message out. >>> > And there was an error about [sysexin] not being implemented on >>> > windows and [midiout] being dangerous.. I'm not sure if midiin worked >>> > with sysex or not because i couldn't get the sysex out.. >>> > >>> > Anyone know if this has changed or if there are plans to make sysex >>> > i/o work for windows? >>> > >>> > Thanks, >>> > Alex >>> > >>> > On Wed, Nov 11, 2009 at 7:23 AM, kristof lauwers >>> > <[email protected]> wrote: >>> >> hello, >>> >> >>> >> I was wondering what the current state of midiout is on windows (i'm >>> >> working >>> >> on Xp, but should make something that works under any recent windows >>> >> version) I see some discussion about it in the list archives and forum, >>> >> but >>> >> it's not clear if it should be working or not right now.. >>> >> >>> >> I tried it on vanilla PD 0.42.5 and in extended 0.4.3. It seems in >>> >> vanilla >>> >> it does nothing at all. In extended it's sending out something, but not >>> >> what >>> >> i expect.. (sometimes the 3 bytes i try to send each padded by 2 or 3 >>> >> 0's, >>> >> sometimes nothing at all..) >>> >> >>> >> Also, it's not very clear what kind of input midiout expects - the >>> >> documentation doesn't say anything about that.. i'd guess a list with >>> >> first >>> >> status byte and then the data bytes? >>> >> >>> >> if it's not working (yet), are there any alternatives to send sysexes >>> >> from >>> >> Pd? >>> >> >>> >> thanks, >>> >> >>> >> Kristof >>> >> >>> >> >>> >> >>> >> >>> >> _______________________________________________ >>> >> [email protected] mailing list >>> >> UNSUBSCRIBE and account-management -> >>> >> http://lists.puredata.info/listinfo/pd-list >>> >> >>> > >>> >>> _______________________________________________ >>> [email protected] mailing list >>> UNSUBSCRIBE and account-management -> >>> http://lists.puredata.info/listinfo/pd-list >> > _______________________________________________ Pd-dev mailing list [email protected] http://lists.puredata.info/listinfo/pd-dev
