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: 671536" data-attributes="member: 10858"><p>Difference between event driven mode and the polling mode is related to the glitch resistant. In even driven mode the HW / drivers are telling to audio renderer when the WASAPI buffer is requiring filling where as in polling mode the audio renderer uses a timer to check the buffer state periodicly. There are two cons of that polling </p><p></p><p>1) It is not as robust so it is more error prone to have buffer underruns when there is some system activuty (high HD trafic, CPU usage etc.)</p><p>2) It uses slightly more CPU (not enough to make any actual difference)</p><p></p><p></p><p></p><p>Code is ready and in SVN, but I'm currently waiting more test results from the v15 before releasing (and maybe few patches from davidf <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" />). The difference approach for the drift data collection reset should workaround the bad clock data we get (but the clock data still itself make some errors still - but should be at least better when it comes to fixing the drift on Xonar).</p></blockquote><p></p>
[QUOTE="tourettes, post: 671536, member: 10858"] Difference between event driven mode and the polling mode is related to the glitch resistant. In even driven mode the HW / drivers are telling to audio renderer when the WASAPI buffer is requiring filling where as in polling mode the audio renderer uses a timer to check the buffer state periodicly. There are two cons of that polling 1) It is not as robust so it is more error prone to have buffer underruns when there is some system activuty (high HD trafic, CPU usage etc.) 2) It uses slightly more CPU (not enough to make any actual difference) Code is ready and in SVN, but I'm currently waiting more test results from the v15 before releasing (and maybe few patches from davidf :)). The difference approach for the drift data collection reset should workaround the bad clock data we get (but the clock data still itself make some errors still - but should be at least better when it comes to fixing the drift on Xonar). [/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