digitalFAQ.com Forums [Archives]

digitalFAQ.com Forums [Archives] (http://www.digitalfaq.com/archives/)
-   Avisynth Scripting (http://www.digitalfaq.com/archives/avisynth/)
-   -   Solution to File Prediction on 1 CD when Auto gets it wrong. (http://www.digitalfaq.com/archives/avisynth/5391-solution-file-prediction.html)

Markymoo 09-05-2003 11:27 AM

Solution to File Prediction on 1 CD when Auto gets it wrong.
 
Hello

Ok well i've read alot a forums, guides, auto, manual size prediction but at the end of the day i want speed and accurate results. Time is Precious. I don't want to do lots of re-encodes, passes.

I tried CQMatic and TOC and they both give me 2-3% bigger predicted file size even with Jorel's new(Toks "Length of Sample" 72 75 90) every time. Is this the size everybody else is getting(oversized files)??? I'm using AVI's but this will work for DVD. I know everbodys trying for exact filesize methods but i will use this method until someone can tell me a finer way.
I've tried to use all the advice together i've seen and this is simplistic way to get consistent results. :idea:

So ideally wanting 800-810mb final file size for overburn. I always get 825-835mb.

The most simplest and consistent way i found after trial and error :banghead: using the well known methods and to save time. Who wants to wait for 2-3 trial and error encodes or more to get the result???? NOT ME!!! :( and i'm sure you don't either. :lol:

This method works for me until someone tells me better.
What i do now is i have returned back to ToK http://www.kvcd.net/hedix/ToK_0.0.5.3.zip after trying cqmatic. cqmatic gave me a similar result. but i like ToK because it encodes sound and video with bbmpeg automatically to save more time.

The Auto Predictions get it wrong so i do this....

The Method: inc. Tok Settings

You probably know some of this already of course from formulas etc. in your head. But this works for me.

I start by doing the necessary in ToK ticking Tok "No Encoding(Only Prediction)" setting and when its done predicting...
I take a note of the Final CQ Prediction then i untick "No Encoding(Only Prediction)" and select No Prediction(Fixed CQ)
I then enter the Final CQ prediction number which is 76 for example but before i do i MINUS it by 1 to 75 and enter that.

THATS IT!! :wink:

This works if your 25mb 30mb over predicted filesize. I worked out that
a CQ of 1 equals 25-30mb a CQ of 4=approx 100mb so reduce your CQ accordingly. this will cut down on lots of re-encoding.

This compensates for 2-3% over file size prediction by reducing Final CQ Prediction by 1..
It is better to be tiny bit under filesize than over so you don't have to re-encode to get it right first time.
I read its harder to predict AVI filesize Mpeg-4 and gives less consistent results over dvd sources.....Hmmmmmmmmm
I setup Prediction & Spacing in ToK like so....nothing new here...except Length of Samples method.

Tok Settings:
New Faster Prediction Ticked
Precision% 0.50
Speed Up By 10 times
Length of Sample 72 for 23fps 75 for 25fps 90 for 29fps Untick Auto to select.
Number of Samples 1 for more than 100mins 2 for less 100mins
Factor for Prediction 1.0
Fixed Number of CDs 80mins 1 CD


Markymoo

Wolfi 09-05-2003 11:53 AM

You can try to lower the Factor for Prediction value 1.0 to 0.99 or 0.98 :)

//Wolfi

Markymoo 09-05-2003 12:02 PM

Thanks Wolfi i will try that. I have heard untick"New faster Prediction"
and using "2nd Group of Passes" default settings but dosent seem to make any difference to Final CQ.

Markymoo

Markymoo 09-06-2003 01:13 AM

Ok that has worked! It helps knowing what the individual settings do exactly.
I realise that lowering the "Factor for Prediction Value" does the same thing so i now use that. I have learnt something new. :o I haven't come across doing that before. Wish i had more time to experiment.

Thanks Wolfi again. :wink:

Markymoo

kwag 09-06-2003 01:18 AM

You can also use CQMatic and use CalcuMatic, and set your audio bitrate to 128Kbps.
Then, after you encode, if your file size is too big, encode your audio at 112Kbps. If the file size is too low, then encode your audio at 160Kbps.
That's what I do. I always predict at 128Kbps audio ;)

-kwag

incognito 09-06-2003 03:58 AM

Quote:

Originally Posted by kwag
You can also use CQMatic and use CalcuMatic, and set your audio bitrate to 128Kbps.
Then, after you encode, if your file size is too big, encode your audio at 112Kbps. If the file size is too low, then encode your audio at 160Kbps.
That's what I do. I always predict at 128Kbps audio ;)

-kwag

I do the same thing. :lol:

Markymoo 09-06-2003 10:53 AM

Superb!

Great Stuff!

This all good logical common sense. I can't go wrong! I'm sure this helps alot more than me. :D

Thanks ALOT Guys


All times are GMT -5. The time now is 07:30 PM  —  vBulletin © Jelsoft Enterprises Ltd

Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.