Printable Version of Topic
Click here to view this topic in its original format
Unofficial VirtualDub Support Forums > Newbie Questions > How Do I Render Avi With A Really Small File Size?


Posted by: aDogNameDude Mar 15 2014, 02:34 AM
I am rendering some AVIs that were missing a codec. the videos are only 10mins long. but this program is making the final file size 13GB!!!! I need them to each be under 1 GB. Please Help Me.

Thanks

Posted by: raffriff42 Mar 15 2014, 04:01 AM
  • Get http://sourceforge.net/projects/x264vfw/
  • CRF mode suggested
  • Suggested Ratefactor
    • 27 (YouTube-like quality, very small file size)
    • 23 (good quality, small file size)
    • 18 (very high quality, almost lossless; best if uploading to YouTube)
  • Be sure to check "Virtualdub hack"
  • Preset = "veryfast" for speed, or default "medium" or "slow" for ~20% smaller file

user posted image

Posted by: -vdub- Mar 15 2014, 06:46 PM
.

Posted by: raffriff42 Mar 16 2014, 01:24 AM
QUOTE (-vdub- @ Mar 15 2014, 06:46 PM)
YUV 4:2:0 No convert colorspace again when the video source is YUV 4:2:0
Keep Accept\Only YUV 4:2:0
Agreed, I try to do that when possible.

@aDogNameDude, for this to work you need to be in Fast Recompress mode; or if in Full Processing, set Video / Color Depth / Output to "4:2:0 Planar YCbCr (YV12)," and don't use any filter that forces conversion to RGB.

(BTW are we understanding your original question correctly?)

Posted by: Abrazo Mar 16 2014, 08:18 AM
Maybe just missing the knowledge that you need to set the Video- and the Audio-menu of VirtualDub to "Full processing mode" and that you need to set - also in these both menu's - Compression... to a certain 'codec' to compress the data. Something like "x264vfw" for video and "Lame MP3" for audio.

Posted by: dloneranger Mar 16 2014, 11:30 AM
Can a add a few eeks here?

Zero latency
That's turning off bframes, mbtrees
Makes larger files than normal

Profile Auto and Level Auto
Not setting a limit on those can make x264vfw use profiles and levels that are too high or unneeded
It can sometimes pick specs like 10bit colour and vuy444, or levels too high for the playback device
Makes larger files than needed, files may not play on limited memory devices

Preset veryfast
Disables some size/quality optimizations just for speed of encoding

Fast decode
Turns off cabac, deblocking and p/bframe optimizations
Makes larger, lower quality files than normal

Extra command line options
--colorprim, transfer, colormatrix
Unless your source is 709 already then setting those to 709 here will change the colours on playback
Without knowing the OP's source material this may be wrong or right

All of those (except 709 colourspace) are why the ratefactor has to be increased so much
You've disabled all the bits that make good quality small files
in favour of larger files, less quality for the bitrate but a faster encode time

A basic setting that works almost anywhere and gives decent quality/size looks more like this
http://imageshack.us/photo/my-images/547/ab3n.png/
The ratefactor can be made smaller if higher quality is needed
If the source is 709 add the options --colorprim bt709 --transfer bt709 --colormatrix bt709

Posted by: raffriff42 Mar 16 2014, 12:07 PM
The settings in my screenshot are for uploading to YouTube, which likes simple, easy-to-decode sources -- high bitrate and low complexity. I like to encode quickly, but more importantly, "veryfast" does things (--no-mixed-refs, --rc-lookahead 10, --ref 1, --subme 2, --trellis 0, --weightp 1) that seem to work well with YouTube. Yes, the file size is significantly larger. I don't know the intended purpose of the OP's compression task, which is why I mentioned several options.

Posted by: -vdub- Mar 16 2014, 03:50 PM
Thanks dloneranger your latest x264vfw guide picture and advice is much more than your original x264vfw guide picture

Ratefactor of 20 to 18 would better 25 for video quality and size !

Posted by: dloneranger Mar 16 2014, 04:01 PM
It's a compromise I guess, tbh 25's more than adequate for me - when the video's actually playing I can't honestly see much of a difference
It's an adjustment that doesn't turn off any features of x264, so you can move it around to your liking without any problems

The best way is to experiment, encode the same video with 20,21,22,23....etc
Then play them back to find your happy spot for quality/size

Some other stuff..........

I should mention the difference between keep/accept and convert for the format option
If keep/accept only yuv420 is selected virtualdub will convert whatever it has to yuv420 before giving it to x264
If convert to yuv420 is selected virtualdub will give whatever it has to x264 and x264 will convert it to yuv420 itself
Unless virtualdub of x264 is has buggy conversion routines then it's six of one half a dozen of the other

Colourspaces 601 and 709
The video stream can be either unmarked, marked as 601 or marked as 709 (and other variations, but we'll just go with the main two)
If you don't enter anything in the extra command line options the stream is unmarked
If you want to mark it for 601 use
CODE
--colorprim smpte170m --transfer smpte170m --colormatrix smpte170m

If you want to mark it for 709 use
CODE
--colorprim bt709--transfer bt709--colormatrix bt709

x264 doesn't have a bt601 as I think it assumes no marking=601
Players can decide that an unmarked video is 709 though, so it's best to mark either way (smpte170m=601)
(I'm not sure they should choose 709 by themselves, but there you go)

Powered by Invision Board (http://www.invisionboard.com)
© Invision Power Services (http://www.invisionpower.com)