From: Takashi Iwai <tiwai@suse.de>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: Lee Revell <rlrevell@joe-job.com>,
alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Creative Audigy 4
Date: Thu, 09 Dec 2004 16:00:14 +0100 [thread overview]
Message-ID: <s5hbrd3a54x.wl@alsa2.suse.de> (raw)
In-Reply-To: <41B234F3.9010904@superbug.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]
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
[-- Attachment #2: Type: text/plain, Size: 1281 bytes --]
#!/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
next prev parent reply other threads:[~2004-12-09 15:00 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
2004-12-04 21:43 ` Lee Revell
2004-12-04 22:06 ` James Courtier-Dutton
2004-12-09 15:00 ` Takashi Iwai [this message]
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=s5hbrd3a54x.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox