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: 650895" data-attributes="member: 10858"><p>According the driver - event based renderering mode (non-polling) is not supported by the device itself. Shame on the HW maker. Currently the audio device you have is not compatible with the best possible WASAPI mode we have (and MP audio renderer doesn't support anymore the poll based one - the one you earlier had serious trouble with the other audio device(s) ). Of course it could be just the driver that reports the wrong properties to OS / WASAPI, but we cannot know. Maybe you could ask from the manufacturer?</p><p></p><p>Audio renderer.log itself doesn't show any dropped data, so all buffers that the WASAPI / driver are requesting to be filled are completed nicely.</p></blockquote><p></p>
[QUOTE="tourettes, post: 650895, member: 10858"] According the driver - event based renderering mode (non-polling) is not supported by the device itself. Shame on the HW maker. Currently the audio device you have is not compatible with the best possible WASAPI mode we have (and MP audio renderer doesn't support anymore the poll based one - the one you earlier had serious trouble with the other audio device(s) ). Of course it could be just the driver that reports the wrong properties to OS / WASAPI, but we cannot know. Maybe you could ask from the manufacturer? Audio renderer.log itself doesn't show any dropped data, so all buffers that the WASAPI / driver are requesting to be filled are completed nicely. [/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
