How important is a resolution that is a multiple of 16?

[ViciousXUSMC]

I know for optimal results you want to use a resolution for your file that can evenly be divided by 16. So I guess you can resize or crop. However some resolutions I like to leave untouched like native 1920x1080.

Should I be worried about it or just leave it be?

[Dark Shikari]

Should I be worried about itno.or just leave it be?yes.

[ViciousXUSMC]

I figured as much. Was playing with StaxRip and it will not let you start the encoding process untill you have a resolution that is croped or resized to be divisible by 16.

I think I found a way around it though, the GUI still shows 1920x1072 on my resolution slider but I double clicked the crop filter and edited the .avs script so that the crop filter should just crop 0.

I'll see when this encode is done, 2 hours for a 10 minute file :/

I like how StaxRip uses Avisynth and even saves the script files for you, its making it easier for me to go back and look at those logs and files to see how it all works. Bringing me one step closer to a full manual control over the process as to not rely on the features and limitations of a GUI.

Id feel very comfortable running x264 from a .bat file manually with no help at this point. So now I just need to learn more Avisynth and then the demuxing/muxing stuff.

[dat720]

unless you need to do the sort of processing where avisynth excels, it's often easier just to feed the video directly to x264, ffmpeg, mencoder... they all do an excelent job and don't require avisynth to frame serve which means they are faster!

[ViciousXUSMC]

unless you need to do the sort of processing where avisynth excels, it's often easier just to feed the video directly to x264, ffmpeg, mencoder... they all do an excelent job and don't require avisynth to frame serve which means they are faster!

I think I noticed this, 2 hours is longer that what that clip would have normally taken and my 4 cores on my q6600 were not pegged at 100% the entire time like normal, instead it fluxed between 60 to 100 randomly meaning something was slowing it down.

That means its easier on my cpu though since it is overclocked to 3.6ghz.

However what I was working with was FRAPS files, they are broken down into chuncks of like 4gb each so I need to splice them together first, and so far the only programs I know are Avidemux, HandBrake, and now StaxRip. Avidemux is not working properly at the moment after I render, Handbrake will not take FRAPS files nativly requiring me to render them in another codec first. So the frameserve method for StaxRip is actually working well for me.

I do plan to use x264 directly, but I am not yet advanced enough to be able to demux, encode, and then mux my file back together again without one of these do it all for you gui's.

I do know x264 well enough to run it solo via a .bat file but I am clueless currently for muxing/demuxing and it may not do me much good to find gui's for that purpose at this point.

So x264 can take a fraps file directly though? I was under the impression it had to be converted first or frame served.

Edit: Looked at mencoder its command line based just like x264 so I see no reason you would use it instead of directly going with x264 its like adding a program to run a program. There must be some extra options you gain that I need to be aware of.

I looked at the gui automen for mencoder and it was too simple for my needs, no choice for audio codec and you can only select from some presets and not edit them. So FFmpeg is the only one on the list I have not tried and that sounds like it would be more of a DVD tool.