On 14-Jul-2003 James Courtier-Dutton wrote:
>>>Worst case accuracy is about one period AFAIK. It depends on the sound chip
>>>because the low level driver reads the DMA pointer (or something) from some
>>>hardware register or it can know the DMA pointer when it receives an interrupt
>>>at the end
Takashi Iwai wrote:
At Fri, 11 Jul 2003 17:28:08 +0200,
Giuliano Pochini wrote:
On Thu, 10 Jul 2003 16:31:28 +0100
James Courtier-Dutton <[EMAIL PROTECTED]> wrote:
Hi,
When an application reads the "avail" or "delay" pcm values: -
1) how accurate are they?
2) does the accuracy depend on the sound
At Fri, 11 Jul 2003 17:28:08 +0200,
Giuliano Pochini wrote:
>
> On Thu, 10 Jul 2003 16:31:28 +0100
> James Courtier-Dutton <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > When an application reads the "avail" or "delay" pcm values: -
> > 1) how accurate are they?
> > 2) does the accuracy depend on t
On Thu, 10 Jul 2003 16:31:28 +0100
James Courtier-Dutton <[EMAIL PROTECTED]> wrote:
> Hi,
>
> When an application reads the "avail" or "delay" pcm values: -
> 1) how accurate are they?
> 2) does the accuracy depend on the sound card driver being used.
Worst case accuracy is about one period AFAIK
Hi,
When an application reads the "avail" or "delay" pcm values: -
1) how accurate are they?
2) does the accuracy depend on the sound card driver being used.
The reason I ask this, is that I am going to be writing an alsa driver
for bluetooth headsets.
With bluetooth headsets, sound is sent to th
