On Tue, 5 Oct 2010 09:30:37 -0400
Paul Braman wrote:
> Sergei Steshenko wrote:
> >
> > Maybe these:
> >
> > http://www.alsa-project.org/main/index.php/Low_latency_howto
> > https://lwn.net/Articles/120797/
> >
> > can help ?
>
> That is certainly some interesting stuff but not entirely relevant
On Tue, 5 Oct 2010 09:30:37 -0400
Paul Braman wrote:
> The problem is that there is no good way to discover or set these
> things that seems "official." There are semi-official suggestions of
> "set to maximum buffer and divide into four periods" or "buffer about
> a second and divide into about
Sergei Steshenko wrote:
>
> Maybe these:
>
> http://www.alsa-project.org/main/index.php/Low_latency_howto
> https://lwn.net/Articles/120797/
>
> can help ?
That is certainly some interesting stuff but not entirely relevant to
the discussion at hand. Currently, I do not have latency requirements
fo
On Sun, 3 Oct 2010 00:46:27 -0400
Paul Braman wrote:
> Paul Braman wrote:
> >
> > I guess therein lies some of the fundamental difference with how I was
> > previously thinking. I figured I could just ask the driver/device for
> > some basic defaults that should work but, instead, I should *tell*
On Sun, 3 Oct 2010, Paul Braman wrote:
> Paul Braman wrote:
>>
>> I guess therein lies some of the fundamental difference with how I was
>> previously thinking. I figured I could just ask the driver/device for
>> some basic defaults that should work but, instead, I should *tell* it
>> what basic d
Paul Braman wrote:
>
> I guess therein lies some of the fundamental difference with how I was
> previously thinking. I figured I could just ask the driver/device for
> some basic defaults that should work but, instead, I should *tell* it
> what basic defaults I can live with. (Set buffer size near
Jaroslav Kysela wrote:
>
> My suggestion was to set something reasonable - the application should
> give hints for what purpose the stream parameters are.
I guess therein lies some of the fundamental difference with how I was
previously thinking. I figured I could just ask the driver/device for
so
On Fri, 24 Sep 2010, Paul Braman wrote:
> Well, so far no-one has been able to sufficiently answer my inquiry
> about how proper default ALSA sound capture should be coded. I've done
> enough research to know that my program is getting an underrun
> condition on the read. Fine.
>
> My question rem
Well, so far no-one has been able to sufficiently answer my inquiry
about how proper default ALSA sound capture should be coded. I've done
enough research to know that my program is getting an underrun
condition on the read. Fine.
My question remains...
When I set the hardware parameters, who sho
It seems like I must be missing something when it comes to recording
audio from a device. What I expect to happen is for me to set some
simple parameters (much like I do using OSS) and then have the API
tell me what the best buffer size is for the device so that I can read
reliably. For example ..
10 matches
Mail list logo
