27 Jul
2009
27 Jul
'09
6:35 a.m.
Gabriel M. Beddingfield wrote:
Hi Christoph,
On Mon, 27 Jul 2009, Christoph Eckert wrote:
Hi :)
on my system it's possible to receive more than 16355 bytes. It might be
hat the TG33 sends "F0 [...] F7" blocks. Should I take a look at this?
Does amidi work for your system?
spinymouse-sudo@64studio:~$ amidi -l
Dir Device Name
IO hw:0,0 TerraTec EWX24/96 MIDI
IO hw:1,0,0 USB Device 0x170b:0x11 MIDI 1
spinymouse-sudo@64studio:~$ amidi -p hw:1,0,0 -t 8 -r
/mnt/music/studio3.0b/SysEx/2009-07-27/YamahaTG33dAlltAll.syx
40981 bytes read
spinymouse-sudo@64studio:~$ ls -Al /mnt/music/studio3.0b/SysEx/2009-07-27
total 44
-rw-r--r-- 1 spinymouse-sudo spinymouse-sudo 40981 2009-07-27 10:27
YamahaTG33dAlltAll.syx
spinymouse-sudo@64studio:~$
Cheers,
Ralf
I'm currently playing with some code that sends SysEx data to ALSA using
RtMidi¹. I get an error reported by the latter one as soon as the
size of the
message exceeds 16355 bytes. Unfortunately, I have such SysEx files
of two
devices (namely a Waldorf Microwave I and a Digitech Studio Quad).
Can anyone comment whether this is a limitation in ALSA, and in case
it is if
there are coding workarounds? AFAIR ALSA splits incoming SysEx-events
into
Have you tried doing SysEx dumps with amidi?[1] It might give you more
insight into whether the problem is ALSA or RtMidi.
Peace,
Gabriel
[1] On Debian, this is in the package 'alsa-utils'