You'll see that TMPEG automatically selects "Non-interlace".

-kwag

Yes. You're right :)

-kwag

sorry for the lame answer didn't get the latest version till after postin msg :oops:

Kwag...want to make sure I got this. If I am using FieldDeinterlace() in my script on an interlaced source I usually set video source as "Progressive" in Tmpgenc for mpeg-1 project. In CQMatic I still check the "interlace" box however. Is this correct?

Cheers
Ozjeff99

Hi kwag,

in CQMatic there are disabled checkboxes for MCE and CCE. Do you think you'd sometime be able to include vmesquita's CCE method in CQMatic?

Regards,
new_bee

Yes. You must check the "interlace" option in CQM.

-kwag

I haven't tried that yet :!:
And I will go forward, only when I finish with the TMPEG problems we currently have. CCE should follow. MCE, I don't know. I'm still waiting on a E-Mail I wrote to them, related to command line control. Apparently, MCE doesn't have any :!:
If that's the case, MCE will be removed from the option, as there's no way to use the program from external sources.

-kwag

Is this true? I thought if you have telecide and decimate or fielddeinterlace in your avs script it is considered progressive material because it is frameserved as such?

Should I use the interlaced option even when using telecide and decimate to convert 29fps interlaced hybrid material to 23fps?

No. Only when the source is 29.97fps interlaced and you are encoding at 29.97fps.
If your source is IVTC'ed, with telecide or any other function, then your source is seen as progressive by the encoder, and you must "uncheck" the option. ( Actually it will be unchecked automatically, because CQM will see "Progressive" in TMPEG's source type )

-kwag

Thanks :D :!:

Kwag,

As you probably know, CCE doesn't have native command-line support. But we can use ECLCCE to add this functionality. ECLCCE does not crack CCE executable, it just simulates normal user input, and uses WIndows Functions. So probabily, this could also be done with MCE to allow CQMAtic to work! This is just an idea, I don't know exactly how this is implemented in ECLCCE.

[]'s
Vmesquita

Hi vmesquita,

Yes, I think ECLCCE is what DVD2SVCD uses to control CCE.
It's really sad these programs (CCE, MCE) don't have any kind of command line control :?
I really don't like the "User simulated software" programs, as they can fail under some conditions. And then, the complete process is messed up :!:
But if it is the only alternative, then that's the way it will have to be done :)

-kwag

It's definatelly sad... It's not really reliable, and new versions sometimes kill the thing... But sometimes it's the only way. I think most companies really don't care about this.

[]'s
Vmesquita

CQMatic 1.1.04 up!
 

As usual, at the top of this thread :!:

Changes to 1.1.04
Added: Internal prediction factors now taken into consideration, depending on the project resolution.
Valid resolutions are:
352x240(288)
352x480(576)
480x480(576)
528x480(576)
544x480(576)
704x480(576)
720x480(576)
Any other resolution will not be processed
A warning message will be issued by CQMatic if you try to process any another resolution.

-kwag

XSVCD
 

Movie length: 146Min
CD's: 2 SVCD's (2 languages)
max: 3600; min: 350; avg: 1145
720*576 Pal

After encoding the Filesize was ~116MB to small!
MovieStacker's file size: 1216MB
Filesize after Encoding: 1100,5MB

The Quality also is really good! :D :D :D

You better try CQMatic 1.1.0.4, since the previous Versions aren't very accurate.

Better yet, get 1.1.06 :mrgreen:
http://www.kvcd.net/CQMatic-1.1.06.exe

Enjoy ;)
-kwag

But something wrong...

Why you sample the "end" of the movie, when the generic is display...

99% of tihe time, it's only a big black background with white letter...

This 4 minutes of generic at the end of a movie, calculated by CQMatic don't "false" the result???

Hi Rambytes,

CQMatic samples whatever you set in your project file. If you don't want end credits, then cut them off in DVD2AVI, when you do your project file.

-kwag

you're right...

aah Rambytes..

also, if you are using the VFAPI route, you could cut the credits out in vdub
and NOT have to worry about the end creadits AND the extra TMPG steps
and things :eeks:

I'm not saying to NOT use AVIsynth of course, cuase it's GREAT, but I just
haven't gotten the cropping/resizing things :hammer: nailed yet !!
It's not easy asking simple noob questions, and then a :eyebrows: guru is to proud to
answer such questions, and kicks you off w/ a :dunce: stupdity response
I slowly get my answers, thanks to this forum here. anyways.. just me ranting
about nothing.. :heee:

But, I like using the VFAPI(psuedo .avi) to vdub route because I have what
I consider THE BEST cropping (for 16:9) encodes around (imo) to my taste.
Anways.. the above is definately something to consider too, if you want to
cut credits or anything 'in between' (specially) using vdub as your server :!:

Be cool dude,
-vhelp

CQM Updated to 1.1.07.
Top of this thread.

-kwag

Are you guys having success now with avi conversions?

Look at my post here ;) http://www.kvcd.net/forum/viewtopic.php?t=5522

-kwag

