digitalFAQ.com Forums [Archives] - Bitrates: Cq matic final cq always 89.xx

digitalFAQ.com Forums [Archives] (http://www.digitalfaq.com/archives/)

- Video Encoding and Conversion (http://www.digitalfaq.com/archives/encode/)

- - Bitrates: Cq matic final cq always 89.xx (http://www.digitalfaq.com/archives/encode/5351-bitrates-cq-matic.html)

Bitrates: Cq matic final cq always 89.xx

hi,
when using cq matic my final cq is always 89,xx!
ive deactivated things like detect scene change and don't know whats wrong ):

also the path to the file (the path in the tmpgenc project file to the mpeg2 file) has no spacers or something like that.
"source" is an mpeg2 file!

hope anyone can help me.
please dont answer use search, thx.
there are many topics with more than 30 pages...

sorry for wrong expressions, my english isn't the best, but i think you can understand it!? ;)

Post CQMatic's log :!:

-kwag

k, here it is:
CQMatic Log

Quote:

http://www.kvcd.net
CQMatic Version 1.2.00
Copyright Softronex Corporation, 2003.
All rights reserved.
Time: 22:11:42 Date: 09/02/2003
Ready!
Project: F:\cqmatic_try.tpr

Creating: CQMatic.tpr

F:\cqmatic_try.m1v
Project resolution: 480x576
Execute.
Movie Time: 97
Average Bitrate: 940.5
Prediction Only mode
Executing Prediction Phase...
Process started at 22:12:28
On 09/02/2003
CQ set for prediction
Setting up initial sampling.
Using CQ of 60.00
Prediction cycle #1
Encoder started...
Process time: 0.00 minutes.
Encoder end.
File size difference = -14438400.000000
Low fence: 60.000000
High fence: 90.000000
Last CQ = 60.00
Current CQ = 75.00
CQ difference = 15.000000
Using CQ of 75.00
Prediction cycle #2
Encoder started...
Process time: 0.02 minutes.
Encoder end.
File size difference = -14438400.000000
Low fence: 75.000000
High fence: 90.000000
Last CQ = 75.00
Current CQ = 82.50
CQ difference = 7.500000
Using CQ of 82.50
Prediction cycle #3
Encoder started...
Process time: 0.00 minutes.
Encoder end.
File size difference = -14438400.000000
Low fence: 82.500000
High fence: 90.000000
Last CQ = 82.50
Current CQ = 86.25
CQ difference = 3.750000
Using CQ of 86.25
Prediction cycle #4
Encoder started...
Process time: 0.00 minutes.
Encoder end.
File size difference = -14438400.000000
Low fence: 86.250000
High fence: 90.000000
Last CQ = 86.25
Current CQ = 88.13
CQ difference = 1.875000
Using CQ of 88.13
Prediction cycle #5
Encoder started...
Process time: 0.00 minutes.
Encoder end.
File size difference = -14438400.000000
Low fence: 88.125000
High fence: 90.000000
Last CQ = 88.13
Current CQ = 89.06
CQ difference = 0.937500
Using CQ of 89.06
Prediction cycle #6
Encoder started...
Process time: 0.02 minutes.
Encoder end.
File size difference = -14438400.000000
Low fence: 89.062500
High fence: 90.000000
Last CQ = 89.06
Current CQ = 89.53
CQ difference = 0.468750
Using CQ of 89.53
Prediction cycle #7
Encoder started...
Process time: 0.00 minutes.
Encoder end.
File size difference = -14438400.000000
Low fence: 89.531250
High fence: 90.000000
Last CQ = 89.53
Current CQ = 89.77
CQ difference = 0.234375
Using CQ of 89.77
Prediction cycle #8
Encoder started...
Process time: 0.00 minutes.
Encoder end.
File size difference = -14438400.000000
Low fence: 89.765625
High fence: 90.000000
Last CQ = 89.77
Current CQ = 89.88
CQ difference = 0.117188
Final CQ value is 89.77
CQMatic complete!
Total minutes of process: 0.03
Process ended at 22:12:30
On 09/02/2003

thx in advance!

All size are negatives, that means TMPGEnc doesn't encode anything.

Be sure to have cut editing reset and range selection unckeck in the advanced settings of tmpgenc before to save the project (as text file)

ive done all like written down here:
http://www.kvcd.net/forum/viewtopic.php?t=5145

-saved as "text" project
-source range disabled
-detect scene change disabled
-start frame is 0 and end frame -1 (at source range)

any more i should change?

hmm damn i havent changed really anything and now it seems to work...
i reseted source editing... but thought it was reseted, cause start frame was 0 and end frame -1....

ive chosen prediction only now it started tmpgenc and it is encoding...
already 1:14 (source pos.) encoded.... thought it will only use a small sample, max. a minute or so?

This part is also important (in bold):

"You must make sure that you save the project without source range selection, and "Cut editing" cleared (or reset)"

Did you check that point ?

Quote:

Originally Posted by Dialhot

This part is also important (in bold):

"You must make sure that you save the project without source range selection, and "Cut editing" cleared (or reset)"

Did you check that point ?

its saved without source range sel.
you cut editing button at source range, right?
reset is grey (cause its already reseted!?).

or do you mean something else?
by the way: it encoded over 5minutes (source pos.)

Quote:

Originally Posted by StayAlive

you cut editing button at source range, right?
reset is grey (cause its already reseted!?).

grey = already reseted, yes. And it seems it was your problem as after doing it, tmpgenc starts to encode (yes, it does only a sample of 120 sec for prediction else it will take DAYS to find the optimal CQ :-))

hmm i've got a new problem, a strange problem...
i've unchecked source range, then i save my project.
even if i close tmpgenc, start tmpgenc again and load the project its still unchecked - like it should be.

but when im using cqmatic and it starts to enode (precision mode) source range is again checked.

ive reinstalled tmpgenc & cqmatic - still the same :cry:
im using TMPGEnc-2.520.54.163-Plus-EN - can this be the problem?
has ever anybody tested cqmatic with this new version?

Quote:

Originally Posted by StayAlive

but when im using cqmatic and it starts to enode (precision mode) source range is again checked.

For sure ! CQMatic does use source range selection. And that is why it must be unchecked in the initial project : without this, CQMatic can't set its own selection range settings and that makes TMPGEnc to fail.

hmm *lol* k, thx, didn't know that ;)
but how already posted:
it (still) starts encoding, encodes, encodes - it dosn't stop after 120seconds, i already was at over 5minutes source position (the i chanceld). anyone knows whats wrong when its not the source range option?

(of course i've chosen prediction only, also shown in the log)

This problem was already reported to me twice and Kwag never gave a solution. :-(

Perhaps this time ?

Quote:

Originally Posted by StayAlive

Redo your .d2v project file :!:

-kwag

ive used no dvd2avi and no project file the whole time, but now ive saved the mpeg2 file as project with dvd2avi and chosen it in tmpgenc.

but also with the .d2v its the same problem:
ive chosen prediction mode, it starts encoding and dosnt stop (after over 3 minutes source position ive chanceld).

here's the log, may be it can help to find my problem:

Quote:

http://www.kvcd.net
CQMatic Version 1.2.00
Copyright Softronex Corporation, 2003.
All rights reserved.
Time: 20:56:29 Date: 09/03/2003
Ready!
Project: F:\cqmatictry.tpr

Creating: CQMatic.tpr

F:\cqmatictry.m1v
Project resolution: 480x576
Execute.
Movie Time: 97
Average Bitrate: 940.5
Prediction Only mode
Executing Prediction Phase...
Process started at 20:56:58
On 09/03/2003
CQ set for prediction
Setting up initial sampling.
Using CQ of 60.00
Prediction cycle #1
Encoder started...
Process time: 10.62 minutes.
Encoder end.
File size difference = 0.768523
Low fence: 2.000000
High fence: 60.000000
Last CQ = 60.00
Current CQ = 46.11
CQ difference = 13.888626
Using CQ of 46.11
Prediction cycle #2
Encoder started...
Process canceled

There is no problem 8O
It's predicting :!:

-kwag

Quote:

Originally Posted by kwag

There is no problem 8O
It's predicting :!:

-kwag

well it encodes and encodes, once it was even at 10minutes... (source position!)
thought there will be only encoded a sample of 2 minutes for every tried cq or is that wrong?

If you load your .tpr in TMPEG, and then go to source range and scroll all the way to the right, does it read 97 minutes :?:

-kwag

it reads/shows 96,27!
even once tried it with 96min (entered @ cqmatic) - same problem.
maybe problem is really the new tmpgenc version?

could even post a screenshot of my tmpgenc config(s) if needed...

What version are you using :?:
I'm on 2.520, and never had a single problem :!:

-kwag

im using TMPGEnc-2.520.54.163-Plus-EN
i wish i also wouldn't have any problems ;)