Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > Hardware & Software > Software players

Reply
 
Thread Tools Search this Thread Display Modes
Old 27th July 2017, 20:41   #44441  |  Link
Asmodian
Registered User
 
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,406
No. 0.1% faster does not matter at all.

Use 75 Hz instead of 60 Hz if you can but 59 = 60 Hz as far as smooth motion is concerned.
__________________
madVR options explained
Asmodian is offline   Reply With Quote
Old 27th July 2017, 21:13   #44442  |  Link
clsid
*****
 
Join Date: Feb 2005
Posts: 5,642
Try both and compare average render time. 59hz might result in less blended frames, which means better quality and performance.
clsid is offline   Reply With Quote
Old 27th July 2017, 21:49   #44443  |  Link
sauma144
Registered User
 
Join Date: Sep 2016
Posts: 89
I thought smoothmotion was optimized for 60hz!
If it's really better with high framerate, it would be interesting to let madVR switches the framerate of the current display to the highest available one automatically.

Last edited by sauma144; 27th July 2017 at 21:53.
sauma144 is offline   Reply With Quote
Old 27th July 2017, 21:57   #44444  |  Link
clsid
*****
 
Join Date: Feb 2005
Posts: 5,642
No, it isn't optimized for a specific framerate. And you should not take it literally that highest is best for it, just generally speaking.

59.9 and 60 are practically same value, so using 60 purely because it is highest is nonsense. 59.9 may be better match with most video content framerates.
clsid is offline   Reply With Quote
Old 27th July 2017, 22:10   #44445  |  Link
huhn
Registered User
 
Join Date: Oct 2012
Posts: 7,903
while the difference between 59p and 60p is not worth it higher is always better with smoothmotion. smoothmotion is fixing clock deviations so you should get the "same" number of blended frames with 59 and 60. the really important part is the time a blended frame is shown.
huhn is offline   Reply With Quote
Old 27th July 2017, 22:48   #44446  |  Link
clsid
*****
 
Join Date: Feb 2005
Posts: 5,642
I disagree. Smoothmotion is also useful when you have a perfect clock, but framerate is not a exact multiple. In that case 59.94 (2.5 x 23.976) would be better than 60.0. But given the blending threshold, it might not even make much of a difference. But this is a pointless discussion. They can just try and test if there is a difference or not.
clsid is offline   Reply With Quote
Old 27th July 2017, 23:19   #44447  |  Link
huhn
Registered User
 
Join Date: Oct 2012
Posts: 7,903
but a perfect clock is impossible i mean it has to be absolute perfect.

so even with a repeated frame every 2 hour you are off 21 ms after 1 h.
and do we even start in perfect sync?

with a perfect 100% matching clocks it would only need to blend a frame every 5 frames but this is not going to happen is this even remotely possible with direct show?
huhn is offline   Reply With Quote
Old 28th July 2017, 00:34   #44448  |  Link
Asmodian
Registered User
 
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,406
Quote:
Originally Posted by huhn View Post
and do we even start in perfect sync?
No, even with an absolutely perfect clock madVR does not time the start of playback to match v-sync so 60 v.s. 59.94 Hz makes no difference at all to smooth motion in any situation.
__________________
madVR options explained
Asmodian is offline   Reply With Quote
Old 28th July 2017, 03:54   #44449  |  Link
JarrettH
Registered User
 
Join Date: Aug 2004
Location: Canada
Posts: 860
Interesting discussion on the topic. Yeah, that is my prime question: does smooth motion nullify accurate clock timings. Less blended frames is a good thing. I'm sure madshi will answer too.
JarrettH is offline   Reply With Quote
Old 28th July 2017, 04:10   #44450  |  Link
huhn
Registered User
 
Join Date: Oct 2012
Posts: 7,903
the clock deviation doesn't matter with smoothmotion.

the higher the frame rate the lower the number of blended frames and the shorter the time they are shown.
huhn is offline   Reply With Quote
Old 28th July 2017, 06:23   #44451  |  Link
70MM
X Cinema Projectionist NZ
 
Join Date: Feb 2006
Location: Auckland NZ
Posts: 310
Still I find playing ripped BDs at 59.94Hz with smooth motion on doesnt look that great, there is too much blur going on with the blended frames.
I used it this way for a very long time, but finally went back to setting everything up to play in its native frame rate, 23.98 in > 23.98 out, no smooth motion.

However having a perfect clock run without a dropped or repeated frame is quiet hard to master....
Although I dont get many, I do get them....

Im waiting and hoping what madshi is working on in this area does come to fruition.
70MM is offline   Reply With Quote
Old 28th July 2017, 07:54   #44452  |  Link
AngelGraves13
Registered User
 
Join Date: Dec 2010
Posts: 254
I hope that sometime in the future that NGU Chroma will only scale once with image doubling, like SuperXBR instead of scaling once and then being doubled.
AngelGraves13 is offline   Reply With Quote
Old 28th July 2017, 09:02   #44453  |  Link
mrjones
Registered User
 
Join Date: Aug 2015
Posts: 2
Clock Deviation

