The one question I do have is the buffer size (128/2 ?) and if you tested at more than one buffer size. I would expect that the two would be tied together.

On Tue, 3 Nov 2020, Christopher Arndt wrote: I knew there was a limit but had never run into it. I realize that the longest sysex I had used were ~20 bytes (mackie control with LCD info sent channel at a time) The one question I do have is the buffer size (128/2 ?) and if you tested at more than one buffer size. I would expect that the two would be tied together. I also remember reading that there had been code developed for jack (I do not remember if it was jack 1 or 2 specific) to allow long, non-realtime sysex to be used. However, I do not remember if it was ever included or how it was accessed. -- Len Ovens www.ovenwerks.net _______________________________________________ Linux-audio-user mailing list Linux-audio-user(a)lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-user

Tested MusE with Jack 1.9.14: Successfully sent a 1536 byte sysex from one MusE instance to another. Has Jack midi sysex length finally improved? Yay! It sure didn't seem to be working years ago when I did the MusE sysex stuff. Thanks. Tim. MusE sequencer project.

On 11/2/20 6:25 PM, Alexandre DENIS wrote: > Hi, > > I try to understand why sysex go through jack MIDI sometimes, and > sometimes they are lost. I am aware that jack has a limit for the > maximum message size per period, but I am playing with program dump of > my Nordlead which are only 139 bytes -- definitely not huge. > > I am running jackdbus with a2jmidid, through Catia. My system is Debian > + kxstudio. > > When I try an application with native jack MIDI, such as Reaper (with > jack backend) or MuSE, I can record sysex successfully, but when I play > it, it never reaches the hardware. > > With applications using ALSA sequencer (tested with qtractor and > Rosegarden), I can record and play successfully sysex using ALSA. > However, I cannot record nor play sysex when connecting jack MIDI ports > instead (jack MIDI wrapper ports from a2jmidid). > > Is this the expected behavior? Are we stuck with ALSA when we are > dealing with sysex messages? > > Bonus question: is it possible to be warned when jack is dropping sysex > messages? > > Thanks! > -a. > > > _______________________________________________ > Linux-audio-user mailing list > Linux-audio-user(a)lists.linuxaudio.org > https://lists.linuxaudio.org/listinfo/linux-audio-user

On 11/3/20 11:31 PM, Tim E. Real wrote: "Bonus question: is it possible to be warned when jack is dropping sysex messages?" I forgot to mention, in MusE we call jack_midi_event_reserve(), �and if it fails, look for this message: "MidiJackDevice::queueEvent ME_SYSEX: buffer overflow, sysex too big, event lost" I did not see the message in the test above. IIRC years ago it would happen. Tim. > On 11/2/20 6:25 PM, Alexandre DENIS wrote: >> Hi, >> >> I try to understand why sysex go through jack MIDI sometimes, and >> sometimes they are lost. I am aware that jack has a limit for the >> maximum message size per period, but I am playing with program dump of >> my Nordlead which are only 139 bytes -- definitely not huge. >> >> I am running jackdbus with a2jmidid, through Catia. My system is Debian >> + kxstudio. >> >> When I try an application with native jack MIDI, such as Reaper (with >> jack backend) or MuSE, I can record sysex successfully, but when I play >> it, it never reaches the hardware. >> >> With applications using ALSA sequencer (tested with qtractor and >> Rosegarden), I can record and play successfully sysex using ALSA. >> However, I cannot record nor play sysex when connecting jack MIDI ports >> instead (jack MIDI wrapper ports from a2jmidid). >> >> Is this the expected behavior? Are we stuck with ALSA when we are >> dealing with sysex messages? >> >> Bonus question: is it possible to be warned when jack is dropping sysex >> messages? >> >> Thanks! >> -a.

On Tue, 3 Nov 2020 21:29:28 -1000 david <gnome(a)hawaii.rr.com> wrote: There are limits on some hardware synths. Very many moons ago I wrote SYSEX software for an Acorn Archimedes to support a couple of synths I had at the time. One of them transmitted SYSEX in a series of quite small chunks, the other did the whole lot in a single stream. Both comply with the MIDI standard, but you have to send back in the format you receive, and as far as I recall there was no way of knowing this in advance. This was with MIDI 0 so may have changed since then. Both synths were Yamaha ones, and the biggie was "All voice and multi" - basically the entire synth setup!