[alsa-devel] Audigy bay protocol
Tony "Chainsaw" Vroon
chainsaw at gentoo.org
Tue Jul 1 12:27:12 CEST 2008
On Tue, 2008-07-01 at 12:09 +0200, Takashi Iwai wrote:
> Do you mean that after sending the last two SYSEX, the device returns
> the SYSEX messages above appropriately? In which timing?
Those two SysEx messages are the (immediate) response to the
initialisation string. The first seems some generic "yes, bay attached,
speaking protocol 2.3" reply, while the second is your initial jack
status.
You could time out on not receiving the "bay attached" message and then
not enable your SysEx listener at all. The actual message will arrive
within a single second, but 5 seconds should be a safe bet.
Once this sequence completes, you will then get jack/button/volume
updates as the event occurs on the bay.
To confirm, the initialisation string is:
echo -en "\xf0\x00\x20\x21\x61\x00\x00\x00\x7f\x00\xf7"
> /dev/snd/midiC0D1
> thanks,
> Takashi
Regards,
Tony V.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20080701/dce57062/attachment.sig
More information about the Alsa-devel
mailing list