Yes. It has to do with the linearity range of CQ, and makes the following CQ values easier to calculate.

-kwag

I'll add a "CQ Override" check option for the next rev ;)
But remember: Use it at your own risk :!: :lol:

-kwag

CQMatic 1.1.02
 

Good morning people :D
Let's start the day with more new stuff ;)
http://www.kvcd.net/CQMatic-1.1.02.exe

Changes:
First of all, forget DivX predictions from this release, and on.
The new sampling is now One snapshot every 5 seconds, with a time slot of 0.0833 second each. This provides a very fine grained sample of the material to be encoded, at the cost of longer prediction. There's just no way around it :!:
The current sampling stresses SO MUCH the DivX (XviD) CODECS, that renders prediction useless on these types of materials. With MPEG-1 or MPEG-2, this behaviour is not seen. It's a problem related to "seeking" random frames in MPEG-4 CODECS. So, bye bye MPEG-4, as far as prediction goes, until future versions of those CODECS are revised for faster random access.
I've added an "Interlaced" hack, that takes into consideration if the source is 29.97fps interlaced. I've only tested it on one Video ("Styx - Back to Paradise") and the CQ was right on target. I don't have any other Video DVDs, so I can't test it any further. Your testing is greatly appreciated :!:

If the source is Interlaced, and you are using TMPEG to deinterlace, the "Interlace" checkbox will auto detect, and will be checked automatically. If you are using an external deinterlacer ( Bob(), FiledDeinterlace(), etc. ), then you must manually "check" this option. This applies ONLY to interlaced sources.

I've also added a "Override Default CQ" for prediction. If you "check" this option, CQMatic will use whatever CQ you set in your project (.tpr) file. If you leave it "unchecked" (default), CQMatic will use it's own (recommended) starting CQ/CQ_VBR value for prediction.

Have fun :!:
And please, report EVERYTHING (good or bad), so I can keep pushing this forward, and tune it in the right direction.

-kwag

Thx Kwag,

which bitrate calculator are you using :?:
What is your recommended resolution :?:
Prediction is currently running...

CQ seems to be a bit low, but i'll do a full encode to see if its hitting target.

Remember this: Finding CQ will ALWAYS take a long time when the values are below 50, because there is almost no file size change for a change in CQ value. Same applies above 80. The fastest results will be between CQ of ~50 to ~75. There's just no way around it :!:
Look at the File size difference = xxxxx. There's almost no change, for a change in CQ.

-kwag

What is your target size :?: :?:

Sure. I don't have any problem with long prediction cycles, for me its more important whats coming out :D

My target size is 188 MB.

Me too :D Ok, that's what I thought, based on you numbers. Let me know the final size, as I see that your source is interlaced. :)

-kwag

Will the CQ be affected by the Video Source Type ?

I mean, if I set the Video Source Type in TMPGEnc to interlaced instead of Non-interlaced (Progressive) will the CQ be smaller or bigger ? And if yes, will the difference be considerable ?

And will the video quality be affected, if I set the Video Source Type to interlaced, even if the source isn't interlaced ?

If you set the source in TMPEG to interlaced, but your real source is not interlaced, you'll throw off the prediction formula completely :!:
CQMatic will assume the source is interlaced, and use some internal correction factors. So your file size will be way off :)

-kwag

Good morning folks:

This is my daily report, but I can see that it is already obsolete. Well not quite, because I still have the 64,000 pesos question....... Why is Moviestacker given me the erroneous film length?...Am I the only one having this problem? Just for fun, next time you guys run dvd2av1 and moviestacker, please compare the time you see in dvd2avi (audio time stamp) to the time given by Moviestacker. Thanks

The encoding finished earlier today, and actually I am not going to post the log, but the file size is still large. The file size of the M1V is now 978,573 KB, which is a heck of a lot better than the 1.2+Giga, but far from my target, which is about 700 MB (Moviestacker number)
As mentioned before, when I changed moviestacker to the proper time (from 97 to 120 minutes), the average bitrange also changed, it went down, from ~ 1000 kbps to 780 kbps, so the next logical question is, if the average bitrate goes down, would the final M1V file go down as well? If the answer is yes, then perhaps I will reach target on my next test. I will run the new CQmatic and post the results of it, but the file size will be seeig manana........If TMPGenc would improve its encoding speed it would be great (Yes, I know, I can always purchase a 2 gig machine, but........)

Thanks

Totonho03

Thanks

Totonho03

@ Kwag

I think you didn't understand what i meant (presumeably because of my primitive english) :wink:

I'll try to explain it in really easy way:

I have a not interlaced source with 1000 Frames and I encode it with CQ 50 in TMPGEnc with the Video Source Type set to "interlaced". Will the Size of that clip be bigger or smaller than the same clip with the same CQ and the same framecount with Video Source type set to "Non-interlaced (Progressive) ?

Your file size will be identical ;)

-kwag

just wonderin is there a possibility u could add a function that gets the average bitrate like in moviestacker??

That's what the little "calculator" icon is there for :)
It will be integrated in version 2.0 :cool:

-kwag

XSVCD
 

When i'm using other max and min values, eg. min=300 and max=3300,
won't the prediction be so accurate or will the final size be out of range?
Where are the differents beetween max.=2000 and 3300??? :?

Re: XSVCD
 

Hi OBK,

The way CQMatic predicts, it might just solve the old prediction problems, where we had to tighten the MIN/MAX in order to achieve better accuracy.
Because of the way the new prediction in 1.1.02 works, it might not be necessary to restrict the bitrates :!:
I haven't tested that, but thinking about it, CQM takes so many samples per minute, that you might be able to use any bitrates you want, and still maintain accuracy. You're going to have to try it out yourself :)
As far as max of 2,000 and 3,300, the higher you go, the better the quality and but also the larger the file size.

-kwag

I am using Telecide()/Decimate() with DVD2AVI non-ForceFilm output with KDVDfull. Should I check or not check "Interlaced Source" on Version 1.1.02?

It sounds better and better!

But when predicting in two different max bitrates the final size should
be the same, only the CQ changes, or am I wrong? :roll:

Thanks, OBK!