From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: Creative Audigy 4 Date: Thu, 09 Dec 2004 16:00:14 +0100 Message-ID: References: <41B228F0.4080804@superbug.co.uk> <1102195213.28776.34.camel@krustophenia.net> <41B22DC8.2080704@superbug.co.uk> <1102196632.28776.43.camel@krustophenia.net> <41B234F3.9010904@superbug.co.uk> Mime-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: multipart/mixed; boundary="Multipart_Thu_Dec__9_16:00:14_2004-1" Return-path: In-Reply-To: <41B234F3.9010904@superbug.co.uk> Sender: alsa-devel-admin@lists.sourceforge.net Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: James Courtier-Dutton Cc: Lee Revell , alsa-devel List-Id: alsa-devel@alsa-project.org --Multipart_Thu_Dec__9_16:00:14_2004-1 Content-Type: text/plain; charset=US-ASCII At Sat, 04 Dec 2004 22:06:43 +0000, James Courtier-Dutton wrote: > > Lee Revell wrote: > > On Sat, 2004-12-04 at 21:36 +0000, James Courtier-Dutton wrote: > > > >>I found it. > >>I quote: > > > > > > Heh, I just posted the exact same info. > > > > What do you think is the best long term solution? We can't expect every > > user to add that sequence to modules.conf. > > > > This seems like something the driver should do. After all, just because > > you can set a register via /proc does not mean you should have to, if > > it's something the driver should obviously do. I think this qualifies, > > since this is necessary to get the port to work at all. Basic hardware > > initialization should not be left to userspace. > > > > Besides, the driver _knows_ whether the device is an Audigy 2 ZS, > > whereas userspace would have to extract this from lspci or something. > > > > Lee > > > > It is probably better just to get the program that is going to listen to > the midi commands from the remote to send the command. That command will > not hurt any other midi devices. You can put a script in /etc/alsa.d/emu10k1 when you're using alsasound init script. For example, SUSE has the following script to initialize the soundfont and IR stuff. Takashi --Multipart_Thu_Dec__9_16:00:14_2004-1 Content-Type: text/plain; charset=US-ASCII #!/bin/sh # # load the default soundfont file automatically # . /etc/sysconfig/sound test x"$LOAD_SEQUENCER" = xyes || exit 0 test -x /usr/bin/asfxload || exit 0 . /etc/rc.status load_sf () { for d in /usr/share/sounds/sf2 \ /usr/share/sfbank \ /usr/local/lib/sfbank \ /usr/share/sfbank/creative \ /usr/local/lib/sfbank/creative \ "/windows/c/Program Files/Creative/SBLive/SFBank" \ "/windows/c/Programme/Creative/SBLive/SFBank" \ ; do if [ -r "$d/$1" ]; then echo -n "Loading soundfont $d/$1" /usr/bin/asfxload "$d/$1" rc_status -v -r return 0 fi done return 1 } init_remote () { # this is needed for Audigy2 platinum EX devs=`grep '^[0-9].*Audigy' /proc/asound/cards | cut -b 1` for c in $devs; do if [ -w /dev/snd/midiC${c}D1 ]; then echo -en "\xf0\x00\x20\x21\x61\x00\x00\x00\x7f\x00\xf7" > /dev/snd/midiC${c}D1 fi done } case $SOUNDFONT_FILES in /*) if [ -r "$SOUNDFONT_FILES" ]; then echo -n "Loading soundfont $SOUNDFONT_FILES" /usr/bin/asfxload "$d/$1" rc_status -v -r exit 0 fi ;; esac for file in $SOUNDFONT_FILES default.bnk default.sf2 ; do if load_sf $file ; then break fi done init_remote exit 0 --Multipart_Thu_Dec__9_16:00:14_2004-1-- ------------------------------------------------------- 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/