I am playing live TV through kodi/Vader and am getting buffering .
MADVR is reporting the clock deviation is at 68% !!!
Is this the source or a function of something else?
mrjones is offline   Reply With Quote
Old 28th July 2017, 11:52   #44454  |  Link
QBhd
QB the Slayer
 
QBhd's Avatar
 
Join Date: Feb 2011
Location: Toronto
Posts: 697
Quote:
Originally Posted by mrjones View Post
I am playing live TV through kodi/Vader and am getting buffering .
MADVR is reporting the clock deviation is at 68% !!!
Is this the source or a function of something else?
That's normal... as soon as there is a glitch in the stream or buffering that "clock deviation" is meaningless. It is a calculated guess at the clock deviation, and the calculation goes through the roof if the stream gets interrupted.

QB
__________________
QBhd is offline   Reply With Quote
Old 28th July 2017, 12:09   #44455  |  Link
Asmodian
Registered User
 
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,406
Quote:
Originally Posted by JarrettH View Post
Interesting discussion on the topic. Yeah, that is my prime question: does smooth motion nullify accurate clock timings. Less blended frames is a good thing. I'm sure madshi will answer too.
I found a quote from madshi about it, I remember another one mentioning not syncing the start of the blending factors to v-sync but I couldn't find it.
Quote:
Originally Posted by madshi View Post
The reason madVR measures the VSync position for blending factors does not have anything to do with tearing. Actually I could add any random (but constant!) offset to the measured VSync position, and it wouldn't cause motion smoothness to be harmed. E.g. if I added a 0.5 frame offset to the measured VSync position, this would cause the blending factors to change accordingly, and the net result would be an audio/video sync mismatch of 0.5 frames, but motion smoothness would still be the same. The reason madVR measured the VSync position is that only this way the blending factors adjust perfectly to the output refresh rate, so that I never ever have to drop or repeat a video frame.

It's complicated, but I hope my explanation is understandable?
I did some experimenting in Excel:
24/1.001 fps @ 59.900 Hz = 80.04% blended
24/1.001 fps @ 60/1.001 Hz = 40.12% blended
24/1.001 fps @ 59.94006 Hz = 79.98% blended
24/1.001 fps @ 60.000 Hz = 79.72% blended
24/1.001 fps @ 75.000 Hz = 63.74% blended
24/1.001 fps @ 120.000 Hz = 39.76% blended

Random partial v-sync offsets in the start of playback do not change the percentage of blended frames noticeably, except for the theoretically perfect refresh rates. 24/1.001 fps @ 60/1.001 Hz changes to match the nearly perfect 59.94006 Hz with 79.98% blended frames when adding a 0.3 v-sync offset at the start of playback.
__________________
madVR options explained

Last edited by Asmodian; 28th July 2017 at 12:37.
Asmodian is offline   Reply With Quote
Old 28th July 2017, 17:02   #44456  |  Link
ashlar42
Registered User
 
Join Date: Jun 2007
Posts: 652
Quote:
Originally Posted by Asmodian View Post
I did some experimenting in Excel:
24/1.001 fps @ 59.900 Hz = 80.04% blended
24/1.001 fps @ 60/1.001 Hz = 40.12% blended
24/1.001 fps @ 59.94006 Hz = 79.98% blended
24/1.001 fps @ 60.000 Hz = 79.72% blended
24/1.001 fps @ 75.000 Hz = 63.74% blended
24/1.001 fps @ 120.000 Hz = 39.76% blended

Random partial v-sync offsets in the start of playback do not change the percentage of blended frames noticeably, except for the theoretically perfect refresh rates. 24/1.001 fps @ 60/1.001 Hz changes to match the nearly perfect 59.94006 Hz with 79.98% blended frames when adding a 0.3 v-sync offset at the start of playback.
I really lost you here.

From the experiments in Excel I would conclude that it's better to playback 23.976 material at 60/1.001 but how can only 40% frames being blended? Are some frames simply repeated?
ashlar42 is offline   Reply With Quote
Old 28th July 2017, 18:17   #44457  |  Link
iSeries
Registered User
 
Join Date: Jan 2009
Posts: 625
Quote:
Originally Posted by Asmodian View Post
24/1.001 fps @ 60/1.001 Hz = 40.12% blended
24/1.001 fps @ 59.94006 Hz = 79.98% blended
I don't really understand this (maybe I'm being dim), isn't 60/1.001hz = 59.94006hz?

I had my TV at 60hz, and I typed in Madvr allowable refresh rates of 60p and 59p, and used a 24/1.001 source with smooth motion. MadVR switched to 59p (59.94hz) to play it. So I assumed MadVR thinks 59.94 is better than 60 when using smooth motion.
iSeries is offline   Reply With Quote
Old 28th July 2017, 18:29   #44458  |  Link
nevcairiel
Registered Developer
 
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,342
Quote:
Originally Posted by ashlar42 View Post
I really lost you here.

From the experiments in Excel I would conclude that it's better to playback 23.976 material at 60/1.001 but how can only 40% frames being blended? Are some frames simply repeated?
Don't think you can really get 40% only, not at 60 fps. Only every 5th frame has matching source/VSYNC timings, no matter how perfect the clock.

