View Full Version : dropping frames and wrong frame rate on NASA Thermonuclear Art
mi3gai4rui4
13th July 2019, 21:13
Hi, I'm stumped on this and looking for help.
I downloaded the 21.9GB version of the "Thermonuclear Art" movie from here (https://svs.gsfc.nasa.gov/13057).
Both that web site and MediaInfo say the video is 59.94 FPS.
When I open it with MPC-HC (configured with LAV filters and MadVR) it does not play back smoothly. MadVR's on-screen display shows many dropped frames. It also shows the video frame rate is 25FPS, which is wrong.
When I open it with Windows' built in "Movies and TV" app it plays fine, so I guess there's some software issue somewhere in MPC-HC, LAV, or MadVr.
Things I've tried:
* Updated LAV video filter to latest
* Switched upscaling methods in madVR
* Switched from DXVA2 to D3D11 decoder in LAV Video. When I do this it doesn't play back at all (as in the "play" button in MPC-HC seems to have no effect, the video stays paused).
* Remuxed from .mov to .mkv
LAV Video settings:
Lav Video Decoder 0.74.1
DXVA2 (native)
Active Decoder: avcodec
Codecs for HW Decoding: everything except "H.264 MVC" is checked.
MadVR on-screen display:
Display 25.00005 Hz (8 bit, RGB, full)
Composition rate 25.000 Hz
clock deviation 0.000041%
Smooth motion off
D3D11 fullscreen windowed (10 bit)
h264, 8 bit, 4:2:0 -> NV12, 8 bit, 4:2:0
movie 25.0 fps (says source filter)
movie 3840x2160, 16:9
draw 0,0,3840,2160
touch window from inside
chroma > NGU Sharp (low)
...
average stats
rendering 10.69 ms
present 0.10ms
max stats
rendering 17.87ms
present 0.24ms
NVidia GeForce GTX 1080Ti.
Driver version: 430.53
MPC-HC 1.7.13
Thanks for any help
Asmodian
13th July 2019, 22:36
They seem to have messed up the tagging on the stream.
When muxing to mkv with MKVToolNix GUI select the video stream and change the "Default duration/FPS" to 60000/1001p. I also checked "Fix bitstream timing info" but I am not sure that was required (probably not). I did get a file that played correctly after this remux while I also got a lot of dropped frames with the original file.
Edit: Actually I do need to check "Fix bitstream timing info" to change the frame rate detected by LAV/madVR.
Edit2: The 234 GB ProRes version is properly 60/1.001 FPS and 10 bit 4:2:2.
v0lt
15th July 2019, 05:18
MadVR on-screen display:
Display 25.00005 Hz (8 bit, RGB, full)
FPS is limited to display. Change the mode to 59/60 Hz.
Stereodude
15th July 2019, 12:22
Edit2: The 234 GB ProRes version is properly 60/1.001 FPS and 10 bit 4:2:2.
Did you actually download the whole thing? :scared:
mi3gai4rui4
15th July 2019, 16:04
FPS is limited to display. Change the mode to 59/60 Hz.
I have auto display mode switching, so my display switched to 25 Hz because madVR thinks the video is 25 Hz.
When muxing to mkv with MKVToolNix GUI select the video stream and change the "Default duration/FPS" to 60000/1001p. I also checked "Fix bitstream timing info"
Thanks Asmodian, I will try that when I get home!
mi3gai4rui4
16th July 2019, 03:32
Just confirming remuxing with those settings fixed the issue. Thanks again!
Asmodian
16th July 2019, 10:40
Just confirming remuxing with those settings fixed the issue. Thanks again!
Glad it worked for you too. Thanks for bringing it to my attention, it is a very cool video. :)
Did you actually download the whole thing? :scared:
I did, the 21.8 GB version intrigued me so I had to see what it looked like in its full glory. Now I wish they had a link to the 8K original they mentioned. :p
This is the hardest material I have ever tried to encode... a good test case.
Klaus1189
16th July 2019, 10:49
Did you actually download the whole thing? :scared:
Me too
Stereodude
16th July 2019, 12:24
I did, the 21.8 GB version intrigued me so I had to see what it looked like in its full glory. Now I wish they had a link to the 8K original they mentioned. :p
This is the hardest material I have ever tried to encode... a good test case.
Oh, I downloaded it too. :sly:
Hardest as in it doesn't encode well? Encodes slowly? Hard to get acceptable results from? Are you using x265?
I haven't attempted to pull it into avisynth+ yet. I have a few other encodes I'm trying to finish off first. I'm not even sure what plugin to use to load it.
Stereodude
20th July 2019, 17:07
So I got around to loading this up this morning in avisynth+. Frankly, I'm not sure why it's UHD. From my quick review I didn't find any useful single pixel level detail in it. Very little of it is actually p60 either. Most is frames doubled p30. The fades are p60 and I found one or two short segments that were p60. Then there are sequences of 2 sharp frames followed by a bunch of blurry frames, then another 2 sharp frames, then more blurry frames staring at 1:55-2:07.
Klaus1189
20th July 2019, 19:00
Which file did you test with?
Asmodian
20th July 2019, 20:23
I also noticed it is usually 30p but the detail seems pretty good. I notice a lot of small detail in the images of the full sun, it is only the zoomed in parts that don't have a lot of detail. What about around 26 minutes in?
Then there are sequences of 2 sharp frames followed by a bunch of blurry frames, then another 2 sharp frames, then more blurry frames staring at 1:55-2:07.
This is in the image sequence where the spacecraft is being overwhelmed by the intensity from that flair/sunspot. Remember this is real data from a spacecraft, not just pretty pictures.
Hardest as in it doesn't encode well? Encodes slowly? Hard to get acceptable results from? Are you using x265?
It encodes slowly and requires a lot of bitrate to look OK. I used both x265 and x264.
Stereodude
20th July 2019, 22:57
Which file did you test with?
The giant ProRes 4:2:2 one.
I also noticed it is usually 30p but the detail seems pretty good. I notice a lot of small detail is the images of the full sun, it is only the zoomed in parts that don't have a lot of detail. What about around 26 minutes in?
Maybe. I still think it could be competently scaled to 1080p and lose virtually nothing with madVR playback compared to the original. I'd really like to throw some light temporal denoising at it, but MCTD doesn't work in >8 bits.
shae
22nd July 2019, 01:01
MPC-HC 1.7.13
Even without remuxing, version 1.8.7 of MPC-HC might help.
clsid keeps it alive by fixing problems, adding minor features, and keeping components up to date.
https://github.com/clsid2/mpc-hc/releases
https://forum.doom9.org/showthread.php?t=175209
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.