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!)
MP1 EVR Presenter/dshowhelper community development
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="Jong" data-source="post: 610285" data-attributes="member: 104040"><p>Yes, EOP sounds like a safer thing to set, regardless of Reclock. Don't think this. by itself, will help us use Reclock vsync correction in combination with your code though.</p><p></p><p>I don't pretend to know the answer to your second question. One place I would try though is to see how Sync Renderer calculates its "Actual Frame Rate". Even when speeding up 23.976fps material to 25p this still shows 23.976. But when vsync correction kicks in, this speeds up or slows down slightly, showing the correction Reclock is making to move EOP to its target. If you force Reclock to playback at the original speed then this figure jumps all over the place, so it cannot be used as it is, but it looks like if you look at the formula you might be able to derive the correction being applied?</p><p></p><p><strong><em>I have had a thought, though, about how you might be able to use Reclock to fix drift without access to a special API!</em></strong></p><p></p><p>It seems to me that if you could control EOP accurately enough to ensure Reclock vsync correction does not normally engage, you could 'simply':</p><p></p><p>- make a note of the "Sample Paint Time Correction" at the start of playback - the adjustment you are making to ensure SOP is at a safe point.</p><p>- allow it to drift, say, 70% of a frame without turning on Reclock vsync correction</p><p>- when it gets to this point, make your presenter deliberately push your EOP target outside of Reclock's comfort zone in the direction that will bring the "Sample Paint Time Correction" back to its original position.</p><p>- The further EOP is from the target the greater the clock adjustment Reclock will make, so to minimise the time any audio pitch adjustment is being made it might be worth making the EOP move quite a way at the start (but still 'safe', of course) and then slowly move it back towards its normal position as "Sample Paint Time Correction" gets close to its original position, to minimise potential for overshoot.</p><p></p><p>There should never be a need for <em><strong>any </strong></em>frame drop (major Windows scheduling gaffs aside!) and, if the original media speed and refresh rate are compatible (24p@23.976Hz, 24p@59.94Hz, 25p@50Hz) the audio will only have to be pitch corrected once or twice in a movie for a few seconds. The adjustments are truly tiny so it should be inaudible anyway, but for those that don't like any "messing" this is much closer. Of course PCM audio is still being resampled, this is unavoidable if Reclock is improving the reference clock, but most of the time it will be very benign and the upside is <strong><em>no dropped frames at all</em></strong>!</p><p></p><p>If you have a problem setting EOP tightly enough to ensure Reclock vsync correction is not engaged unless you want it to be we could ask James to add a registry value that defines the size of the Reclock target zone. As I mentioned before, it used to be much larger, about 3ms and he reduced the value for me to 0.5ms. I imagine he would be happy to let this be defined in the registry as a percentage of screen size.</p><p></p><p>What do you think?</p></blockquote><p></p>
[QUOTE="Jong, post: 610285, member: 104040"] Yes, EOP sounds like a safer thing to set, regardless of Reclock. Don't think this. by itself, will help us use Reclock vsync correction in combination with your code though. I don't pretend to know the answer to your second question. One place I would try though is to see how Sync Renderer calculates its "Actual Frame Rate". Even when speeding up 23.976fps material to 25p this still shows 23.976. But when vsync correction kicks in, this speeds up or slows down slightly, showing the correction Reclock is making to move EOP to its target. If you force Reclock to playback at the original speed then this figure jumps all over the place, so it cannot be used as it is, but it looks like if you look at the formula you might be able to derive the correction being applied? [B][I]I have had a thought, though, about how you might be able to use Reclock to fix drift without access to a special API![/I][/B] It seems to me that if you could control EOP accurately enough to ensure Reclock vsync correction does not normally engage, you could 'simply': - make a note of the "Sample Paint Time Correction" at the start of playback - the adjustment you are making to ensure SOP is at a safe point. - allow it to drift, say, 70% of a frame without turning on Reclock vsync correction - when it gets to this point, make your presenter deliberately push your EOP target outside of Reclock's comfort zone in the direction that will bring the "Sample Paint Time Correction" back to its original position. - The further EOP is from the target the greater the clock adjustment Reclock will make, so to minimise the time any audio pitch adjustment is being made it might be worth making the EOP move quite a way at the start (but still 'safe', of course) and then slowly move it back towards its normal position as "Sample Paint Time Correction" gets close to its original position, to minimise potential for overshoot. There should never be a need for [I][B]any [/B][/I]frame drop (major Windows scheduling gaffs aside!) and, if the original media speed and refresh rate are compatible (24p@23.976Hz, 24p@59.94Hz, 25p@50Hz) the audio will only have to be pitch corrected once or twice in a movie for a few seconds. The adjustments are truly tiny so it should be inaudible anyway, but for those that don't like any "messing" this is much closer. Of course PCM audio is still being resampled, this is unavoidable if Reclock is improving the reference clock, but most of the time it will be very benign and the upside is [B][I]no dropped frames at all[/I][/B]! If you have a problem setting EOP tightly enough to ensure Reclock vsync correction is not engaged unless you want it to be we could ask James to add a registry value that defines the size of the Reclock target zone. As I mentioned before, it used to be much larger, about 3ms and he reduced the value for me to 0.5ms. I imagine he would be happy to let this be defined in the registry as a percentage of screen size. What do you think? [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
MP1 EVR Presenter/dshowhelper community development
Contact us
RSS
Top
Bottom