Sorry, even worse here with the Duron, 30-40 min. per prediction cycle. Tried with different and shorter movies too, but they are also very slow. Will take hours to find the correct CQ. How do I configure the Prediction & Spacing page in ToK to use the same sample cycle as in CQMatic? I'd like to try and see if there's any difference in speed when using ToK.

took now a 53 min, wanted it to have it (for tests) on 300mb ;

calculated avg bitrate , with 631.

here the log

using cq 60
encoder started...
encoder end...
difference=-5439988.500000
using cq 90
encoder started
encoder end
differnce=-5439988.500000
cq above watermark , cq set to 90
using cq 90
cqmatic complete

hmm strange

Set Length of sample to 6, and number of samples per minute to 4.

-kwag

Load your project (.tpr file) in TMPEG manually, and hit "Start" to encode. See what you get

-kwag

?
don´t know exactly what you mean ?
when i hit start he starts encoding ...

got another test running now, so can´t do another one...

what i wanted to say :
cqmatic is getting information on cdsize, nr of cds...about the average bitrate , i think?

so why does it take cq 90 , when i like to have the movie on 300mb ?

but thats not the most important thing,its more important that it runs stable, finds the cq as fast as possible, so that everybody can use it

Kwag, tigger , please:

i have doubts ...
tigger wrote:
"took now a 53 min, wanted it to have it (for tests) on 300mb ;
calculated avg bitrate , with 631."

this size (300mb) is not too low for 53 minutes?
and the average is not too low?


maybe i misunderstand....seems strange for me!

you´re right of course, would never do that

but for 1 test, i chose such values...

i thougt that cqmatic would calqulate the cq very low...perhaps 20-30 as cq or sth, but it chose 90

and thats strange for me

Just finished running the test.
Source was 104 min. 576 x 304 PAL AVI movie.
Using the same script for both tests, and destination was MPEG2 - 480 x 576 PAL.

One prediction cycle with CQMatic took 16 min 40 sec, with a source range of 1 min 39 sec.
One prediction cycle with ToK took 6 min 17 sec, with a source range of 1 min 44 sec.

I have checked the project file over and over again, and as far as I can see, everything looks ok. This really puzzles me....

Forget about the current beta. Wait for the next release. Don't bother testing testing BETA 7.

This WILL be fixed today on BETA 8 as I'm duplicating the problem now. Until later today, no more BETAS

-kwag

If somebody want beta 7 here the right link:

http://www.kvcd.net/cqmatic-1.0b7.exe

Kwag forgot the "-" ...

Great, looking forward to it!

I think this will be the right link ... then:


http://www.kvcd.net/cqmatic-1.0b8.exe

hope beta8 will be there soon

Kwag I'm still getting CQ prediction loops with beta 7. It starts at CQ 60, then 50.25, 40.83, 40.66, 40.57, 40.53, 40.51, 40.50, 40.50, 40.49...

And that's where it gets stuck. The value for Difference = also doesn't change. It also SEEMS like prediction samples take a longer time to encode than with ToK, but I haven't done a direct comparison.

I'm encoding a widescreen avi, 640x272, 152 min long, avg bitrate 608, into a KVCDx3.

avg 608 @ KVCDx3???
Is the quality still good at these settings?

Oh... CQMatic calculated CQ is wrong... I want to encode a 100 min movie... but the CQ is 100MB too big...

please fn86,
post big details....
wanted size,CQ found,average,etc.

Try CQMatic RC-1. You shouldn't get those numbers, and it should predict in around 4 or 5 tries

-kwag

Actually, I jumped to RC-1 (Release Candidate), because I believe it's now almost ready for prime time
Only final prediction accuracy tweaks "might" be needed
Here's the link, in case some of you haven't noticed it:
www.kvcd.net/cqmatic-1.0RC1.exe

-kwag

Hello Kwag:

Cqmatic is now working for me. The video stream error message that I was receiving, as well as the strehed screen, were corrected following krassis and your answer to previous posts. On Cqmatic v6 I was seeing up to 2 hours of CQ checking, prior to encoding. I am presently running v RC-1, and so far is in its third pass. It takes about 12 minutes per pass, for an 80 minutes dvd. Will let you know how many passes it takes prior to the actual encoding, which in this oicture is about 13.5 hours.....
Question: What is the shortest film, in minutes, that can I test with no problems? On previous versions I have used 4 minutes, but Moviestacker was given me erroneous numbers for the average kbs. ( anywhere from 8,000 to over 240,000- Theshortest the film, the higher the number. Obviously I am doing something wrong here, perhaps I should do this manually no?)

Thanks again for your help

Totonho03