#39
- Created on2006-11-30 01:01
- Reported by
- StatusFixed
- PriorityHigh (2)
- Assigned to
- Milestone
- Plan Level-
- Due Date-
PA/ALSA recommended deviceInfo->defaultOutputLatency will lead to bad pops
From: meyer@mesw.de
Subject: Re: [Portaudio] Sample Rate and FrameCount
Date: November 28, 2006 1:08:17 PM EST
To: Axel.Roebel@ircam.fr
Cc: portaudio@techweb.rfa.org, bjorn@xowave.com
We use paFramesPerBufferUnspecified, but set a higher output latency
>(because default output latency will lead to bad pops at least on
>ALSA/v19 -- this has been reported by a number of people already.) >The
>API will then calculate a reliable buffer size for you automatically. >No
>problems with this strategy so far.
Markus
META TICKET: #97 [META] Some PA recommended deviceInfo->default*Latency values are bad or unimplemented
Subject: Re: [Portaudio] Sample Rate and FrameCount
Date: November 28, 2006 1:08:17 PM EST
To: Axel.Roebel@ircam.fr
Cc: portaudio@techweb.rfa.org, bjorn@xowave.com
We use paFramesPerBufferUnspecified, but set a higher output latency
>(because default output latency will lead to bad pops at least on
>ALSA/v19 -- this has been reported by a number of people already.) >The
>API will then calculate a reliable buffer size for you automatically. >No
>problems with this strategy so far.
Markus
META TICKET: #97 [META] Some PA recommended deviceInfo->default*Latency values are bad or unimplemented
Leave a comment
Default output latency should not lead to bad pops. This is a bug. The fact that multiple people have reported it means that it is not an isolated issue. The fix would be to determine safe default values for most or all systems (by trial and error or test program) and commit them.
