CCE 2.70 vs. CCE 2.66
 

I did some testes and find out some interesting things.

http://www.digitalfaq.com/archives/i.../2005/11/9.gif

We can see that CCE 2.70 files, both actually encoded trhough EclCreate, and same size of course, are the littles one files.
As we know KVCD are biggers than BVCD ones.
The more interesting thing is that files created with CCE 2.66 are bigger if we change a few options in ecl files.

The differences in ecl files are:

I think "opv_q_factor" doesn't matter in the different size of files, as it was not OPV encoding.
There is not any other meanfull difference.
I don't know how, with these differences, all programs could end with a similar final size with a same avg bitrate???
Does somebody know how to interprete this, related with the final size difference.

Re: CCE 2.70 vs. CCE 2.66
 

Just remember that there's a relationship between file sizes and any matrix, when all are encoded with the same constant CQ/Q.
You can't encode at the same CQ/Q setting with different matrixes, and expect the same quality at the final file size.
Make a subjective test, so that all the encodes look basically the same, and THEN see which matrix created the smallest file size. ( I already know which ;) )

Remember :arrow: "There is no "Notch" pattern on ANY other matrix", and that (plus a couple of other bits) makes a hell of a difference on filesize/quality for a given footprint.

-kwag

Re: CCE 2.70 vs. CCE 2.66
 

[quote="Prodater64"]If I'm not wrong :
Automatic Q-Matrix switching. This should be deactivated to be sure that K-Notch is used anytime during the process.
Creation of the vaf file during first pass insteed of using the existing one (force to redo the 1st pass), nothing to do with file size.

Very important if you let CCE to do the resize ! You encoded in anamorphic in this and in letterbox in the other ECL (or the opposite...). No action on the filesier if you did the resize with avisynth.
[quote]h_filter=1[\quote]
Usage of a high-pass filter. This must be removed also. It is like using "DCTFilters" in avisynth : depending on the setting the result can be a disaster on the quality (blurring effect). For KVCD we use to deselect ALL filters in the encoder, there is not reason to change that.
Same as above : do not use internal encoder filters. If something need to be filtered, the script is there for that.
I don't know the purpose of that setting.

Thanks for your answers.

Re: CCE 2.70 vs. CCE 2.66
 

It means DC precision 9 bits. I think 0 means 8 bits and 2 means 10 bits.

Re: CCE 2.70 vs. CCE 2.66
 

Yep, Thats right !

For CCE 2.66.xx to 2.70.xx the values are:
0 = 8 Bits
1 = 9 Bits
2 = 10 Bits

For CCE 2.50.xx the values are:
-1 = AUTO
0 = 8 Bits
1 = 9 Bits
2 = 10 Bits

Cheers