Hi Clemens.
I actually add the length using a lambda function in the ev_dict at line 24:
lambda ev: [len(ev.sysex)-1] + ev.sysex[1:-1]
lambda ev: [len(ev.sysex)-1] + ev.sysex[1:-1]
SysEx events are not a problem per se, if you have a track with only SysEx events, it works like a charm; the issue happens when there are different event types in the same track, in a peculiar order.
More about this:
https://github.com/vishnubob/python-midi/issues/95
More about this:
https://github.com/vishnubob/
(I actually closed that issue because wasn't directly related and was waiting for a confirmation from a guy on #ardour who was going to look into it.
If you can help us to shed some light on this, it'll be very appreciated!
Regards,
Maurizio
2016-09-27 19:08 GMT+02:00 Clemens Ladisch <clemens@xxxxxxxxxx>:
Maurizio Berti wrote:
> There are still some bugs (a strange export problem with sysex messages I'm
> trying to solve)
Apparently, the length is not written:
elif isinstance(event, SysexEvent):
ret += chr(0xF0)
ret += str.join('', map(chr, event.data))
ret += chr(0xF7)
(And the length includes the F7 bytes. And I don't know if the data includes
the F0 and F7 in both the Jack and ALSA interfaces.)
Regards,
Clemens
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
È difficile avere una convinzione precisa quando si parla delle ragioni del cuore. - "Sostiene Pereira", Antonio Tabucchi
http://www.jidesk.net
http://www.jidesk.net
_______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
