ok paul i had another look at the driver playback/capture tutorials. I have one question.Do applicationsinitialize and use a pcm_handle of the alsa driver when they begin interaction with it?Surely not
I thought that the driver would work totally independently of my VoIP and this is why I
Hi ,
i'm trying to change the fragment size that the alsa
driver is capturing/playing out. It's currently set at
32 msecs(256 bytes).
They are set in the runtime structure...
runtime-period_max ...etc
Could anybody tell me which file these parameters are
set in the alsa-driver directory?
--- Paul Davis [EMAIL PROTECTED] wrote:
Hi ,
i'm trying to change the fragment size that the
alsa
driver is capturing/playing out. It's currently set
at
32 msecs(256 bytes).
They are set in the runtime structure...
runtime-period_max ...etc
Could anybody tell me which file these
to driver sending buffer every 32 msecs.However this does not match for GSM because it needs only 132 bytes every 64/96 msecs.
Can the driver change the amount of data it gets from the soundcard to suit the codec?
Help appreciated,Brian.James Courtier-Dutton [EMAIL PROTECTED] wrote:
Brian Furey wrote
Hi All,
with the ALSA driver, what do the OSS substream
mean?If you have a 2 main capture channels, how many
substream would you have?
Also the capture stream is supposed to operate at 8000
Hz per second.Is it possible that it is actually say
8192, a value to the power-of-two?
How can I find
Hi All,
i'm using an open source VoIP application with the
alsa driver. My card is the onboard intel8x0.
My problem is figuring out the patterns I am
getting with the alsa driver when transmitting
packets.
For instance when I use the GSM codec with a packets
size of 80 msecs and 132 bytes,
, 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 transmitted every 32
Hi All,
still trying to get the hardware and software
runtime paramters of the driver...
In alsa-driver*/alsa-kernel/core there is the pcm.c
file.
There are 2 functions in this file
snd_pcm_substream_proc_hw_params_read
and
snd_pcm_substream_proc_sw_params_read
Both of these print out to
trying to find out the reason packets
are transmitted at alternate intervals of 64 and 96
millisecondsand the runtime period size is the key
help appreciated,
brian.
--- James Courtier-Dutton [EMAIL PROTECTED]
wrote: Brian Furey wrote:
Hi all,
I have an intel810 onboard soundcard.I am
Hi all,
I have an intel810 onboard soundcard.I am using the
alsa driver with a VoIP session.
The intel8x0.c file has a minimum period byte size
of 32 bytes with the minimum no. of periods being
1.The min and max rate is set to 48k.
How can I find out what actual(runtime) size period
the
application and check contents of text
file.
Am I right in saying this?
Thanks in advance,
Brian.
--- Jaroslav Kysela [EMAIL PROTECTED] wrote: On Tue,
30 Mar 2004, Brian Furey wrote:
Hi all,
I have an intel810 onboard soundcard.I am using
the
alsa driver with a VoIP session
Thanks Giuliano,
How can I get a dump of the current hardware configuration space?I have the ALSA driver 1.0.0 installed on my Redhat 9 Machine.
Brian.Giuliano Pochini [EMAIL PROTECTED] wrote:
On 24-Mar-2004 Brian Furey wrote: Hi all, im using the ALSA driver 1.0.0 on two linux machines
Hi all,
im using the ALSA driver 1.0.0 on two linux machines that connect a voice-over-ip session.
I need to know the minimum fragment size that the alsa drivercan take from the soundcard and place in the sending/receiving buffer.Does it depend on the speed that the soundcard is operating at?
Any
13 matches
Mail list logo
