iriXx [EMAIL PROTECTED] writes:
just upgraded mandrake from 8.2 to 9.0
and found out that it seems to have made my alsa all foobar :(
i recompiled and reinstalled alsa 0.9.rc5 after upgrading... but i
dont seem to be able to get it working.
im running a quattro usb audio unit...
On Sun, Dec 15, 2002 at 08:38:54PM -0800, Mark Knecht wrote:
Paul,
I'm using two Hammerfalls in separate boxes. Please try to come up
with a solution, either automatically or by asking questions in some
configuration process, that allows two Linux boxes to choose which to
make the master.
At Sat, 14 Dec 2002 13:04:40 +0100,
Rafal Dejewski wrote:
Hi,
I have a problem with alsa mixer on kernel 2.5.51 and alsa-lib, alsa-utils
0.6rc6. Whenerver I try to run alsamixer the following message appers in
console and alsamixer would not start:
$ alsamixer
ALSA lib
Martin,
That might certainly be an answer. How would this amixer switch get
st in the first place? I wouldn't mind doing it by hand once as long as
it was then loaded after that.
I'm having an interesting problem with this setup with now that's
probably based in this area. If I bring up
Martin,
That might certainly be an answer. How would this amixer switch get
st in the first place? I wouldn't mind doing it by hand once as long as
it was then loaded after that.
what you want is a short startup script (typically in somewhere under
/etc/rc.d, but unfortunately this varies
At Mon, 16 Dec 2002 08:49:35 -0500,
Paul Davis wrote:
Martin,
That might certainly be an answer. How would this amixer switch get
st in the first place? I wouldn't mind doing it by hand once as long as
it was then loaded after that.
what you want is a short startup script (typically in
On Sun, 15 Dec 2002, Henry Walpool wrote:
The Hoontech Media 7.1 card has a consumer/professional option at least
under windows. I would assume that with the correct information from
hoontech one could program this under alsa. Of course I don't have a
clue, I'm just guessing here.
It's
the standard alsasound init script can call a card-dependent script
that reminds me. the last version of the alsasound script that i saw
did something very dangerous. it seemed to try to install *every*
snd-card module it could find. if you have a system with an ISA bus,
this can prove fatal to
On Mon, Dec 16, 2002 at 04:04:23AM -0800, Mark Knecht wrote:
I'm having an interesting problem with this setup with now that's
probably based in this area. If I bring up these two systems with the
main DAW in Linux, and the slave system in Windows everything is fine.
The DAW controls the
IMHO this is a design bug of all rme cards. The documents about rme32 and
rme96 where identical in this point. They were talking about one master-mode
and nothing about the frequency. I don't know anything about rme9652 or
hdsp, but the sourcecode looks not very different to the older rme96.
But
At Mon, 16 Dec 2002 09:29:05 -0500,
Paul Davis wrote:
the standard alsasound init script can call a card-dependent script
that reminds me. the last version of the alsasound script that i saw
did something very dangerous. it seemed to try to install *every*
snd-card module it could find. if
At Sun, 15 Dec 2002 09:40:24 -0300,
Juan Linietsky wrote:
Hello!
I am looking for documentation on the schematics and working of the
Gravis Ultrasound Classic with the hopes to add support for it in
DOSEMU. Unfortunatedly I failed to find information about it
on the net. Does anyone
Hi,
can anyone who owns the CMI8330 ISA test the attached patch?
the patch will change the pcm interface of this soundchip as a more
reasonable way. the playback and capture are combined into one pcm.
it's for the latest cvs version. not sure whether it's applicable to
rc6.
please check
At Sat, 14 Dec 2002 19:48:25 +0900,
Patrick Shirkey wrote:
Takashi Iwai wrote:
could you tell me the rcs version numbers of the files on
alsa-kernel/usb you are using (18 Nov.) ? i've checked the files via
cvs but i couldn't see any differences around the date.
I have managed
Takashi Iwai wrote:
hmm, it's weird. it would be nice if we can know at which point the
driver became broken...
It was working nicely before the drivers were merged but wouldn't paly
with jack. Now it likes jack.
the attached patch will (hopefully) do the same thing as qinit in the
paul davis wrote:
does any of this make it any clearer? its really a bit of problem that
the rate setting code doesn't do a full 100% check on all this
stuff. an app can set the rate to 44100, and appear to have succeeded,
but it will have no difference on the actual rate if the sync source
Hi!
Hopefully, the following information is of some help.
Takashi Iwai wrote:
to be sure, could you elaborate the symptom again and the detail of
your system (kernel version, applied patches, ALSA version)?
kernel: 2.4.19-16mdkcustom, compiled with sound and without alsa. I
compiled from
Patrick,
I believe the AI-3 operates at 48K if it is not receiving a clock via
it's ADAT input. If the ADAT input is applied and provides 44.1K, then
it is my understanding that the AI-3 operates at 44.1K.
Mark
On Mon, 2002-12-16 at 14:53, patrick reardon wrote:
yes, thnx, it's much
On Mon, 2002-12-16 at 18:51, Paul Davis wrote:
i think it would something like this:
options snd-hdsp snd_index=0
options snd-usb-foo snd_index=1
i'm sure that takashi or jaroslav will correct me if i got this wrong.
--p
Paul,
This makes perfect sense, and it isn't what I did.
19 matches
Mail list logo
