Clemens Ladisch wrote:

Sean M. Pappalardo - D.J. Pegasus wrote:

...

As soon as I start the JACK server to handle the audio interface on the SCS.1m, the ALSA driver stops sending MIDI for that device unless I stop JACK and power-cycle the device. Its last words are: F0 00 01 60 48 53 53 0F 03 00 03 00 00 0B 01 F7

This is a ping response (tag F3). Apparently, Jack's FFADO driver reinitializes the device and registers its own address for received packets. Since it does _not_ handle MIDI messages, it really should not do this.

If we're talking about the ARM handler for HSS1394 messages, then I suspect the reason it sets this up is that Pieter initially fully intended for FFADO to pass these messages back. Obviously if this were to be done then an ARM handler would be necessary, but that's not how things are panning out. To prevent the ARM handler being registered by FFADO it should only be ncessary to comment out the initMessageHandler() call in the ScsDevice::discover() method. I'm happy to make this change since it seems to make sense to do so given these latest developments. A preliminary approach is in FFADO svn revision 2163 if you want to check it out. Note that this will break FFADO's test-scs program - a detail I'll tidy up if the overall approach seems to work.

The other related issue is whether the other device setup done by FFADO interferes with the MIDI stream transmission. I guess that's most easily tested by trying FFADO rev 2163 and seeing if there are other issues remaining.

Regards jonathan