Pedro Lopez-Cabanillas wrote:
This patch adds three new options to arecordmidi.
Committed, with some changes.
Thanks,
Clemens
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins,
On Mon, 5 Apr 2004, Mathieu Rondonneau wrote:
I don't use aplay to play the wav file but i use:
dd of=thefile.wav of=/dev/audio0
This is definitely wrong. The /dev/audio devices expect mu-Law
format at 8000Hz.
Jaroslav
-
Jaroslav Kysela
Robert Rozman wrote:
I've got advice how to use this 6 channel device as 3 stereo channels but
there seems something not to be right (it could be my mistake).
I have /etc/asound.conf :
pcm.a {
type plug
slave.pcm ch12
}
pcm.b {
type plug
slave.pcm ch34
}
Now I do:
- alsaplayer
Tom Browne wrote:
Clemens Ladisch wrote:
Tom Browne wrote:
Under certain conditions (yet to be established properly - it doesn't
happen every single time) with this ICE1712 card (DSP24),
snd_pcm_writei doesn't just block... it never comes back.
What is the state of the PCM device when
On Mon, 5 Apr 2004, Eliot Blennerhassett wrote:
TAS1020:
http://focus.ti.com/docs/prod/folders/print/tas1020b.html
But I guess the exact features depend on firmware...
OK, I think this is the most difficult option which is possible?! What
should I do now, is reverse engineering possible at
John H. wrote:
the usb 2.0 hub was at fault,. thanks!
I have heard rumors that the latest 2.6.5 kernel is supposed to have
support for playing audio data through 2.0 hubs to 1.x devices.
HTH
Clemens
---
This SF.Net email is sponsored by:
Patrick Boettcher wrote:
On Mon, 5 Apr 2004, Clemens Ladisch wrote:
What sample rate/format uses 304000 bytes per second?
I don't understand the question completely, what do you mean?
The descriptors say that the device can transfer up to 304000 bytes
per second in each direction. What
Clemens Ladisch wrote:
state: PREPARED
The pcm isn't (yet) running.
avail : 5
And the buffer is almost full. snd_pcm_writei blocks because it
cannot write more data to the buffer, probably because the transfer
threshold is too high.
?! See below...
How do you start the pcm? If
On Tue, 6 Apr 2004, Tom Browne wrote:
Clemens Ladisch wrote:
state: PREPARED
The pcm isn't (yet) running.
avail : 5
And the buffer is almost full. snd_pcm_writei blocks because it
cannot write more data to the buffer, probably because the transfer
threshold is too high.
Jaroslav Kysela wrote:
alsa_buffer_size = snd_pcm_hw_params_get_buffer_size(params);
err = snd_pcm_hw_params_set_period_time_near(handle, params,
alsa_period_time, dir);
alsa_period_size = snd_pcm_hw_params_get_period_size(params, dir);
...
err =
On Tue, 6 Apr 2004, Tom Browne wrote:
Jaroslav Kysela wrote:
alsa_buffer_size = snd_pcm_hw_params_get_buffer_size(params);
err = snd_pcm_hw_params_set_period_time_near(handle, params,
alsa_period_time, dir);
alsa_period_size = snd_pcm_hw_params_get_period_size(params, dir);
...
Jaroslav Kysela wrote:
Which gives threshold = 6552 from buffer=6553, period=3276...
exactly the same value as the code I was already using gives! What
else am I missing from the garish red and yellow blocks of WinDiff?
Then it really appears like a bug. Could you add snd_pcm_dump() call
Am Dienstag 06 April 2004 02:10 schrieb Rui Nuno Capela:
Now comes the weird part. No, I couldn't get it to work unless I set
--with-debug=full on configure line. And I've tested several times,
believe me.
FYI, I'm stick with 2.6 kernel tree, and already tested with 2.6.4 and
latest 2.6.5.
Hi,
I am running a test application on my alsa driver for arm platform.Driver
is statically built.
The test application calls the snd_pcm_open.
With device hw:0,0
At the target I have created sound driver files with snddevices.sh
In /proc/asound i have the
On Tue, 6 Apr 2004 16:44:56 +0530
Pavana Sharma [EMAIL PROTECTED] wrote:
Hi,
I am running a test application on my alsa driver for arm
platform.Driver
is statically built.
The test application calls the snd_pcm_open.
With device hw:0,0
At the target I have
Hi,
chekout these versions ..I am using,
which version of alsa-drivers do you use [cat /proc/asound/version]?
Advanced Linux Sound Architecture Driver Version 1.0.2c (Thu Feb 05 15:41:49
2004 UTC).
which verison of alsa-utils do you use [aplay --version]
aplay: version 1.0.3 by Jaroslav
On Tue, 6 Apr 2004, Pavana Sharma wrote:
Hi,
I am running a test application on my alsa driver for arm platform.Driver
is statically built.
The test application calls the snd_pcm_open.
With device hw:0,0
At the target I have created sound driver files with
Am Dienstag 06 April 2004 12:52 schrieb Karsten Wiese:
Am Dienstag 06 April 2004 02:10 schrieb Rui Nuno Capela:
Now comes the weird part. No, I couldn't get it to work unless I set
--with-debug=full on configure line. And I've tested several times,
believe me.
FYI, I'm stick with 2.6
Karsten Wiese wrote:
Now comes the weird part. No, I couldn't get it to work unless I set
--with-debug=full on configure line. And I've tested several times,
believe me.
FYI, I'm stick with 2.6 kernel tree, and already tested with 2.6.4 and
latest 2.6.5.
My way of building the kernel
hi Jaroslav,
This file is present. The only other thing which I wanted to bring
into your notice is that the file system we are using is a busybox file
system, with no bash. Instead it has smaller shell ash. Will that make a
difference.
And this file /usr/share/alsa/alsa.conf is only
On Tue, 6 Apr 2004, Gupta, Kshitij wrote:
hi Jaroslav,
This file is present. The only other thing which I wanted to bring
into your notice is that the file system we are using is a busybox file
system, with no bash. Instead it has smaller shell ash. Will that make a
difference.
No,
Pavana Sharma wrote:
Hi,
I am running a test application on my alsa driver for arm platform.Driver
is statically built.
The test application calls the snd_pcm_open.
With device hw:0,0
At the target I have created sound driver files with snddevices.sh
In
Pavana Sharma wrote:
ALSA lib pcm.c:1947:(snd_pcm_open_noupdate) Unknown PCM hw:0,0
Please show the output of aplay -l and aplay -L.
Clemens
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by
I wrote:
I think I'll write a quirk for this ...
Please try the attached patch.
HTH
Clemens
diff -urN alsaold/alsa-kernel/usb/usbaudio.c alsa/alsa-kernel/usb/usbaudio.c
--- alsaold/alsa-kernel/usb/usbaudio.c Tue Mar 30 13:51:30 2004
+++ alsa/alsa-kernel/usb/usbaudio.c Tue Apr 6 13:20:36
On Tue, 6 Apr 2004, Brian Furey wrote:
Hi all,
i'm running the alsa-driver-1.0.0. Im using it with
the OpenH323 application. Packets are transmitted or
received in 32 millisecond intervals or multiples of
32 millisecond intervals.
For example using the G711 codec, packets are
Jaroslav,
Busy system cant explain something as consequent as this.
When the packet size being transmitted is 30 msecs(240bytes) or 32 msecs(240bytes), the OpenH323 app sends packets every 32 msecs.
When the packet size is 80 msecs(132 bytes), the OpenH323 app sends packets at alternate intervals
Now comes the weird part. No, I couldn't get it to work unless I set
--with-debug=full on configure line. And I've tested several times,
believe me.
Attached diff fixed it here.
Please verify.
CU
Index: alsa-driver/usb/usx2y/usbusx2y.c
On Tue, 6 Apr 2004, Clemens Ladisch wrote:
I wrote:
I think I'll write a quirk for this ...
Please try the attached patch.
Sorry, don't have lots time now, I only applied the patch, loaded the
module, pluged in the device ... result is attached.
Unfortunately I'm (still) not familar with
Karsten Wiese
Now comes the weird part. No, I couldn't get it to work unless I set
--with-debug=full on configure line. And I've tested several times,
believe me.
Attached diff fixed it here.
Please verify.
CU
First try and it works, that is without debug enabled.
Thankful.
--
I can't find any way to detect the running ALSA version, for diagnostic
purposes. It can't be derived from the library name, which doesn't seem
to change (it's always libasound.so.2.0.0 here, which has no relation
to the actual version).
It's frustrating to receive bug reports like
I can't find any way to detect the running ALSA version, for diagnostic
cat /proc/asound/version
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo
Hi Jaroslav,
Please commit this with comments
- US224 support
- FIX for build without CONFIG_SND_DEBUG
Thanks,
Karsten
Index: usb/usx2y/usX2Yhwdep.c
===
RCS file: /cvsroot/alsa/alsa-driver/usb/usx2y/usX2Yhwdep.c,v
Glenn Maynard wrote:
On Tue, Apr 06, 2004 at 05:04:34PM -0400, Paul Davis wrote:
I can't find any way to detect the running ALSA version, for diagnostic
cat /proc/asound/version
That's the driver version, which I'm already logging. Like I said, I
want the alsa-lib version that's being linked
On Tue, Apr 06, 2004 at 11:16:17PM +0100, James Courtier-Dutton wrote:
cat /usr/include/alsa/version.h tells you the currently installed version.
Nope. That only works if the development files are installed; on user
systems, they usually aren't. I can't simply #include it; that'll tell
me
34 matches
Mail list logo