If you assume perfect timing, and 24 fps and 60Hz for simplicity (in milliseconds)
Code:
Frames: 0          41.66          83.33           125.00            166.66
VSYNC:  0 16.66 33.33 50.00 66.66 83.33 100.00 116.66 133.33 150.00 166.66 183.33 200
As you can see, a few frames fit perfectly on the timing, but only one in five on the output, so 4 in between will be blended (eg. 80%) - and thats already the best case.


Quote:
Originally Posted by iSeries View Post
I don't really understand this (maybe I'm being dim), isn't 60/1.001hz = 59.94006hz?

I had my TV at 60hz, and I typed in Madvr allowable refresh rates of 60p and 59p, and used a 24/1.001 source with smooth motion. MadVR switched to 59p (59.94hz) to play it. So I assumed MadVR thinks 59.94 is better than 60 when using smooth motion.
The key is that 60/1.001 is perfect precision, and 59.940 is not. As soon as it diverges just a tiny tiny bit (which you will), you might as well use 60Hz, since it no longer matters.
Unless SmoothMotion accounts for that of course and allows tiny deviation without blending. In general, just don't think too much about it. Using a native 24p mode is IMO always superior, but if your screen doesn't have that, SM is probably the best you can do.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders

Last edited by nevcairiel; 28th July 2017 at 18:43.
nevcairiel is offline   Reply With Quote
Old 28th July 2017, 18:55   #44459  |  Link
huhn
Registered User
 
Join Date: Oct 2012
Posts: 7,903
@Asmodian

not sure how you used excel to come up with these numbers but madVR blends as little frames as possible. because no clock is perfect every vsync where two frames overlap is blended with other words it blends a frame every time a new frame needs to be displayed.

that means with 42 ms and 16 ms refresh rate 1 out of 3 v-syncs is never ever be blended and up to 2 out of 4 v syncs is not a blended frame so more than 66% blended frames is not possible and less than 50 % too.

with perfects clocks it would be 20% BTW.
huhn is offline   Reply With Quote
Old 29th July 2017, 01:18   #44460  |  Link
Asmodian
Registered User
 
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,406
Quote:
Originally Posted by iSeries View Post
I don't really understand this (maybe I'm being dim), isn't 60/1.001hz = 59.94006hz?

I had my TV at 60hz, and I typed in Madvr allowable refresh rates of 60p and 59p, and used a 24/1.001 source with smooth motion. MadVR switched to 59p (59.94hz) to play it. So I assumed MadVR thinks 59.94 is better than 60 when using smooth motion.
That was an example to show that while theoretically it is possible to get below the normal number of blended frames by tuning the refresh rate perfectly it isn't actually possible (59.94006 is an error of only 0.0000001%).

Quote:
Originally Posted by huhn View Post
@Asmodian

not sure how you used excel to come up with these numbers but madVR blends as little frames as possible. because no clock is perfect every vsync where two frames overlap is blended with other words it blends a frame every time a new frame needs to be displayed.

that means with 42 ms and 16 ms refresh rate 1 out of 3 v-syncs is never ever be blended and up to 2 out of 4 v syncs is not a blended frame so more than 66% blended frames is not possible and less than 50 % too.

with perfects clocks it would be 20% BTW.
I see, I had some trouble trying to figure out an equation that gave reasonable results, I thought I got it but it still isn't accounting for the timing of the frame blends correctly so it was double counting blends.

I will see if I can figure it out... simple math is too easy! Must get simulator working!

Edit2: Hmm, frame 3 is displayed for 3.5 v-syncs? The blend ratios are still off.

Edit3: OK, I think I figured out something. All my logic is timed based now so I hope it matches what madVR calculates. I do get <50% blending but I believe this is correct? All frames total up to exactly the display time ratio we expect. I also calculated a new stat, "Average Blend" which is the average blending ratio across 20 thousand frames. I think this is actually a better representation of how much blending is going on, compared to percent blended frames.

24/1.001 fps video with smooth motion displayed at:

24.00000 Hz = 99.80% blended, 50% average blend
30.00000 Hz = 79.82% blended, 40% average blend
48.00000 Hz = 49.85% blended, 25% average blend
59.94006 Hz = 40.03% blended, 20% average blend
60.00000 Hz = 39.86% blended, 20% average blend
75.00000 Hz = 31.87% blended, 16% average blend
120.0000 Hz = 19.88% blended, 10% average blend
144.0000 Hz = 16.62% blended, 8% average blend

An interesting note about the average blend is that a V-sync offset doesn't change it at all unless you are using a nearly perfect refresh rate, and even then that is only because I am limited to 20,000 frames, as you can see the blending ratios drift up and down as the frame rate and V-sync drift in and out of sync.

I hope someone else finds it useful, it took me a while to figure out the spreadsheet.
__________________
madVR options explained

Last edited by Asmodian; 29th July 2017 at 05:54.
Asmodian is offline   Reply With Quote
Reply

Tags
direct compute, dithering, error diffusion, madvr, ngu, nnedi3, quality, renderer, scaling, uhd upscaling, upsampling

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 13:24.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.