Nvidia 23,796 custom refresh rate

[krille]

Just wanted to share something that has worked on both my old 650 card, and also my new 960. I discovered that even though i came pretty close to 23,976 i still had dropped/repeated frames. I also noticed that when I was playing a 24p movie I could play a whole movie without dropped frames even though the stats in madvr did not report exactly 24,00000. On my 650 card it was a little bit more than 24,00000, lets say 24.00123 and on the 960 card a little bit less, lets say 23,99932.

So what I did on the 650 was to take:

23,97602+0,00123=23,79725

and om my new 960:

24,00000-23,99932=0,00068. 23,79602-0,00068=23,79534.

So to sum it up: I did not aim at 23,976 when setting the custom refresh rate. On the 650 I was aiming for 23,79725 (see above) and on my 960 i aimed for 23,79534( also see above).

This actually works for me! I can now play a whole movie without reclock @23,796 without any framedrops/repeats. Try it for yourself!

Hope you understand what I am writing here as my english is not the best...

[huhn]

the clock it self is pointless the clock deviation is the problem.

23.965 could result in perfect sync it just depends on the audio clock.

[krille]

Works for me though.

[huhn]

just play a video for 2 mins and look at the madVR OSD. if you see a repeated frame every 3 h + than yes you hit the mark for your system.

[Ceremony]

not every monitor might handle the signal well though, as this is not a standard clock at all

[huhn]

there should be no problem as long as the device supports 23p.

a clock with 23.950-23.990 happens all the time with stock hardware.

[Zachs]

Or just use MPDN's rate tuner (http://zachsaw.blogspot.com.au/2015/07/23976-judder.html) :p

I spent countless hours that I'll never get back trying to get my display refresh rate exactly what I wanted but I could never get close enough. It's always been a pet peeve of mine!

[krille]

just play a video for 2 mins and look at the madVR OSD. if you see a repeated frame every 3 h + than yes you hit the mark for your system.

Yes, of course you could do that, but it might save time to know what refresh rate you are aiming at. As I said i aimed at 23,79534. I got pretty close and the stats are pretty fine.

http://i62.tinypic.com/ndmyqo.jpg

[huhn]

Yes, of course you could do that, but it might save time to know what refresh rate you are aiming at. As I said i aimed at 23,79534. I got pretty close and the stats are pretty fine.

http://i62.tinypic.com/ndmyqo.jpg

but it is pretty worthless to aim at the same speed for most other user even with the same GPU.

[krille]

but it is pretty worthless to aim at the same speed for most other user even with the same GPU.

Yes, it would, but it might work if they did what I said in my first post.

[pirlouy]

Nobody would follow the advice of someone who confused 23.976 with 23,796 that much. ;)

[6ari8]

Since MadVR got a 64bit build and having known Reclock developers having no plans to do the same, I've been tinkering with Nvidia Custom Resolutions to get a perfect 23.976 playback. After a LOT of tinkering, I got to a near-perfect 23.976 playback so I'll share my settings here in case someone might benefit from them.

System: Alienware M14x R2, Intel i7-3720QM, 16GB RAM, NVIDIA GeForce GT 650M 2GB + Intel HD Graphics 4000, Windows 10TP 10166.

Custom resolution timings:
http://s2.postimg.org/dlpvu8z3p/bim329.jpg (http://postimg.org/image/dlpvu8z3p/)

This is what this CR got me using MPC-HC+LAV filters+MadVR and using the Directshow audio renderer from MPC-HC. As you can see it's very good.
http://s2.postimg.org/w2kal2f1x/11imn9k.png (http://postimg.org/image/w2kal2f1x/)

I was interested in trying out MPC-BE's WASAPI audio renderer since MPC-HC's was broken. So, I tried MPC-BE and was surprised that even though the resolution was the same, the clock deviation became much smaller and pretty much eliminated my frame drops.

I got the stand alone MPC-BE filters and registered the renderer with regsvr32 so I can try it with MPC-HC and it was perfect.
http://s2.postimg.org/jp7ge5pdh/2n218wk.png (http://postimg.org/image/jp7ge5pdh/)

http://s2.postimg.org/ksrkq4a0l/16lba54.png (http://postimg.org/image/ksrkq4a0l/)




I'm not sure why changing the audio renderer did that but I'm happy with the result.

[THU22]

This is an old thread, but I think it is better to post here than to create a new one.

I tried creating a custom resolution to get exact 23.976 Hz and I managed to achieve it (madVR confirms it). The problem is that any custom resolution is limited to RGB 8-bit, which means I cannot use HDR, not even with dithering, I just cannot turn it on at all.

Is there any way around that?

I have been using ReClock for many years, but it would be nice to able to bitstream Atmos/DTS:X when I upgrade my audio system.

[Stereodude]

Use Custom Resolution Utility instead.

[shaolin95]

This is an old thread, but I think it is better to post here than to create a new one.

I tried creating a custom resolution to get exact 23.976 Hz and I managed to achieve it (madVR confirms it). The problem is that any custom resolution is limited to RGB 8-bit, which means I cannot use HDR, not even with dithering, I just cannot turn it on at all.

Is there any way around that?

I have been using ReClock for many years, but it would be nice to able to bitstream Atmos/DTS:X when I upgrade my audio system.

It seems to be an issue with Nvidia drivers like forever!
But like Stereodude said, Custom Resolution Utility works perfectly one and lets you select 12bits (in my case). I used it for my JVC projector and it adds the resolution under PC resolutions in the Nvidia Control Panel (i had to reboot to get it to show).
Now currently testing a movie and it is showing just over 5 hours before repeated frames. :)