Hi Miller,
yap I'm using ALSA.
btw, I had a look at the source code (I want to clarify I'm not a C
programmer :) ) and from what I found in x_midi.c and s_midi.c, it kind
of make sense that [midiout] returns 1 byte at time.
it seems to me we're missing a way to detect outgoing sysex messages
(maybe having a dedicated object could help), so there's no way to
collect a sysex and send it out in one go (ie having an array to
return). I apologize for my trivial description of the "problem", but
this is what I think is causing this behaviour.
cheers,
Mario
On 13/03/18 04:37, Miller Puckette wrote:
Hi Mario -
Perhaps you said this in the previous message which I missed... are you
using ALSA MIDI system or OSS?
MIDI support has always been a problem in Pd... largely because I don't have
a lot of experience with it.
cheers
Miller
On Tue, Mar 13, 2018 at 12:04:00AM +0000, mario buoninfante wrote:
Hi,
I ran few more tests on Linux trying to understand what's going on with
[midiout] and sysex messages.
I discovered that it's not just about sysex. I'm monitoring MIDI from Pd
with /KMidimon /and /GMIDImonitor/, and I noticed that also sending Note On
messages with [midiout] seems to be in some way different then sending the
same message using [noteout].
when Note On is sent using [midiout], this will spit single bytes that are
recognized as single byte sysex messages by the MIDI monitors!!!!!
has anyone ever experienced the same?
cheers,
Mario
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
