Is there a way to receive, intepret, and send SysEx messages (like MMC) via PD?
I found one message on the list archives, from 1999, and no answer for it.
-ken
IIRC, [midout] should be able to send correct SySex messages out. [sysexin] supposedly reads sysex. I cannot test those right now but i remember having some success with these, but it was long time ago (I can't even track down the patches I used).
On Fri, Apr 18, 2008 at 7:20 PM, Ken Restivo ken@restivo.org wrote:
Is there a way to receive, intepret, and send SysEx messages (like MMC) via PD?
I found one message on the list archives, from 1999, and no answer for it.
-ken
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Mon, Apr 21, 2008 at 12:04:19AM -0400, Michal Seta wrote:
IIRC, [midout] should be able to send correct SySex messages out. [sysexin] supposedly reads sysex. I cannot test those right now but i remember having some success with these, but it was long time ago (I can't even track down the patches I used).
Thanks! midiout appears to work. sysexin doesn't; I'm definitely sending sysexes to the port, but nothing is coming out of the bottom of sysexin.
I'm on vanilla pd 0.40.2-2, the Debian Sid package.
-ken
On Mon, Apr 21, 2008 at 2:09 AM, Ken Restivo ken@restivo.org wrote:
Thanks! midiout appears to work. sysexin doesn't; I'm definitely sending sysexes to the port, but nothing is coming out of the bottom of sysexin.
Have you tried reading your SysEx with [midiin]?
On Tue, Apr 22, 2008 at 10:03 AM, Michal Seta mis@artengine.ca wrote:
Have you tried reading your SysEx with [midiin]?
I just tried it. Seems to be working but I could not check the integrity of the data although it appears fine on the surface. HTH.
On Tue, Apr 22, 2008 at 10:53:44AM -0400, Michal Seta wrote:
On Tue, Apr 22, 2008 at 10:03 AM, Michal Seta mis@artengine.ca wrote:
Have you tried reading your SysEx with [midiin]?
I just tried it. Seems to be working but I could not check the integrity of the data although it appears fine on the surface. HTH.
Nothing shows up on the outputs of midiin or on sysexin.
However, aseqdump shows that the data is definitely being pumped out by the keyboard, and making it into ALSA.
Notes and CC's show up just fine in pd via notein, etc.
May be a bug or misconfiguration in my specific setup of PD then.
-ken
Ken Restivo wrote:
On Tue, Apr 22, 2008 at 10:53:44AM -0400, Michal Seta wrote:
On Tue, Apr 22, 2008 at 10:03 AM, Michal Seta mis@artengine.ca wrote:
Have you tried reading your SysEx with [midiin]?
I just tried it. Seems to be working but I could not check the integrity of the data although it appears fine on the surface. HTH.
Nothing shows up on the outputs of midiin or on sysexin.
However, aseqdump shows that the data is definitely being pumped out by the keyboard, and making it into ALSA.
Notes and CC's show up just fine in pd via notein, etc.
May be a bug or misconfiguration in my specific setup of PD then.
-ken
hi ken,
have you tried to send short sysex messages (shorter than 20 bytes) to midiin? look at http://lists.puredata.info/pipermail/pd-list/2007-07/052435.html
maybe your dump is too long.
best peter
hi all,
I'm working on PD 0.40 and Gem 0.90 (installed via Synaptic), everything works fine with PD and pdp but when I create any objects related to Gem GUI (gemwin) or open a patch with gemwin, it crashes with the output below:
pd -verbose -lib Gem Pd version 0.40-2 compiled 22:04:28 Dec 7 2006 port 5400 TCL_LIBRARY="/usr/lib/pd/tcl/library" TK_LIBRARY="/usr/lib/pd/tk/library" "/usr/lib/pd/bin/pd-gui" 5400 Waiting for connection request... ... connected OSS: requested audio buffer size 8816 limited to 8192 OSS: issuing first ADC 'read' ... ...done. socket receive error: Connection reset by peer (104) Segmentation fault (core dumped)
Same situation if I work as root (except it connects to port 5401) seems to be some problems with tcl/tk but I've installed the latest from Synaptic, P.S I'm working on MacBook
Thanks,