How long has ALSA been in existence now? The documentation for ALSA is
still incomplete and excessively complex for the average user trying to
adapt it to his needs. Here's a rather common scenario. A user just
purchases a new computer. For the sake of argument, the driver for the
audio
Lee,
In a more compact form, here's the output of lspci -n :
00:00.0 Class 0600: 1106:0204
00:00.1 Class 0600: 1106:1204
00:00.2 Class 0600: 1106:2204
00:00.3 Class 0600: 1106:3204
00:00.4 Class 0600: 1106:4204
00:00.7 Class 0600: 1106:7204
00:01.0 Class 0604: 1106:b188
00:0a.0 Class 0200:
I first mentioned this echo problem while experimenting with the
2.6.16.18 kernel. The problem is even worse now. Audio is totally
unusable. Although my PC hasn't hardlocked yet, it just might at some
point in the future. I simply changed from the 2.6.16.1 kernel which
works fine with ALSA to
00:00.0 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
Subsystem: VIA Technologies, Inc. K8M800 Host Bridge
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort-
TAbort-
Lee -
I don't know if I can explain it much better, but here's another
attempt. ANY sound just echoes for several seconds almost like the
problem is due to conflicting interrupts. If I play a brief tone ( 1
sec.), the tone will just echo for several seconds. Imagine listening to
a longer
After more experimentation with the 2.6.16.1 kernel, I've discovered
that 2 channel output is working fine with gXine. The sole problem seems
to be choppy 5.1 channel output as indicated in my previous e-mail. I
won't even think about installing the 2.6.16.18 kernel until this
problem with 5.1
Nevermind ... The problem of choppy 5.1 output seems to be gXine 0.5.6
with the 2.6.16.1 kernel. I'll just wait for newer ALSA drivers to see
if the severe problems with the 2.6.16.18 kernel disappear.
___
Alsa-user mailing list
My audio is nearly trashed, i.e. bad stutter (interrupts?), with the
latest generic kernel for Linux, 2.6.16.18, and an onboard VT8237A audio
controller. As of today, I've updated to Slackware Current with the
latest kernel which was a big mistake in retrospect. I'm also using
ALSA
Takashi and TiMidity++ crew,
I really appreciate your work on making TiMidity++-2.12.0-pre1b
compatible with Jack! Of course, a lot of little problems still exist
with the change to a newer transport mechanism, but I'm absolutely
beside myself with glee! :)
The whole crew working on
Christian,
First, use TiMidity++-2.12.0-pre1b source instead with ALSA 0.9.x. Find
it at http://www.timidity.jp . Better yet, try the newer, unstable
versions of TiMidity++ at http://www.sf.net/projects/timidity . Nightly
tarballs are made of the source. Although bugs exist, I can hardly
Hi,
Recently, I've been experiencing audio problems with ALSA in general.
I've been trying to get Flightgear 0.9.2 and TORCS to run properly, but
both of them had audio problems where the simulations would just hang
for about a minute before returning input control. Now, after further
I don't know much about alsa-compilation, but this sounds more like
a gcc
problem. Which version are you using? Iheard, that there are lots of
problems
between gcc 2.9.x and gcc 3.x. If you have an older gcc version, maybe you'd
try updating it.
I hope that helps.
Kindest regards
I get the following error trying to compile .9rc8's alsa-driver package
on Slackware 8.1 (2.4.18 kernel):
make[1]: Entering directory `/usr/src/alsa/alsa-driver-0.9.0rc8/acore'
gcc -D__KERNEL__ -DMODULE=1 -I/usr/src/alsa/alsa-driver-0.9.0rc8/include
-I/lib/modules/2.4.18/build/include -O2
T.P. Reitzel wrote:
T.P. Reitzel wrote:
Hi,
I bought Santa Cruz from Turtle Beach and I've been enjoying basking
in the sunhe he However, it's been raining on my parade lately
frown.
With the silliness aside, I've been trying to get Ecasound 2.2.1 to
record from a device with no success
T.P. Reitzel wrote:
Hi,
I bought Santa Cruz from Turtle Beach and I've been enjoying basking
in the sunhe he However, it's been raining on my parade lately
frown.
With the silliness aside, I've been trying to get Ecasound 2.2.1 to
record from a device with no success. I must be doing
Hi,
After pondering the situation for awhile, I finally closed my eyes and
bought Santa Cruz. hehe The card should be here on Monday. I've read a
lot of commentary on the lack of support from Cirrus Logic on the
Crystal Semiconductor 4630, especially Jaroslav's comments back in May
of 2002.
Bob,
If you can't adjust the levels of Capture or use the spacebar to
select it with alsamixer, then reinstall ALSA and ensure that the *pcmc
devices are installed.
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition +
17 matches
Mail list logo
