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 pd@kristoflauwers.domainepublic.net 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
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
BTW, he is using pd 0.41.4-extended
-Alex
On Tue, Feb 2, 2010 at 7:46 PM, Alex x37v.alex@gmail.com 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 pd@kristoflauwers.domainepublic.net 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
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
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: x37v.alex@gmail.com To: pd-list@iem.at; pd-dev@iem.at 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 x37v.alex@gmail.com 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 pd@kristoflauwers.domainepublic.net 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
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
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, martin.peach@sympatico.ca 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: x37v.alex@gmail.com To: pd-list@iem.at; pd-dev@iem.at 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 x37v.alex@gmail.com 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 pd@kristoflauwers.domainepublic.net 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
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
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 x37v.alex@gmail.com 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, martin.peach@sympatico.ca 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: x37v.alex@gmail.com To: pd-list@iem.at; pd-dev@iem.at 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 x37v.alex@gmail.com 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 pd@kristoflauwers.domainepublic.net 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
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
I've had trouble getting sysex working in anything except linux using the classic "oss" interface. It's on my long do-list to try again with the other platforms...
cheers Miller
On Wed, Feb 03, 2010 at 10:29:58AM -0800, Alex wrote:
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 x37v.alex@gmail.com 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, ?martin.peach@sympatico.ca 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: x37v.alex@gmail.com To: pd-list@iem.at; pd-dev@iem.at 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 x37v.alex@gmail.com 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 pd@kristoflauwers.domainepublic.net 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
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On linux with alsa midi, sysex output works this way:
bang | [t b b b b] | | | | [247( [123( [88( [240( |_____|_____|____| | | [midiout]
That is, banging all the values separately into [midiout] during one message time slot. (Note the message is written backwards since the first byte to transmit is the sysex status byte, 240) Banging them in one at a time manually only sends one byte, banging them in as a list stops [midiout] from working until you reopen the patch.
Martin
martin.peach@sympatico.ca a écrit :
On linux with alsa midi, sysex output works this way:
bang | [t b b b b] | | | | [247( [123( [88( [240( |_____|_____|____| | | [midiout]
this is the same than :
[240, 88, 123, 247( (with coma)
c
That is, banging all the values separately into [midiout] during one message time slot. (Note the message is written backwards since the first byte to transmit is the sysex status byte, 240) Banging them in one at a time manually only sends one byte, banging them in as a list stops [midiout] from working until you reopen the patch.
Martin
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
I wrote a little abstraction that does list -> sysex and another one that does sysex input -> list They're in the list archives...
-Alex
On Wed, Feb 3, 2010 at 1:52 PM, cyrille henry ch@chnry.net wrote:
martin.peach@sympatico.ca a écrit :
On linux with alsa midi, sysex output works this way:
bang | [t b b b b] | | | | [247( [123( [88( [240( |_____|_____|____| | | [midiout]
this is the same than : [240, 88, 123, 247( (with coma)
c
That is, banging all the values separately into [midiout] during one message time slot. (Note the message is written backwards since the first byte to transmit is the sysex status byte, 240) Banging them in one at a time manually only sends one byte, banging them in as a list stops [midiout] from working until you reopen the patch.
Martin
_______________________________________________ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
They're called list2sysex and sysex2list btw.
-Alex
On Wed, Feb 3, 2010 at 4:21 PM, Alex x37v.alex@gmail.com wrote:
I wrote a little abstraction that does list -> sysex and another one that does sysex input -> list They're in the list archives...
-Alex
On Wed, Feb 3, 2010 at 1:52 PM, cyrille henry ch@chnry.net wrote:
martin.peach@sympatico.ca a écrit :
On linux with alsa midi, sysex output works this way:
bang | [t b b b b] | | | | [247( [123( [88( [240( |_____|_____|____| | | [midiout]
this is the same than : [240, 88, 123, 247( (with coma)
c
That is, banging all the values separately into [midiout] during one message time slot. (Note the message is written backwards since the first byte to transmit is the sysex status byte, 240) Banging them in one at a time manually only sends one byte, banging them in as a list stops [midiout] from working until you reopen the patch.
Martin
_______________________________________________ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Yes, why not just send a list though?
It seems that in WinXP [midiout] sends 247(start sysex) followed by 240(end sysex), the intervening message doesn't get transmitted. Also if the message contains numbers > 127 then more bytes get transmitted, not good.
Also as lists seem to be easier to generate than comma separated messages, and a list already has its buffer allocated, there is no need to reserve 1000 or so bytes just in case. Maybe someone should add a list method to [midiout]?
Maybe rename it to [sysexout] and skip the need to put 247 and 240 in every message...
Martin
cyrille henry wrote:
martin.peach@sympatico.ca a écrit :
On linux with alsa midi, sysex output works this way:
bang | [t b b b b] | | | | [247( [123( [88( [240( |_____|_____|____| | | [midiout]
this is the same than : [240, 88, 123, 247( (with coma)
c
That is, banging all the values separately into [midiout] during one message time slot. (Note the message is written backwards since the first byte to transmit is the sysex status byte, 240) Banging them in one at a time manually only sends one byte, banging them in as a list stops [midiout] from working until you reopen the patch.
Martin
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
hi,
i made an abstraction [sysexout] ;) - but i dont have hardware here to test it. so please do. g.
Martin Peach:
Yes, why not just send a list though?
It seems that in WinXP [midiout] sends 247(start sysex) followed by 240(end sysex), the intervening message doesn't get transmitted. Also if
240 and 247 are in the wrong order here according to the previous messages ...
the message contains numbers > 127 then more bytes get transmitted, not good.
Also as lists seem to be easier to generate than comma separated messages, and a list already has its buffer allocated, there is no need to reserve 1000 or so bytes just in case. Maybe someone should add a list method to [midiout]?
Maybe rename it to [sysexout] and skip the need to put 247 and 240 in every message...
Martin
cyrille henry wrote:
martin.peach@sympatico.ca a écrit :
On linux with alsa midi, sysex output works this way:
bang | [t b b b b] | | | | [247( [123( [88( [240( |_____|_____|____| | | [midiout]
this is the same than : [240, 88, 123, 247( (with coma)
c
That is, banging all the values separately into [midiout] during one message time slot. (Note the message is written backwards since the first byte to transmit is the sysex status byte, 240) Banging them in one at a time manually only sends one byte, banging them in as a list stops [midiout] from working until you reopen the patch.
Martin
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
#N canvas 749 434 450 285 10; #X obj 14 -75 inlet; #N canvas 0 0 450 300 list-drip 0; #X obj 73 94 t a a; #X obj 73 251 spigot; #X obj 112 159 bang; #X obj 112 178 1; #X obj 233 159 route bang; #X obj 193 160 bang; #X obj 193 179 0; #X obj 112 124 list split 2; #X obj 242 389 list split; #X obj 309 338 list length; #X obj 309 360 >> 1; #X obj 73 270 t a a a a; #X obj 73 456 list split; #X obj 140 408 list length; #X obj 140 433 >> 1; #X obj 41 29 inlet; #X obj 300 185 outlet; #X text 83 29 Copyright 2009 by Mathieu Bouchard; #X obj 41 63 t b a; #X obj 475 129 outlet; #X text 530 131 signal end of list; #X text 391 33 made compatible with [list-drip]: fbar 2009; #X connect 0 0 1 0; #X connect 0 1 7 0; #X connect 1 0 11 0; #X connect 2 0 3 0; #X connect 3 0 1 1; #X connect 4 1 16 0; #X connect 5 0 6 0; #X connect 6 0 1 1; #X connect 7 0 2 0; #X connect 7 2 4 0; #X connect 7 2 5 0; #X connect 8 0 0 0; #X connect 9 0 10 0; #X connect 10 0 8 1; #X connect 11 0 12 0; #X connect 11 1 13 0; #X connect 11 2 8 0; #X connect 11 3 9 0; #X connect 12 1 0 0; #X connect 13 0 14 0; #X connect 14 0 12 1; #X connect 15 0 18 0; #X connect 18 0 19 0; #X connect 18 1 0 0; #X restore 14 11 pd list-drip; #X obj 14 -32 t a b b; #X msg 76 81 add2 $1; #X msg 14 81 addcomma; #X obj 14 54 t b f; #X msg 293 61 addcomma; #X obj 83 35 t b b; #X obj 14 183 midiout; #X msg 178 126 add2 247; #X msg 364 61 set 240; #X obj 394 -75 inlet; #X msg 14 150; #X text 268 179 by Georg Werner 2010; #X connect 0 0 2 0; #X connect 1 0 5 0; #X connect 1 1 7 0; #X connect 2 0 1 0; #X connect 2 1 6 0; #X connect 2 2 10 0; #X connect 3 0 12 0; #X connect 4 0 12 0; #X connect 5 0 4 0; #X connect 5 1 3 0; #X connect 6 0 12 0; #X connect 7 0 12 0; #X connect 7 1 9 0; #X connect 9 0 12 0; #X connect 10 0 12 0; #X connect 11 0 8 1; #X connect 12 0 8 0;
Alex a écrit :
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?
i ask exactly the same question about 7 years ago. don't remember the answer. c
Thanks, Alex
On Wed, Nov 11, 2009 at 7:23 AM, kristof lauwers pd@kristoflauwers.domainepublic.net 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
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
-
Alex -
cyrille henry -
Georg Werner -
Martin Peach -
martin.peach＠sympatico.ca
-
Miller Puckette