Re: [LAD] Allocating 96 but reading 16 (multple times)

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <linux-audio-dev@...>
Date: Wednesday, February 16, 2011 - 12:12 am

On Wednesday 16 February 2011, at 00.33.49, Jens M Andreasen
wrote:
[...]

[...]

To quick to post there!

This could mean that you simply have too little buffering between input and
output. Does your application actually define that? (With read()/write() APIs,
you usually have to do this by "pre-buffering" on the output before entering
the actual processing loop.)

The reason why it works better with 16 frames is probably that the driver
starts by waiting for your write()s to fill upp the output buffer, thus adding
one DMA buffer's worth of extra buffering between the input and output.

--
//David Olofson - Consultant, Developer, Artist, Open Source Advocate

.--- Games, examples, libraries, scripting, sound, music, graphics ---.
| http://consulting.olofson.net http://olofsonarcade.com |
'---------------------------------------------------------------------'
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAD] Allocating 96 but reading 16 (multple times), Jens M Andreasen, (Tue Feb 15, 11:34 pm)
Re: [LAD] Allocating 96 but reading 16 (multple times), David Olofson, (Wed Feb 16, 12:12 am)
Re: [LAD] Allocating 96 but reading 16 (multple times), David Olofson, (Wed Feb 16, 12:07 am)