From: Takashi Iwai <tiwai@suse.de>
To: Miguel Duarte <mjrduarte@mail.telepac.pt>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Audigy 2 Platinum eX Remote (Some developer please read this)
Date: Wed, 24 Sep 2003 12:02:12 +0200 [thread overview]
Message-ID: <s5h8yoefqsb.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030924093645.NWH9998.fep06-svc.mail.telepac.pt@[127.0.0.1]>
At Wed, 24 Sep 2003 10:36:45 +0100,
Miguel Duarte wrote:
>
> Hi,
>
> Until now I wasn't able to make my remote work.
> While posting in the EMU10K1 devel mailing list, someone said that it was necessary to "initialize" the MIDI device used by the remote. A SysEx sequence has to be send to '/dev/snd/midiC0D1'. The sequence is '0xf0, 0x00, 0x20,0x21, 0x61, 0x0, 0x00, 0x00, 0x7f, 0x0, 0xf7'.
oh, my...
> The source code bellow is of a program that does just that. After
> modprobing the modules with the correct options (the options are the
> same as the Platinum), just run this prog to "initialize" the midi
> device. Voi-lá! The remote works! I think this is an ugly hack.
i don't think it's so bad.
>I'm sure that this can be implemented in the driver itself.
yes, but why bother to do this in the driver, although you can do it
nicely on user-space?
(you can even use shell's echo command for this :)
anyway, thanks for your info!
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
prev parent reply other threads:[~2003-09-24 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030924093645.NWH9998.fep06-svc.mail.telepac.pt@127.0.0.1>
2003-09-24 9:36 ` Audigy 2 Platinum eX Remote (Some developer please read this) Miguel Duarte
2003-09-24 10:02 ` Takashi Iwai [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=s5h8yoefqsb.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=mjrduarte@mail.telepac.pt \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox