Hey Kwag,
I remember not long ago I asked the same thing about the "detect scene change" feature and you also told me to go ahead and use it.
I just forgot to tell you that I had also seen it in the download/usage intructions.
Shame on me :oops: ...That's why once in a while some guys still ask this one.

Cheer.

Calcumatic 1.0.6
 

I've updated CalcuMatic to version 1.0.6.
The only change is that audio now defaults to 128Kbps, instead of 112Kbps.
So I suggest always predicting with audio set to 128Kbps, and if the final MPEG file size is over or under the wanted size, you can encode the audio at either 112Kbps or 160Kbps, whichever is needed to compensate for the video size difference.

-kwag

If I end up with a filesize witch are ex. 50 Mb to big, are there any way to correct the filesize a litle bit by doing an other encoding with a different avg. bitrate?? Which formula should I use :?:

Hi azel,

The best way, as described above, is do your prediction with 128Kbps audio.
Then if your file is larger, as in your case, re-encode the audio at 112Kbps and you might also want to cut off your end credits when your doing your final muxing ( with BBMpeg ).
This way, you'll get a file size WAY lower than the 50MB in excess you had.
CQMatic does a very good job on most movies, but it can fail miserably on some films, depending on the distributed action of the movie. The only way to increase precision would be to increase the sampling, but at the cost of longer prediction which would then void the original purpose of CQMatic.

-kwag

I'd take acurate prediction over time anyday :D

Ok, then maybe I will put a "Long Prediction" option in CQMatic, so that it takes about 5 times more sampling then the "standard" prediction. This way, it should be far more accurate, but it will also take 5X times to find the correct CQ.
I'll look into that :) when I have some time 8O

-kwag

Not needed ... as the last days Krassi and I figured that a prediction using same sample size but with offset intervals set at every prediction turn will give a very acurate result. Even without pre-2pass run.

Hi incredible,

I'm not so sure about your theory, or maybe I just don't follow it.
How can you calculate a final size without prediction :?:
If you are using a fixed sample size, based on the size of the movie, it will not work :!:
For example: A one minute clip at a fixed CQ value, taken in the center of the movie, will have a different encoded file size if you encode another one minute clip from another part of the movie.
So you can't take an arbitrary sample based on the "run time" of a movie, calculate the supposed sample size based on movie time, and expect the complete encode to come out on target. I hope you understand what I meant :roll:
It's similar to what I tried months ago, taking the full VOBs ( demuxed video streams size ) of a movie, divided by the wanted size given by MovieStacker ( gives you the ratio ) and then cut an arbitrary part of the VOB and divide it by the ratio, and encode a KVCD sample matching that size. It just doesn't work :!:

-kwag

New version
 

CQMatic 1.2.03 is currently cooking in the oven ;)
I'm currently testing it. Will release it later today.
New function: Prediction X1 or Prediction X3 (selectable)
Defaults to X1, which is just as the current version of CQMatic.
Prediction X3, as it says, takes X3 (times 3) longer snapshots ( 15 seconds per sample, instead of 5 seconds as it's currently implemented)
This should yield much higher accuracy, but will also take three times longer to encode each sample :!:
End result: Higher precision and quality, and still faster than a 2-pass VBR.

-kwag

Hi, Kwag.

I assume I'll still need to allow 25MB or so for SVCD.

For muxing :?:
I assume you mean subtracting 25MB to allow for SVCD overhead, right :?:
If that's the case, probably yes, because with the new CQMatic, the final file size should be much more closer to the calculated by CalcuMatic.
I'm currently doing a final prediction in both modes (X1, X3) to verify the final CQ differences.

-kwag

Can you make a "autoclose" version of CQMatic 1.2.03????

Sure :!: :D
Let me open the oven, and I'll cook it in a couple of minutes :cool:

-kwag

Here you go ;)
http://www.kvcd.net/CQMatic-1.2.03_AutoClose.exe

-kwag

Thanks :D
I was just wondering. Could I include CQMatic into DVD2KVCD, like the AVS-filters????

Sure :D
As long as DVD2KVCD is free. Otherwise, we talk ;)

-kwag

Yes, of course :)

could someone explain the buttons to me? how do I know which mode I'm in with each button? so say if the button said Prediction X1 does that mean its in that prediction mode or if u press the button it will be in X1 prediction mode?

What is displayed, is the current encoding mode.
Default is "X1". If you press it, it changes to "X3", and that will be the mode if you start encoding.

-kwag

how come then when I choose prediction mode it does a full encode too after prediction? I had prediciton mode selected but it still seemed to 1. do a full encode and 2. produce a large final m1v file which caused a final mpg file size of nearly 900mb after muxin with 112 audio even when I used 128 audio in predicition aswell as 112 in calcumatic.

I'll take a look :!:


-kwag

oooooh I spotted a possible bug yay lol

Well, I tried it, and after selecting "Prediction Only", that's exactly what it did :!:
Just predicted CQ, and exited.

-kwag

well I feel silly I was usin a older version of cqmatic :oops: but hey I done a predicition and yer everythin is fine in latest version sorry about that :oops:

why does CQMatic check the video-resolution?
I tried to make a 480x288 - SVCD (MPEG-2)
and CQMatic won't encode!

Welcome Scharfis_brain ! Where have you been so long.

What do you mean CQmatic won't encode?

In regular and as I remember it's all Template-Settings based, also the encoding size, so if the CQmatic routine behaves abnormal, could it be that something's set wrong in your TE-project?

480x288?? (??something Field separarted??? as I know you are very much in interlaced stuff. I think maybe I'm a bit confused now, but you could explain me your intention)

Inc.

I want to encode 4:3 - Fullscreen progressive Video that suffers in Vertical crispness.

therefore some thing like VCD res (288 lines, too!) would be quite nice.

So i decided 480x288@25fps (instead of 480x576) with MPEG-2 would be cool.
My player (CH-505) supports it.

Now I want to make a CQ-encoding using CQ-Matic, but it says

"Your Video reolution is not valid"

480x576 works (who wonders) with CQ-Matic.

I think that this resolution-test is unnessesary.

Hi scharfis_brain,

CQMatic verifies resolutions, and because 480x288 is not a valid resolution ( at least 99% of the players won't support it ), I did put in those resolution constraints.
But then again, 528x480(576) and 544x480(576) are not valid either, but most players do support it. But now, probably new players do support this :!: So here you have it. Happy birthday ;)
http://www.kvcd.net/CQMatic-1.2.04.exe

-kwag

u know how u had the auto shutdown function in a previous version of cqmatic I can't remember if it was a shut down windows function or not but a shutdown windows function can come in handy. could this be brought into a new build with a option to enable or disable the feature.

CQMatic never had a shutdown option :!:
I do have it planned for a future version.

-kwag

oh yeah sorry I meant autoclose function hehehe but that auto shutdown would be a handy feature especially for overnight predicitons 8) and havin both as a tick box in cqmatic to enable or disable the feature.

also I was wonderin which average bitrate do I use in calcumatic the first bitrate or the second one?? I've always been a little confused by that why not just have one average bitrate?

The second average, "0.57 * average", is the suggested value to be used as MIN bitrate. It has to do with better prediction.

-kwag

ah good I used the right bitrate lol, well I'm doin a test of cqmatic and tok and in CQMatic usin X3 prediction I got 45.05 , now in tok I got 62.766. The movie is 102 mins and I used 352 x 576 template usin latest script, goin by results I'm more tempted to go with tok cause its normally been right in past for me CQMatic in the past has ended up bein too big in the end mpg file.

@Kwag

You know what I find annoying :?: Having to input the path to TMPGEnc every time :x

Why can't CQMatic save it in a config file and read it in each time it is started :?:

I know you said that you didn't want to tie CQMatic to any programs, but I would say that it's already tied to TMPGEnc, CCE & MCE by the Encoder choices at the top :wink:

Can only be an improvement in my book.

That's exactly what it does. You should not have to give the path each time. There is a problem on your PC :-)

I'll try it again tonight Phil.

Thanks m8 :)

@Kwag

THX. The new version of CQMatic and the feature X3 is very cool and like always easy to use. My first tests are very good and exact.

But can programm one version with batch encode or predict I think this is very cool for many user. Or what do you think? :?:

Maybe in a future "future" version ;)
But don't hold your breath :lol:

-kwag

OK kwag :wink: