Ok, here's my stupid question of the day:
Is there any way for a program to query the alsa-lib to determine the version number? Ie... Assuming I'm using the relase of alsa-lib-1.0.4, I'd like to query and get back something that would indicate that I'm using that release (and I don't even care
Hey,
The library API documentation looks to be out of date. Going to:
http://www.alsa-project.org/documentation.php3#Library
and clicking on the latest on-line documentation link:
http://www.alsa-project.org/alsa-doc/alsa-lib/
gives me documentation that was generated on Nov 25, 2003. I notice
We went ahead and added code to our alsa client software to cleanly
return to a PCM value of 0 and then stuffed a full buffer worth of 0s
into the buffer before closeing the PCM in order to solve our pop
problem. I'm not sure how the OSS emulation stuff works since we don't
use it, but maybe
Takashi,
I've completed my changes on the serial-u16550 driver. I have
implemented most of your suggestions to my previous patch. Now:
* There is a user selectable flag droponfull. Set to 1 and
any new bytes delivered to the driver after the buffer fills
up will be discarded until the
All,
We're having a problem with some of our audio applications. When a song
starts playing we will often hear a loud pop out of the speakers before
it plays audio. It seems dependent upon where we stoped and the specfic
content of the last song, if we hit our stop control and abort in the
starting a native Alsa
application like alsaplayer.
Does this sound at all like what you're experiencing?
- Mark
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Steve
deRosier
Sent: Wednesday, November 19, 2003 2:15 PM
To: [EMAIL PROTECTED]
Subject: [Alsa
Steve deRosier wrote:
All,
We're having a problem with some of our audio applications. When a
song starts playing we will often hear a loud pop out of the speakers
before it plays audio. It seems dependent upon where we stoped and
the specfic content of the last song, if we hit our stop
Takashi Iwai wrote:
At Thu, 30 Oct 2003 13:33:37 -0800,
Steve deRosier wrote:
Takashi,
Thanks for your response. I've addressed your issues below. Let's
discuss this and if necessary I'll modify my fix.
1. Move all checks of buffer overflow and such to the
actual buffer write and read
Takashi,
Thanks for your response. I've addressed your issues below. Let's
discuss this and if necessary I'll modify my fix.
1. Move all checks of buffer overflow and such to the
actual buffer write and read routines. This makes
the buffer routines more robust and encaspulates buffer
I am submitting a patch to the serial-u16550 driver fix a bug
that we have encountered. Basically, when using the
SNDRV_SERIAL_GENERIC adaptor in the serial-u16550 MIDI driver,
if the device becomes unplugged or some other condition where
the device stops signaling CTS, the send buffer backs
when the state is OPEN, these values are bogus, since snd_pcm_status()
returns immediately without putting the values.
So, alsa writes bogus data to the proc entries? Maybe it shouldn't
write bad data, just leave the spots blank, initilize with 0's or
something else?
-
hw_ptr :
All,
We've noticed a problem with the newest version of Alsa while doing some
stress testing of our devices. Basically, the scenerio is we're playing
through a large library of .ogg files over the weekend. When we checked
on the progress upon getting in on Monday, we discovered that the PCM
Jaroslav,
You've probably been distracted with more pressing matters, but are you
still looking at this issue? I'd be happy to look into it or fix it
myself if you could give me some ideas of where/what/how to fix it.
Thanks,
- Steve
Steve deRosier wrote:
Jaroslav, thanks for replying. I'm
to make this work so I can
fix it myself and give you guys a patch.
Help, please!?!?
Thanks,
- Steve
Steve deRosier wrote:
All,
I hope that someone here can help with a problem we're having with the
newer versions of the alsa-lib. We are using the ladspa interface with
alsa to use a pitch
Jaroslav, thanks for replying. I'm not 100% sure that my setup is right
(it was quoted in the origional email), but since it used to work with
these setings, but now doesn't...?...
I've looked over both the setup in my asound.conf and the output from
the verbose mode aplay and I have nearly
All,
I hope that someone here can help with a problem we're having with the
newer versions of the alsa-lib. We are using the ladspa interface with
alsa to use a pitch-shifting plugin. It worked fine with earlier
versions of the alsa lib, but with the newer versions it produces no
sound
Paul,
Ah, well that explains it. Thanks. Can you point me to some info on
how I would link the two clocks (I guess it would be to make the seq use
the PCM clock)?
As far as using kernel 2.5/2.6 or the backport of the hi-res timers
code... unfortunately this isn't an option for me. I can't
I'm writting an app that plays a special format and uses both the Alsa
seq and pcm interfaces to output MIDI and audio data together. I'm
almost done, but I've got one problem that is plaugeing me: I can't get
the two to stay in sync.
Basically, what I'm doing is using writei() to send frames
18 matches
Mail list logo
