From: James Courtier-Dutton <James@superbug.co.uk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Creative Audigy 4
Date: Sat, 04 Dec 2004 21:36:08 +0000 [thread overview]
Message-ID: <41B22DC8.2080704@superbug.co.uk> (raw)
In-Reply-To: <1102195213.28776.34.camel@krustophenia.net>
Lee Revell wrote:
> On Sat, 2004-12-04 at 21:15 +0000, James Courtier-Dutton wrote:
>
>>Now to the problems.
>>The card seems to work quite well, except for the remote control.
>>Has anyone ever got the Audigy 2 ZS remote control to work?
>
>
> Yes I got mine to work a whle back. There is a sequence of commands you
> have to echo to the midi port first. Don't have it handy but you should
> be able to google for it. I think it's on the ALSA wiki.
>
> Lee
>
I found it.
I quote:
There is an issue with the Audigy 2 Platinum Ex soundcard
(and probably some other Audigy 2 cards as well), whereas the
IR sensor, MIDI and the buttons on the LiveDrive do _not_ work
at all until the LiveDrive is initialized by sending the sequence
of '0xf0, 0x00, 0x20, 0x21, 0x61, 0x0, 0x00, 0x00, 0x7f, 0x0, 0xf7'
to the MIDI port. Before doing this, even the LED on the LiveDrive
won't blink, as it usually does when a button on the remote is pressed.
As far as I know, this behaviour is different than with most
LiveDrives manufactured by Creative.
For more information see:
http://www.mail-archive.com/alsa-devel@lists.sourceforge.net/msg09267.html
The easiest workaround to this is to add the following line to
/etc/modules.conf
post-install snd-emu10k1
echo -e '\360\000\040\041\141\000\000\000\177\000\367' > /dev/snd/midiC0D1
[(Ed) The above is wrapped for formatting. It should be one line.]
It works for me and it should be distribution-independent
(with exception to Debian, where you change /etc/modutils/alsa
and run update-modules afterwards, Debian users will know anyway).
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-04 21:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 21:15 Creative Audigy 4 James Courtier-Dutton
2004-12-04 21:20 ` Lee Revell
2004-12-04 21:36 ` James Courtier-Dutton [this message]
2004-12-04 21:43 ` Lee Revell
2004-12-04 22:06 ` James Courtier-Dutton
2004-12-09 15:00 ` Takashi Iwai
2004-12-04 21:36 ` Lee Revell
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=41B22DC8.2080704@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=rlrevell@joe-job.com \
/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.