On Mon, 12 Jan 2004, Lorn Potter wrote:
I am currently looking into rewriting our current OSS sound routines to
native ALSA, as it seems OSS will invariably be phased out now that the
ALSA driver is distrubuted with the Linux kernel, plus ALSA seems to have a
Personally, I hope OSS compat
Hello,
On Thu, 27 Nov 2003, Kai Vehmanen wrote:
With 1.0.0pre3, for example arecord -r 8000 - |aplay -r 8000 - produces
constant xruns. A similar app that relies on poll()/select(), fails even
more severely. When looking at...
this problem was fixed in 1.0.0rc1! It seems that the final
Hi,
On Thu, 27 Nov 2003, Takashi Iwai wrote:
/proc/asound/card0/pcm0p/sub0/hw_params and
.. the rate is locked to 48000 with 1.0.0pre3.
do you mean both for playback and capture, or only on capture side?
if the playback rate isn't set correctly (i.e. aplay -Dhw with 44.1kHz
doesn't work),
On Wed, 26 Nov 2003, Takashi Iwai wrote:
On the same machine, alsa-driver-0.9.8 works fine, but not with 1.0.0pre1
and 1.0.0pre3.
what do you mean exactly don't work in the above?
the operation is blocked, or returns an error?
if it's blocked, check /proc/asound/card0/pcm0*/sub0/* files.
I
On Wed, 19 Nov 2003, Takashi Iwai wrote:
Especially, if you have a card or a mobo with ICH (or compatible)
chip and *multiple* AC97 codecs, testing this version is appreciated.
Some of my apps have stopped working after 1.0.0pre1 on a T23 Thinkpad
(intel8x0, 82801).
Simple things like
On Wed, 26 Nov 2003, Takashi Iwai wrote:
Some of my apps have stopped working after 1.0.0pre1 on a T23 Thinkpad
(intel8x0, 82801).
[...]
On the same machine, alsa-driver-0.9.8 works fine, but not with 1.0.0pre1
and 1.0.0pre3.
what do you mean exactly don't work in the above?
the operation
Hi,
this issue is over a year old, but in case someone stumbles on
to the same problem. The solution is already documented at
http://alsa.opensrc.org/index.php?page=cs46xx
... but it took me a while to find it. :)
On Tue, 29 Oct 2002, Bob McElrath wrote:
Recording still seems to not work.
Hi,
this reply comes a bit late, but I guess this is still very much a
relevant topic.
On Mon, 7 Jul 2003, Takashi Iwai wrote:
Already alsa-lib has some features that are not so good from embedded
perspective:
- not a small lib; with default settings around 0.5MB; this
is an extra 0.5MB
On Tue, 30 Sep 2003, Tommi Sakari Uimonen wrote:
This, I think, caused also ecasound problems; it couldn't stop the
recording and after killing the process I found out that it had not
recorded anything even thougn the engine started fine.
I quess the drivers were halted just after ecasound
Note: this probably belongs to alsa-devel, so please remove alsa-user from
replies.
On Fri, 26 Sep 2003, Jamie Lutch wrote:
Didnt have any responses on my post of a few days ago, so I'm giving it
another go:
Sorry for the late reply.
So I have my setup (pdaudiocf cardecasound) running fine
On Wed, 27 Aug 2003, Tommi Sakari Uimonen wrote:
I'm planning to use arecord for serious harddisk recording, but it can't
I strongly suggest to look for other alternatives. For serious
harddisk recording you absolutely need an application that provides
protection against spikes in disk i/o
On Wed, 27 Aug 2003, Tommi Sakari Uimonen wrote:
Ecasound has support for LFS (compile with --with-largefile).
Is there also --with-96khz option? :)
If there is, or there will be soon (in two days), I'll change to that.
No need for a separate option :) ...
ecasound -f:s32_le,2,96000 -i
On Wed, 27 Aug 2003, Tommi Sakari Uimonen wrote:
Yes it doesn't sound sexy at all. But I tested arecord to perform nicely
with 96khz 24channels 32bit data, on a ext2 filesystem (I found ext2 to be
the best filesystem for this kind of writing). As I'm going to record max
12 channels, this
On Thu, 7 Aug 2003, Jeremy Hall wrote:
Kai, did you make a multi out of your cards together?
Nope, jackd accessed the individual soundcards directly (... -d alsa -d
hw:{0,1,2}).
In the new year, Kai Vehmanen wrote:
No lockups so far with the following setup:
2.4.19-ll
ALSA CVS of today
On Tue, 5 Aug 2003, Paul Davis wrote:
i am having a repeated problem with system lockups using current CVS
with JACK running SCHED_FIFO on an SMP system, with the Planet's
2.4.21 kernel.
No lockups so far with the following setup:
2.4.19-ll
ALSA CVS of today
JACK CVS of today
Hi,
On Thu, 10 Jul 2003, Carlo Wood wrote:
I only see questions on this list,
and nobody who answers them.
[...]
Where are the developers? Is ALSA still maintained?
ALSA is definitely maintained, and alsa-devel is the correct list. ALSA
actually has quite a good history in project activity.
On Fri, 11 Jul 2003, Carlo Wood wrote:
Total number of fragments allocated for buffering: 64
Well, you have 64 fragments - I only 2.
Yup, that's because I'm using the snd-ens1371 driver (maximum interrupt
frequency ~= period size, is driver/card dependent).
#fragments, #bytes: 13, 13472
One more post - I'll promise this is the last one. :)
On Fri, 11 Jul 2003, Carlo Wood wrote:
That gives rather strange output:
But it's not stopping...? That's at least different behaviour...
It doesn't feel right to read bytes when it says
that there are no fragments/bytes available.
On Thu, 3 Jul 2003, Kai Vehmanen wrote:
* making alsa-conf the primary tool for setting up ALSA user-space
Ugh, that should primary tool for setting up ALSA (kernel) drivers.
Hmm, I guess we could have two tools, one for drivers (current alsa-conf)
and one for user-space (asoundrc editor
Ok, this is a bit late, but hopefully not too late. :)
On Tue, 24 Jun 2003, Joern Nettingsmeier wrote:
other people might propose XML. then it becomes to a question whether
I think that XML is too overkill for our purposes.
otoh, the embedded guys will probably not like it, but then memory is
On Sun, 22 Jun 2003, Jaroslav Kysela wrote:
here are my next goals for the ALSA library development (short
term). I invite all developers to comment these directions.
[...]
* create ordinary pcm mixer interfaces
These are very welcome additions, especially the mixer part! Although
On Thu, 29 May 2003, Paul Davis wrote:
ah. are you running on an SMP system with current ALSA CVS? if so, its
broken within the core of ALSA. you will need to back up to April
Hmm, anyway to easily and reliably reproduce the bug?
run jack? :))
Well, I've done a lot of testing during the last
On Thu, 29 May 2003, Paul Davis wrote:
c0106298 __up_wakeup
c02bfff4 csum_partial_copy_generic_Rsmp_e8aa9a96
ah. are you running on an SMP system with current ALSA CVS? if so, its
broken within the core of ALSA. you will need to back up to April
27th to get a working SMP version. nobody has a
On Tue, 25 Mar 2003, Takashi Iwai wrote:
It seems that with newer ALSA versions, snd_pcm_read[in]() sometimes
returns -EIO even though documentation says nothing about this. After some
i also don't know whether Jaroslav added as a feature or as an
unexpected bug. anyway, this means that the
Kai Vehmanen
- [ Session created ] --
- [ Chainsetup created (cmdline) ] -
(eca-chainsetup-parser) Setting buffersize
On Tue, 18 Mar 2003, Jon Ellis wrote:
http://bugs.gentoo.org/show_bug.cgi?id=12724
[...]
and it's giving me grief because it takes so long to reproduce. The
basic problem is that either arecord or oggenc hangs after 400min
47sec. The fact that lowering the sample rate (and talking to the
On Tue, 18 Mar 2003, Kai Vehmanen wrote:
ecasound -f:16,2,44100 -i alsa -o stdout |oggenc -r -q 0 -o recording.ogg -
Btw; ecasound can also launch oggenc by itself. To modify oggenc params,
you have to edit ~/.ecasound/ecasoundrc (see man ecasoundrc(5) for info).
So the above command would
On Tue, 4 Mar 2003, Patrick Shirkey wrote:
Has anyone tried the dmix plugin thats part of alsa rc8? This looks
I was fscking around with it on Saturday. So far I have managed to use
multiple instances of aplay but other apps like alsaplayer bork at it. I
have yet to figure out why but I
Has anyone else seen this?
In the middle of playback my midiman-44 stops processing completely (no
interrupts, no activity, tried with multiple apps). Reloading modules
succeeds, but still no sound. Dmesg shows:
ALSA ../alsa-kernel/core/pcm_lib.c:187: Unexpected hw_pointer value (stream = 0,
Sorry for the late response..
On Thu, 21 Nov 2002, Mark Ziegler wrote:
thank you. You are right: my ide-dma is turned off. I only activated it in the
SUSE setup, but I've never check if it is really switched on.
Unfortunately I can not turn on the dma:
[...]
linux:/home/woody # hdparm -m 8
On Wed, 27 Nov 2002, Paul Davis wrote:
Let's be totally clear about this. its not just that the callback
model is suitable - the mserver model will actually not work for
sample sync between applications. I have always been sure that the
I think this is the critical point. ALSA's smix/mserver
On Tue, 19 Nov 2002, Mark Ziegler wrote:
ecasound -r -z:db -z:intbuf -f:s32_le,12,44100 -i alsa,hw:1 -f:s32_le,2,44100
-o test.wav
[...]
under root, but usually my system hangs complete after starting ecasound.
Only once it worked and it also reported that some data are lost.
How about if
On Wed, 23 Oct 2002, Maarten de Boer wrote:
I just installed alsa-driver-0.9.0rc4, but alas i get invalid parameter
when modprobing...
Unload all rc3 modules, check your /etc/modules.conf (replace all
instances of 'snd_xxx' with 'xxx' (but not 'snd-xxx'!), and try
modprobing snd-emu10k1
On Wed, 23 Oct 2002, Matthias Saou wrote:
Seeing how the 0.9.0rc4 release went, I was wondering if the ALSA people
wouldn't mind re-thinking the release method?
Yes, but...
- Would it be possible to release some tarballs, supposedly identical to
the final ones but a few hours/days before
On Fri, 20 Sep 2002, Takashi Iwai wrote:
your almost all negative messages persuaded me to wait awhile with
new function prototypes. Here is the result:
thanks for quick reaction.
the new library works fine with the old applications.
Btw; with ld from binutils-2.9.5.0.22-6 (rh62) I
On Tue, 17 Sep 2002, Jaroslav Kysela wrote:
After some thoughs, I think that this sort of cleanups is good for
implementing at any time. It doesn't break the implementation (in the
sense of behaviour), but it makes that older code is not compilable.
Fortunately, any C programmer can
On Tue, 17 Sep 2002, Jaroslav Kysela wrote:
1) New versioned library is libasound.so.3, so that older applications
uses older libasound.so.2.
Hmm, the 'Versions' ld script doesn't seem to be in CVS, and as a result,
linking alsa-lib currently fails. Have I missed something?
--
Hi,
I tested a laptop with 'Intel 82801CA-ICH3' and 'Cirrus Logic
CS4299 rev 6' and they seem to work fine with the new intel8x0
and ac97 versions now in CVS. I'll do more testing today.
Jaroslav, let me know if you need help in testing.
Btw; I currently have access to quite a lot of sound
Karsten Wiese wrote:
--- Kai Vehmanen [EMAIL PROTECTED] schrieb:
arecord: pcm_params.c:1051:
_snd_pcm_hw_param_refine: Assertion '0'
failed.
i get here lots of:
arecord: pcm_plug.c:68: snd_pcm_plug_close: Assertion
`plug-slave == plug-req_slave' failed.
Yup, exactly the same problem
Takashi Iwai wrote:
BTW; The cs4281 compilation problem I reported earlier is definitely
a compiler issue. On two different laptops (x20x21 thinkpads),
compiling with the RH72 gcc 2.96 produces a snd-cs4281.o that fails
to recognize the soundchip. By adding one (volatile*)
On Tue, 20 Aug 2002, Takashi Iwai wrote:
Kai Vehmanen wrote:
After doing a cvs update and recompiling and reinstalling the driver
package, snd-cs4281 now freezes my ibm-x20 laptop (rh7x, kernel 2.4.16,
today's ALSA-CVS). 0.9.0rc1 works fine. Anyone with similar experience? I
Jaroslav
On Tue, 20 Aug 2002, Kai Vehmanen wrote:
BTW; The cs4281 compilation problem I reported earlier is definitely
a compiler issue. On two different laptops (x20x21 thinkpads),
compiling with the RH72 gcc 2.96 produces a snd-cs4281.o that fails
to recognize the soundchip
After doing a cvs update and recompiling and reinstalling the driver
package, snd-cs4281 now freezes my ibm-x20 laptop (rh7x, kernel 2.4.16,
today's ALSA-CVS). 0.9.0rc1 works fine. Anyone with similar experience? I
didn't get any debug info as the system freezes up completely and I don't
have
It seems that rh72's gcc-2.96-98 does something funny when compiling
alsa-kernel/pci/cs4281.c (today's CVS-tree). Trying to install the module
results in following error messages:
--cut--
Aug 2 16:46:28 xxx kernel: ALSA ../alsa-kernel/pci/cs4281.c:675: AC'97
read problem (ACSTS_VSTS), reg =
note! cross-posted to alsa-devel; some questions about the
korg1212 driver...
On Thu, 11 Jul 2002, Martijn Sipkema wrote:
Ok, I guess here\'s the first real case against const-nframe.
I thought i had already mentioned this several time :)
You didn't say it loud enough.. ;)
[soundcards
On Mon, 17 Jun 2002, Jaroslav Kysela wrote:
Bellow patch should fix this problem, but I need to do more tests with
latest 2.5 and older 2.2 kernels, if it's a correct fix.
Hmm, this doesn't solve the problem at least when using the 2.4.17
kernel. With the test program I still get the
Here's a patch against current CVS-tree to make
alsa-driver work with 2.2.x kernels (acore/misc.c
only defines snd_compat_request_region()):
--cut--
RCS file: /cvsroot/alsa/alsa-driver/include/compat_22.h,v
retrieving revision 1.41
diff -u -r1.41 compat_22.h
--- compat_22.h 7 May 2002 15:45:47
Here's a patch against current CVS-tree to make
alsa-driver again work with 2.2.x kernels (acore/misc.c
only defines snd_compat_request_region()):
--cut--
RCS file: /cvsroot/alsa/alsa-driver/include/compat_22.h,v
retrieving revision 1.41
diff -u -r1.41 compat_22.h
--- compat_22.h 7 May 2002
Why is ALSA the better alternative? That's a question I've been asked
quite a few times recently. Below is a reply I just wrote to
ecasound-list. I'd be very interested in hearing your comments on this
issue. Have I missed some important points?
One thing that seems be causing a lot of confusion
On Thu, 7 Mar 2002, Emmanuel Fleury wrote:
Why is ALSA the better alternative?
Is it really related to devel ?
Yes. One, if not the most, important advantage ALSA has over OSS is the
framework it provides for developers. But it's not clear to everyone
(judging from the questions I get
On Thu, 28 Feb 2002, Patrick Shirkey wrote:
I attempted to get the share device working a little while ago but had
no luck. I can try again though. Actually, at the time Abramo said that
it was possible but that it had not been coded completely yet due to
funding constraints. Is that right
Answering to my own mail...
Looking at jackd code, one possibility is that the we are only getting an
EPIPE from snd_pcm_avail_update(), but the stream is still in RUNNING
state. At least in alsa-lib/src/pcm/pcm_hw.c:snd_pcm_hw_avail_update()
we have a test for:
[...]
if (avail
On Thu, 21 Feb 2002, Abramo Bagnara wrote:
if (avail pcm-buffer_size)
Yes, this condition is faulty. It should be 'avail = pcm-stop_threshold'.
- if avail buffer_size this means either played garbage (playback) or
overwritten samples (capture). The return of an error is perfectly
sensible
On Thu, 21 Feb 2002, Jaroslav Kysela wrote:
Yes, this condition is faulty. It should be 'avail = pcm-stop_threshold'.
Btw; shouldn't that be 'avail pcm-stop_threshold'...? For
instance if you want to prefill playback buffers
with silence before starting processing, you must be able
On Thu, 21 Feb 2002, Jaroslav Kysela wrote:
Btw; shouldn't that be 'avail pcm-stop_threshold'...? For
Yes, but in this case avail == 0, so the XRUN doesn't occur. But it's
true, that the check for XRUN should be active only when PCM state is
RUNNING. I'll correct it soon.
Ok, sounds good.
On Tue, 19 Feb 2002, Jaroslav Kysela wrote:
I'm still a bit puzzled why I didn't get xruns in the test case quoted
below, but until I can reproduce the problem, there's not much to discuss
You posted this sw params on alsa-devel a few days ago:
[]
sw_params:
stop_threshold: 4294967295
On Tue, 19 Feb 2002, Patrick Shirkey wrote:
I have just uploaded a template for the idea PD had to make a complete
howto for each card and link it to the sound card matrix or something
similar.
[...]
http://www.boosthardware.com/LAU/alsa/template2.html
Looks very good.
Also I have not
of alsa-devel archives, if you are having xrun
detection problems with ALSA mmap pcm API, do post a message about it. :)
On Thu, 14 Feb 2002, Kai Vehmanen wrote:
- no xruns are detected even though after the timeout
alsa_driver_wait() took 56.4msec which is more than
period_size
On Wed, 13 Feb 2002, Paul Davis wrote:
[xrun after mmap_begin]
after restarting, the audio stream is not in sync - it contains minor
crackles and clicks suggesting that the device driver doesn't really
know where the hw pointer is. the effect varies with the period size,
which reinforces my
25057.508584 usecs
engine cycle took 25170.804721 usecs
engine cycle took 25704.386266 usecs
DIS-connect ecasound:defoutput_1 and alsa_pcm:out_1
DIS-connect ecasound:defoutput_2 and alsa_pcm:out_2
removing client ecasound
engine cycle took 28678.154506 usecs
--cut--
On Thu, 14 Feb 2002, Kai Vehmanen wrote
On Thu, 14 Feb 2002, Paul Davis wrote:
- no xruns are detected even though after the timeout
alsa_driver_wait() took 56.4msec which is more than
cards, i am starting to suspect part of jack's design rather than
ALSA, but i have not yet managed to figure out what it could be. when
i check
On Thu, 14 Feb 2002, Kai Vehmanen wrote:
2.a) way to notice that an xrun has happened during b-c
b) ability to reset the streams
3. way to make sure that engine-process() never takes longer
than period_time*number_of_periods
More debug information follows. I changed jackd code so
On Thu, 14 Feb 2002, Jaroslav Kysela wrote:
What I did try was replacing drop() with snd_pcm_drain() and this resulted
in a hang (not a kernel hang, but process never returns to user-space) in
the driver level. Here's the backtrace:
I'm curious what is saying this command:
cat
On Wed, 13 Feb 2002, Patrick Shirkey wrote:
Apart from that what are the job requirements of an ALSA web maintainer
and a documentation leader?
Ok, do note that I'm not a member of the ALSA dev team, so I can't make
any real claims. Hopefully the dev team agrees with at least some of what
I'm
This is great news!
Congratulations to the ALSA team and to all who've contributed to the
effort. This is of course just the beginning. Hopefully the merge will not
only increase the number of incoming bug reports, but also the number of
incoming new developers. :)
On Wed, 13 Feb 2002,
On Tue, 12 Feb 2002, Juhana Sadeharju wrote:
We barely have any proper documentation. Checking source code is also
outdated.
We do have quite detailed documentation in the form of javadoc comments.
Not perfect but actually much better than docs of many other kernel
subsystems.
Improving
On Tue, 12 Feb 2002, Kevin Conder wrote:
I was wondering about the status of ALSA's API documentation. The
last time I checked, the ALSA developers were adding doxygen comments to
the source code. Was that project completed?
Yes and no. Just like code, there's always room for
On Tue, 5 Feb 2002 [EMAIL PROTECTED] wrote:
I am writing a Python extension module for the ALSA PCM device,
because I am interested in real-time audio processing with Python
scripts. This may sound weird first, but Python is fast enough
[...]
Now I'm writing an pure C extension for ALSA-0.9
On Thu, 24 Jan 2002, Kai Vehmanen wrote:
On the other hand with '-r 44100', full-duplex seems to work relatively
well. Even though nominally running at different speeds
(44100.952-44099.814=1.138frames/sec), they won't drift much apart.
Ok, here's a patch that adds mathematical rounding
On Thu, 24 Jan 2002, Kai Vehmanen wrote:
After applying this, I stopped getting Unexpected hw_pointer and Lost
interrupt: hw_ptr = %d expected %d errors from pcm_lib.c. Without the
patch, I get these errors with all parameters I've tried (even 48kHz!) if
both stream directions are active
On Thu, 24 Jan 2002, Jan P. wrote:
write my code in callback fashion. has anyone got a
simple alsa code template that does fullduplex
input-processloop-output in realtime?
See 'alsa-lib/test/latency.c'.
.. visions of an opensource realtime portable
multichannel blackbox audio processor..
On Wed, 23 Jan 2002, Maarten de Boer wrote:
When I run the alsa-lib/test/latency (CVS), like this:
[...]
./latency -r 44099 -m 512 -M 512 -c 1 -s 2000 -p
[...]
after about 40 seconds, the signal gets distorted badly
and gets worse over time. It happens independ of the
buffer size.
I
On Thu, 17 Jan 2002, Paul Davis wrote:
What's going to happen with usb audio/midi support ?
Since alsa should become the kernel standard driver for audio/midi/seq
devices and all the work the usb people have done to support the audio
class is based on the oss-api does that mean with 2.5 or
While compiling the latest CVS-tree I get the following... any ideas?
[ ... alsa-lib/src/pcm/ ]
/bin/sh ../../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../include
-I../../include-g -O2 -c pcm_lfloat.c
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I../../include -g -O2
On Tue, 9 Oct 2001, Kai Vehmanen wrote:
). Now this causes a more-or-less complete system-freeze (SMP, user
priviledges). The latest ecasound development version (2.1dev0) failed to
A minor correction, bug also happens on non-SMP machines. I meant to say
that the nature of the system-freeze
75 matches
Mail list logo
