the putbytes of the alsa-implementation does not get called.
the attached patch (s_midi.c, x_midi.c; pd=0.39-1-CVS)
should fix this.
the current alsa-implementation of [midiout] uses a kind of
sysex-wrapper to get the raw-data through the alsa-seq
interface; later think whether this is really a good idea,
in the meantime it works.
btw, since i changed the subject to not reflect the version
number of pd, i give it here: confirmed wrong behaviour in
pd-0.39-1 (both vanilla and devel); all pd-versions with
alsamidi until now should be affected
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=564396
the putbytes of the alsa-implementation does not get called.
the attached patch (s_midi.c, x_midi.c; pd=0.39-1-CVS)
should fix this.
the current alsa-implementation of [midiout] uses a kind of
sysex-wrapper to get the raw-data through the alsa-seq
interface; later think whether this is really a good idea,
in the meantime it works.
btw, since i changed the subject to not reflect the version
number of pd, i give it here: confirmed wrong behaviour in
pd-0.39-1 (both vanilla and devel); all pd-versions with
alsamidi until now should be affected
patch against pd-0.39-1
Logged In: YES
user_id=564396
as gnter has noticed, there is a memory leak in
sys_alsa_putmidibyte()
attached is a patch against s_midi_alsa.c (in pd-0.39-1-CVS)
which should fix this
patch against pd-0.39-1
Logged In: YES
user_id=1361897
Tested [midiout] sysex output with external hardware; works
fine.
Logged In: NO
thanks!
tested here too and it works.
I don't have output with midiout in 0.40.3-extended.
Now is this a bug or there a way around for me?
is this still an issue
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).