All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tony \"Chainsaw\" Vroon" <chainsaw@gentoo.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Audigy bay protocol
Date: Tue, 01 Jul 2008 11:27:12 +0100	[thread overview]
Message-ID: <1214908032.15385.7.camel@localhost> (raw)
In-Reply-To: <s5h3amtgbkd.wl%tiwai@suse.de>


[-- Attachment #1.1: Type: text/plain, Size: 889 bytes --]

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.

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      reply	other threads:[~2008-07-01 10:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26 13:11 Audigy bay protocol Tony "Chainsaw" Vroon
2008-07-01 10:09 ` Takashi Iwai
2008-07-01 10:27   ` Tony "Chainsaw" Vroon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1214908032.15385.7.camel@localhost \
    --to=chainsaw@gentoo.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.