[alsa-devel] Help requested: new HSS1394 MIDI back-end

Clemens Ladisch clemens at ladisch.de
Fri Jun 1 10:22:48 CEST 2012

Sean M. Pappalardo - D.J. Pegasus wrote:
> On 05/30/2012 09:18 AM, Clemens Ladisch wrote:
>> As it happens, the actual SysEx commands use the wrong manufacturer ID
>> ("00 01 02" is Crystal Semiconductor); I could just use the real ID
>> (Stanton is "00 01 60") to escape non-MIDI HSS1394 messages.  Let's add
>> "HSS" to identify this, and to allow the full byte range, each HSS1394
>> byte is split into two nibbles.
> That all sounds good, but that now means that applications that want
> to use these device features must have different code for Linux than
> they do for Windows or OSX.

IIRC it was decided to use a MIDI driver in order to allow other
applications to access these devices with standard MIDI APIs.
(Does this imply that on Windows and OS X, it is not possible to
access them without using the HSS1394 library?)

You could still port the HSS1394 library so that it sits on top of the
MIDI driver.  (In other words, the Linux MIDI backend would be the
equivalent of the Windows and OS X FireWire backends.)


More information about the Alsa-devel mailing list