DVDREasy method to find the optimal Q value for CCE is:
1) put all the right settings as normal multipass VBR and only change VBR(x passes) to OPV
2) estimate the first Q value – formula based on movie time ( if Q is bigger than 45 then Q=45)
3)encode 1% of the movie with avisynth command “SelectRangeEvery(1200,12)” and using the first Q
4)Based on file size of the 1% sample estimate the full movie size
5)Calculate the difference between estimated full movie size and wanted movie size
6)Calculate the new Q value until :
----a. The next Q is equal to the last Q
----b. Or % difference is < 1%
Although this is acceptable, I'm having feedback of users that the final size (after authoring) is a little undersized. The worse case is 4.06GB for the final size.
Incredible post the code to slicer :
Code:
function slicer(clip input, int percent, int Goplenght, int Gopmulti, string "ping")
{
PercCount = (Framecount(input)/100)*percent
period = int(Framecount(input)/PercCount)*(Goplenght*Gopmulti)
input=(ping == "pong") ? input.trim((period/2),Framecount(input)):input
selectrangeevery(input, period, (Goplenght*Gopmulti))
}
I was wondering if using this method instead of a simple "selectrangeevery" could do a more accurate value (although the Q value in CCE is a integer)
@incredible,
Could you tell me what you think of it and explain why ?
Thanks!
Cheers,
DVDREasy
and how much GOPs will one slice take (the Gop multiplier integer of slicer()).
.
