home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
General Development (no feature request here!)
MediaPortal Audio renderer - better video playback quality
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="tourettes" data-source="post: 638086" data-attributes="member: 10858"><p>I thin the NULL buffer is drivers reaction to our request for zero bytes sized buffer. I'll check if that happens on my dev PC as well (zero bytes requested, hopefully yes so I can debug it easier).</p><p></p><p>Those could (or actually should) be heard as clicks / jumps / pops etc. since there will be a small amount of audio data that is going not to be rendered when such happens.</p><p></p><p></p><p></p><p>This is also source for click / po(o)p noise that you will hear. It just tells that CPU was not able to fill the buffers as quickly as driver / HW eats the data. Mainly the smaller the latency / buffer size the more timi critical the whole buffer filling will be (so less other processes, video decoding etc. should be happening).</p></blockquote><p></p>
[QUOTE="tourettes, post: 638086, member: 10858"] I thin the NULL buffer is drivers reaction to our request for zero bytes sized buffer. I'll check if that happens on my dev PC as well (zero bytes requested, hopefully yes so I can debug it easier). Those could (or actually should) be heard as clicks / jumps / pops etc. since there will be a small amount of audio data that is going not to be rendered when such happens. This is also source for click / po(o)p noise that you will hear. It just tells that CPU was not able to fill the buffers as quickly as driver / HW eats the data. Mainly the smaller the latency / buffer size the more timi critical the whole buffer filling will be (so less other processes, video decoding etc. should be happening). [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
MediaPortal Audio renderer - better video playback quality
Contact us
RSS
Top
Bottom