I think I've missed something here :oops: - can someone please explain or link to where the "min-bitrate = 0.57*avg-bitrate ; max-bitrate = 2000" modifcation came from? Whats the benefit of using these settings compared to the regular 300-2500kbps range? Does it apply to non-MA encodes as well?

TIA girv :)

Hi girv,

It has to do with TMPEG's linearity range. The recommended MIN is (0.57 * average bitrate) and the MAX is 2,000. That is, if you are using the MA script. If you are not using the MA script, then you must use a higher MAX bitrate (~2,500) to overcome the visible macroblocks on high motion scenes.

-kwag

Version 1.1.10 released!
 

CQM updated to version 1.1.10
Grab it at the top of this thread.
And PLEASE, UNCHECK Detect Scene Change in TMPEG before you save your project :!:
That's one reason our prediction is off in some movies.

-kwag

Ripper!!!!! :lol:

At long last with a few unsuccessful attempts with CQMatic, I used 1.1.07 on Santana Supernatural Live PAL DVD. Full Screen, Lot's of movement, very low CQ of 38 (still very watchable), interlaced. This was the DVD from hell but CQma"J"ic did its job and put the whole encode with sound to within .5%. 8)

No worries Kwag mate. Thanks a million. Feels like a mega-milestone
Cheers
ozjeff99

Where does 0.57 come from in "(0.57 * average bitrate)" ?

Re: Version 1.1.10 released!
 

Should "Detect Scene Change" be unchecked during both prediction and encoding?

Re: Version 1.1.10 released!
 

Yes.

-kwag

Now I can't find the thread where we came to that percent :!:
I know it's the right balance below average bitrate and a MAX of 2,000, after many trial runs. This may now change, however, with the latest version of CQMatic and the way prediction is done.

-kwag

CQMatic Version 1.1.11
 

CQMatic Updated.
http://www.kvcd.net/CQMatic-1.1.11.exe

-kwag

Hi Kwag..

.
.
I believe that the MIN = (0.57 * average) formula was derived from
one of the following threads.. however, I believe it may have started
on page 3 of the last thread :wink:

* Confirm TMPGE Settings

* File prediction experiment #1,000,000 (pg 5)

* File prediction experiment #1,000,000 (pg 3)

Good luck.. TGIF !!
-vhelp

Version updated to 1.1.12a.

-kwag

I've been testing CQ 1.1.12 on an analog capture. My results seem a bit strange:

My settings:

Movie Time: 117
Average bit rate: 800



My Results:

Final CQ- 2.11 (?)

According to BitrateViewer:

Aveage bit rate: 384
Max bit rate: 905
Min bit rate: 328
Final file size: 466,888

The movie was Chocolat.

Hi MrTibs,

Was this with HuffYUV :?:

-kwag

Is this correct 8O :arrow: Max bit rate: 905

The source is an analog capture using HuffYUV, 352x480. The only noise filter used was PixieDust().

Here is the CQ log (as best I can re-type it with my broken kb)


http:\\www.kvcd.net
CQMatich Version 1.1.12a
Copyright....
Time 17:19:28 Date: 08/18/2003
Ready!
Projectc:\chocolat_cq_matci.tpr
Creating: CQMatic.tpr
C:\Avisynth\chocolat_cq_matic.mpg
Project resolution: 352x480
Execute:
Movie Time:117
Average Bitrate: 800
Full Encode mode
Executing Prediction Phase...
Process started at 17:22:17
On 08/18/2003
Setting up initial sampling.
Using CQ of 60.00
Prediction cycle #1
Encoder started...
Process time: 9.13 minutes
Encoder end.
File size difference = 0.023225
Low fence: 2.000000
High Fence: 60.000000
Last CQ = 60.00
Current CQ = 31.00
Prediction cycle #2
Encoder started...
Process time: 90.93 minutes
Encoder end.
File size difference = 0.023703
Low fence: 2.000000
High fence: 31.000000
Last CQ = 31.00
Curren CQ = 16.50
CQ difference = 14.500000
Using CQ of 16.50
Prediction cycle #3
Encoder started...
Process time: 90.52 minutes
Encoder end.
File size difference = 0.023704
Low fence: 2.0000000
High fence: 16.500000
Last CQ = 16.50
Current CQ = 9.25
CQ differnece = 7.250000
Using CQ of 9.25
Prediction cycle #4
Encoder started....

---- this goes on until Prediciton cycle #9-----


As for the max bit rate, yes it says 905 but to be honest, I don't see where it ever hits that. The short lived peak seems to be at the begining and it maxes out at 543. Most of the movie is at about 345.

When I encoded the movie (from a Huffy capture from TV) at a CQ of 100%, the average bit rate was about 1341 with a max of 2432. The final file size was 1,355,977.

Hi MrTibs,

Verify that you only have "Checked" "AVI VFW Compatibility Reader" in TMPEG. Uncheck ALL other options. Maybe your capture is being read by one of the darn DivX (XviD) CODECS, and that's what's throwing off file reading and proper prediction from your capture.

-kwag