result from post #26
+ Reply to Thread
Results 31 to 43 of 43
Max number for those frames is here (stored frames):
It all comes in a bunch with max bitrate, resolution,fps and that is bunched up as a regulation and it is called a level. So if you choose a level Main 4.0 in Voucoder you should have max 30fps for HD and 20000kbps for bitrate. But Voucoder uses x264, so you just select a profile. And particular profile would select all of it for you. It is a safe way with profile medium to keep all within regulations. For example profile Medium is a decent choice, compromise, and that would select all for you, number of reference frames etc., I would not worry about that, medium profile and forget it. For Youtube perhaps you can crank it up to profile Slow. You do not get a miracle changes if you change number of reference frames, only make it harder for decoding. And increasing storage space for those frames. If encoding HD, each stored frame suddenly is lots of space. In no way I'd let it be more than 4. There is some crazy things on web, where mostly for a cartoons you might see a video with 16 reference frames, but for a regular video I'd never do that.
If there is a choise for reference frames in Vegas again, just to be sane, for HD content never more than 4, for UHD it gets even more demanding, not sure if 4 would you get into trouble, if it is too much, you'd need also level at least 5.1 or 5.2(HD, UHD 60fps). But you try to play a level 5.1 on some older TV and it gets rejected, where only levels 4 are tolerated. So you can see now how it is all connected.
If it is for Youtube only, whatever it takes, whatever is tolerated, I'd guess Youtube might take even those extreme settings. But to increase ref frames is a wrong end to do it. Using higher bitrates or frames per second (60, record -> publish) or upload UHD instead of HD is the way to go.
Also x264 for HD content with about 20000kbits would not give you such a difference between frames, that is why people use encoders outside of Vegas , frame server or now perhaps even Voucoder if it is working and using x264 or other encoders. In Vegas you have to be generous with bitrate. Your video clip needs lots of bitrate because of constant pan, movement, encoder (cheap versions of reals ones that are for a sale) might struggle to come up with a reference or do not check quantizers deep enough to be on par and persistent, it might be set for a speed, and x264 might be much better.
Last edited by _Al_; 13th Feb 2021 at 20:19.
The default setting for voukoder libx264 is crf23 . Higher crf values lead to lower bitrate, lower quality, lower filesize. crf 23 is a bit too high IMO , I would use something lower . For general use I'd use 16-20 . If you want less loss you can go a bit lower. At crf 0 , it's lossless, but filesizes will be very large
But you can see when using libx264 the patterns and tree details are much more stable, there is less flicker, they don't change shape and details blurry/sharp/blurry/sharp
You can batch mp4fpsmod , and it can inplace edit if you want (e.g. process a folder of files without re-writing a copy of them)
I just manually processed my new drone 2.7k 60fps VFR to 60000/1001 FFR with mp4fpsmod because there is some stutter in the original 60fpsVFR footage.
Hopefuly the frame rate adjust will improve it like it did with the 4k@30fps VFR from the drone.
I have been recording in 60fps VFR lately because the drone video looks smoother with recording fast movement over ground and panning.
I see that voukoder uses the vegas project settings, so for 1080p 29.97fps render output i just set that in vegas pro project settings.
I'm dropping the fps to 29.97 for more reliably viewing on friends HD TV.
With voukodec settings i chose H264 as my cpu has intelQSV and a geforce mx110 video card.
Hopefully the codec will use my cpu threads and graphics card for faster render. I will check it with task manager when rendering
With voukoder set to H264, the option shown are preset "medium" and CRF 17.
Should i bother with the advanced settings including rate control and frames options.
I'll give these setting a go.
This will copy the rotation (and presumably other) metadata from the source mp4 file to the CFR mp4 file:
ffmpeg -r 30000.0/1001.0 -i input.mp4 -c:v copy -an CFR.avi ffmpeg -i CFR.AVI -i input.mp4 -map 0:v -map_metadata:s:v 1:s:v -c:v copy -an -fflags +genpts CFR.mp4 del CFR.AVI
I ended up rendering a 2min clips with 3 different codecs.
MAGIX AVC with QSV took 7min and had that blurred to sharp frame.
MAGIX no QSV just cpu it took 2:20 min, still had sight burred to sharp frames.
Voukoder CRF 17 took 26min quality was better. ( no QSV, I think it's been disabled in the latest version of Voukoder)
Sony AVC no QSV took 2:20 min with good sharp frames.
My laptop only has a Intel i5 cpu and the Geforce MX 110 graphics card doesn't do GPU encoding.
So for speed and quality compromise i will be using the Sony codec.
If i cranked up the MAGIX codec to MAX quality and Bit rate the render was better but not as good as the Sony codec set to max bit rate.
Looks like CPU only does better rendering than QSV.
After searching the Vegas pro forum.
Other people are disappointed with the performance of the MAGIX codec.
They also find the old tried and proven Sony codec is better.