Log in

View Full Version : Using the "Quality" setting


3ncrypted
6th September 2005, 19:31
I don't really care all that much about the file size I end up with. Everytime I go to run AGK I have to let it run thru a bit of the encode so I can see how large to set the file size so that I get resolution in the 600's and 700's. If this is what I'm doing, would using the quality setting at 100% save me a lot of time and hassle? A 100% quality "one pass" encode is basically as good as AGK can encode...right?

I've been reading posts about using the "quality" setting and I've seen people mention that using anything above 75% is a waste. Is that true? Or is there more to it than that? Is there anyway to calulate a ballpark figure for file size at a given percentage?

unskinnyboy
6th September 2005, 20:58
Why don't you use SEARCH and do some research before asking these repetitive questions? AutoGK "quality" setting discussion for the Nth time now, urgghh..

75% is no set-in-stone cut-off figure, depending on your material this can change. But yes, too high a quality setting means you are not exploiting the benefits of MPEG-4 compression. And no, you cannot calculate a ballpark figure, filesize is totally unpredictable. Maybe with a lot experience with similar material you will get a general idea, but otherwise no calculation possible.

3ncrypted
7th September 2005, 22:23
I apologize. I did a few searches but didn't read THIS POST (http://forum.doom9.org/showpost.php?p=698597&postcount=2) thoroughly enough. It answers my question about whether one pass encodes are the best quality you can get.

75% is no set-in-stone cut-off figure, depending on your material this can change. But yes, too high a quality setting means you are not exploiting the benefits of MPEG-4 compression. And no, you cannot calculate a ballpark figure, filesize is totally unpredictable. Maybe with a lot experience with similar material you will get a general idea, but otherwise no calculation possible.

Thanks. You've cleared some things up and I'm going to stick with 2 pass encodes.