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: 657051" data-attributes="member: 10858"><p>Yep, its 50 ms.</p><p></p><p></p><p></p><p>Yep, since there should be only 10 ms - 5 ms == 5 ms A/V sync issue.</p><p></p><p></p><p>Currently I have no clue how to solve the issue with these types of audio cards / drivers that have different latency when compared to the buffer size (in ms). The problem is quite easy to understand. Directshow requests the preroll time before we know how big the audio card / driver latency is. This is also an issue with some cards and AC3 encoding since the buffer size will be changed on the fly to match the driver's request.</p><p></p><p>We could always set the preroll to be zero ms and then just drop the data to match the latency, but it would be not so good since it would introduce the amount of audio devices latency amount of dropped data in the beginning of playback (mainly silence).</p></blockquote><p></p>
[QUOTE="tourettes, post: 657051, member: 10858"] Yep, its 50 ms. Yep, since there should be only 10 ms - 5 ms == 5 ms A/V sync issue. Currently I have no clue how to solve the issue with these types of audio cards / drivers that have different latency when compared to the buffer size (in ms). The problem is quite easy to understand. Directshow requests the preroll time before we know how big the audio card / driver latency is. This is also an issue with some cards and AC3 encoding since the buffer size will be changed on the fly to match the driver's request. We could always set the preroll to be zero ms and then just drop the data to match the latency, but it would be not so good since it would introduce the amount of audio devices latency amount of dropped data in the beginning of playback (mainly silence). [/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
