I'm trying to reduce some captures that come in at 60fps. I did one to 23.976 using tmpgenc video mastering works and the result is choppy/jerky video. I'm not even sure what setting I would tweak or what other options I'd have.
Any suggestions that I can at least translate to vmw if not in it directly?
+ Reply to Thread
Results 1 to 14 of 14
-
-
If the captures are capturing motion & unique frames at each time instance, you can never achieve NO loss of smoothness, unless the amount or type of motion is lower than a reduced capture rate (and changes occur in sync with that rate).
IOW, if you move slowly enough a lower framerate would still be able to handle it.
However, "stuttery" refers not just to low speed but to UNEVEN framerates. Framerate reduction that is whole numbered is much smoother than framrate reduction that has a cadence. Stairsteps that are uneven are much more noticeable than just bigger stairsteps.
What you seemed to do in your example was a form of IVTC, which sets up a cadence (usually 3:2:3:2). TC usually goes from 24->30, and IVTC usually removes that cadence and restores the original 24fps, but since your original was 60fps, there was no original to restore and so you are Generating a cadence through decimation.
Try doing whole multiple rate reduction: 60->30 (2:1), with or without frame blending. It takes out every other frame, but the result is still "natural" motion.
Scott -
Check correct framerate of your source video. If is it 60fps or 59.94
Best practice is get framerate divided by 2. Which of course 23,976 isn't. So try to do it to 30fps if 60fps or 29,97fps if 59,94.
You should get better result.
Scott was faster
Bernix -
You can add some motion blur and you can go to interlaced... eventually you may try to perform framerate conversion with motion interpolation/compensation
-
Why do you lower frame rate?
I'm asking because you reduce it to 23.976 now trying 30fps, so it seams that you do not have a project or mixing editing problem. -
-
-
Reducing frame rate 50% would not reduce video size 50%. It does not work like that, if you planned on this sort of rule. Frames are suddenly "further apart" so changes are bigger, so more bits have to allocated as oppose using double frame rate.
If it is captured video, like games , are you using CRF method for encoding? That might surprise you how effective it could be for that kind of video, meaning you might end up with much lower average as oppose guessing it using 2pass VBR or just 1pass bitrate encoding.
If video is not much dynamic at all, you might benefit reducing frame rate, but do not blend, interpolate frames or anything, just skip every other frame with whatever software or videoeditor you use.
So basically it helps if you say what are you actually doing, what are you capturing etc. Otherwise it is a bunch of folks telling you something and shooting in the dark general rules at you. -
I never said or thought cutting frames in half would cut the size in half. But reducing the frames per second will help. The source is at 60 but I would rather capture at that rate and then use processing to handle the rest.
It is a capture from TV and I'm using constant quality. -
If it's a capture from (US) TV, then very likely it should either have been 1280x720@60p (or 59.94p), where you should keep the high framerate because those shows usually have higher motion, or it should have been 1920x1080@60i (59.94i), where it is already interlaced and dropping the framerate should be done only when absolutely necessary and only using smart deint tools. ATSC currently doesn't support 1080p60.
If you captured some other way, you MAY have duplicate frames or inherent judder, depending.
Scott -
Then depends on your TV set and go for 1080p60 or 720p60, apply some antialiasing processing, IMHO some blur may help, use crf mode and level compliant with your TV decoder capabilities (i.e. at least 4.0 for 30p and at least 4.2 for 1080p60), favour also slower processing than fast.
https://software.intel.com/en-us/articles/common-bitrate-control-methods-in-intel-media-sdk
https://software.intel.com/en-us/articles/advanced-bitrate-control-methods-in-intel-media-sdk
Reducing bitrate by frame rate conversion is most significant quality degradation. -
Part of the problem for me is I don't know where or how to do some of the things mentioned in this thread, especially with video mastering works, which is what I'm using.
However, it sounds like the recommendation, at least in my case, is to just go to 30fps and, in general, the best bet is to keep to simple math if converting frame rates.
As an FYI, transcoding a sample video made a difference of about 12% in going to 23.976 vs 30fps for me, where the 30fps was larger.
Similar Threads
-
60fps jerky/choppy output via Sony Vegas 13
By s34n04 in forum Video ConversionReplies: 7Last Post: 21st Sep 2017, 21:01 -
24p to 60fps using frame interpolation on OSX
By bmick23 in forum Video ConversionReplies: 1Last Post: 17th Mar 2016, 16:06 -
60fps playback perfect, 30fps choppy stutter (YouTube)
By mr2ggaming in forum EditingReplies: 17Last Post: 28th Nov 2014, 21:03 -
Highest video frame rates (consumer grade)
By dbooksta in forum Camcorders (DV/HDV/AVCHD/HD)Replies: 6Last Post: 19th Feb 2014, 00:09 -
Converting video frame rates
By KyleMadrid in forum Newbie / General discussionsReplies: 46Last Post: 7th Mar 2013, 23:09