From your CQMatic log:

Thats a very long movie...2237 min ??
Are you sure it shouldn't have been 46 min and avg bitrate of 2237 ??

Edit: Ups, you noticed allready... :D :D

correct the values and try again my friend OBK!

your problem can get out of my head...
i was thinking to ask about your script but now you found the error,
you will get the perfect CQ.....we're waiting your good results.

:wink:

Hi,

may I've found the problem ...

I've tried to predict the movie again using the new version of CQM (1.1.11) but failed with the same result. The log show the same negative file size difference and no sample file is created.

After that I loaded the original tmpgenc project file into tmpgenc and it works. Loading the CQMaticMaster.tpr generated by CQM while prediting also works. But if I try to load the CQMatic.tpr into tmpgenc the following error message is displayed:
Visited the file via vi and read the following (only copied a view lines around the line 367):
The line 367 is the line saying StartTime = 0. But the error seems to be the > after the end two lines above. If I remove the > the file is loadable for tmpgenc and encoding takes about 12 minutes. So that file contains some part of "Sampler" like movie fracment selection.

For me, this seems to be the bug that prevents CQM to work as desired at my system. But I don't know where the > comes from. If needed I can post or email the hole tmpgenc project file for debuging.

Holger
[/code]

I don't think that this is a bug in CQMatic! This Error I had 2 weeks ago, too, and after I reinstalled TMPGEnc it was away! Try this:
-Remove TMPGEnc from your system!
-Restart your computer
-Install TMPGEnc again!
-Create your ".tbr" completly new!


I hope it works!


OBK!

Hey, there is a 'smarter' way:
just go to Settings/Advanced, double click on Source range, accept the error message, and click on Cut Editing/Reset..

That's it! :)

Fabrice

.
.
Also, I've found that if you just delete all the *.TPR files that CQMatic
puts in the current folder might need to be deleted. I've always felt that
keeping the older/previous set of CQM generated files SHOULD be deleted
so not to "taint" the latest and great version of CQM that continues.

This should probably be added to the instructs on CQMatic main page :wink:

:idea: Or, better yet, just add a (yet another, for which has still not ben done)
button to refresh (delete) all CQM generated files !!

:arrow: PS to above, and where's that [DELETE] button for clearing the contents of
the Listbox of the LOG ?? ?? ?? 8) :lol: 8)
I'm tired of closing down CQM to get a fresh start, not to mention, I have
to reload in the .TPR and re-enter in my Min. and AveBitrate values 8O

Well, you must be busy (developer) and I must be boring you 8)

Keep up the good work,
-vhelp

Not needed. The two temporary files are overwritten on every CQMatic run. I'll add more features, as soon as we're all happy with prediction ;) Yes. No. :mrgreen:

-kwag

Ok, cool.. I didn't realize that !!

Actually, I keep forgeting this one :confused:
..yeah, sorry for being such a pain :crazya:

Theres' just NOT enough time in a day to do all these fun stuff :mnkypile:

Well, keep at it, cause its all fun :lol: 8) :lol:
-vhelp

I little suggestion : when doing Prediction Only, add a line at the end telling "CQ Calculated is : ..." and the value.
Because it's hard to understand that the optimal CQ value to use is the last "Current CQ" seen in the log and not the "Next CQ" that is just after :idea:

Got it ;)

-kwag

Thanks, that has solved the problem. Now CQM/TMPG is predicting the movie.

kwag, one small thing: can you set a tab order for the gui controls of CQM so that one can "jump" from the movie time in minutes field to the avg bitrate field pressing the tab key (I like programs that can be controlled via keyboard without using the mouse)?

Holger

Try "Shift+Tab" to go to Average (from Minutes), and "Tab" to go back to Minutes ;)

-kwag

hi holgerschlegel,

I know how you feel. But, actaully, you can just press: Shift+Tab, and
that will get to AveBitrate field. I don't know how Kwag could have
missed this all these builds, but it most have ben nothing (no trouble) to
him 8O (but to you and I hehe)

-vhelp

Hey,

One thing I found that eliminated these types of issues was to when I start TMPGEnc and choose New Project then load you avs. Sometimes when I chose another .avs without doing this I would get strange results. Now I do this and have not experience the problem..

Just my 2 cents.

Racer99

In the "My-Project.tbr" or in the "CQMatic.tbr"???
I don't get an error message by clicking on Source Range, but the problem is still there! :cry:

OBK!

Hi OBK..

Try this routine, when you're setting up for a new CQM predict process:

--------------
* open tmpg
* click settings
* select video tab (default)
* open your CQ settings, and change back to your default value ie, mine is 50, then [OK]
* select Advance tab
* check [x] Source Range, and double-click it
* click [Cut editing] button
* select "Reset cut editing" and then [OK]
...note, if this doesn't work, then select "Cut currently selected area" and
...click [OK], THEN, re-select "Reset cut editing" and then [OK]
* Now, select the -1, and type in -1, followed by [OK] button
* Next, uncheck [ ] Source Range, and click on [OK] button to accept.
* Now, File/SaveProject.. select your .tpr then, select 'text' Type.tpr, [OK] and save
* close tmpg
* restart (fresh) CQM
* reload your project file
* set your minutes and bitrate (and anything else)
* click predict -- we're prediting here
* click begin button, and you're off.
--------------

Do this for every CQM project, and you'll never have issues again. But, if
you have other issues, I don't have any answers for ya.

-vhelp

Thank you! :wink: I'll try this for every project now! When I have any Problems again, I will post it here! :P

OBK!

No! Same Problem! :x But I'm sure it's not a problem of the .tbr Project-file!
I tried to predict an older .tbr of another movie that worked before, and got the same results! 8O It's a problem of CQMatic or TMPGEnc!

OBK!

Hello all:

I am trying CQmatic with a 74 minutes Disney movie, and the MA script, While I set Q at 60, when CQmatic starts it brings it down to 15, which is way too low. Tmpgenc settings are per instructions. The min and average rates were give by kwags calculator, and I am using 2500 as max bit rate.
It is also taken 22 minutes per prediction cycle. (It used to be anywhere from 8 to 10 minutes)

Any ideas why this is happening?

Totonho03

Edit.- I cancelled the prediction program, the second cycle went from 15
to a CQ_VBR of 7.63, which, if I remember what I have read, is way too low..
Edit 2.- I changed the rate control mode to Constant quality, and now CQmatic begins prediction at 60

Hi again:

Well, it took 2 h and 49 minutes for 7 cycles of prediciton to complete, and the final Q was:
Do not know if this old cartoon is interlaced or Progressive. DVD2avi's screen was not clear here, the screen was rapidly switching between interlaced and progressive, so I used non-interlaced. I also used Force film and tha MA script. Doing some quick calculations, it will take about 14 hours to encode this film in my set up. Do not know how long ffmpeg will take, but it looks like that it is faster than this................

Your comments will be appreciated

Thanks

Totonho03

hy Otto,
i'm(trying to)encode Dalmatians2 and is breaking my head!
in dvd2avi is changing progressive/interlaced and ntsc/film(42% to 92%)
is a mad thing.....
i'm testing
GreedyHMA(1,0,1,0,0,0,0,0)
or
Telecide(1)
to see what's better ..using fieldeinterlace is horrible..show "ghosts"!

and using dvd2svcd i got:
"Hybrid Film activated. IVTC will be applied and will slow down the entire process!"
and the prog put in the script:
telecide()
Decimate(5)
but the result is horrible!

please Phil,Kwag,vmesquita,GFR,....all:
i need big help!
:?

It could be that you can't get a good result no matter what you try.

Create a DVD2AVI project with "No Field Operation" and try a simple script:

MPEG2Source("path\video.d2v")

See if you can find a pattern between the progressive and interlaced frames.

i did the project like your recomendations
mpeg2source("D:\dvd\a1.D2V")
and in vdub got:
720x480, 29,970fps
in tmpgenc:
720x480,29,970fps,interlace.

i need more help Boulder,i'm really lost!
thanks.
:wink:

See what that script produces in VirtualDub. Is there for example two or three frames out of 5 interlaced - that's what I meant with a pattern.

Hi jorel,

If your target is MPEG-2, encode @29.97fps "Interlaced" ( not 3:2 pulldown ).
No need to do anything else.

-kwag

i choose one part with moviments from left to right:
in each 5 frames i got:
2 frames with transitions in the moviments(ghosts with thin lines)....
and 3 frames very clean.

:!:

Well, this looks like a pattern that should be IVTC'd by Telecide() followed by Decimate(). However, if the pattern changes during the film, the result is a poor quality video. As you already tried this, I think it's best to do as the chief (Kwag) says and encode as 29.97fps interlaced :idea:

oh yes Boulder,thanks!
:D
thanks too Kwag, i see your last post now!
:D

ps:
strange,i post "seconds" after Boulder and have a big distance
between mine and your last post Kwag...i didn't see you!
your post: Sat Sep 13, 2003 9:15 pm
my post: Sat Sep 13, 2003 9:25 pm
:?
don't matter,the best was your help my friends....thanks!
:wink:

i'm encoding a sample to test!

:(
believe me, the result is horrible on 2 players in 2 tvs!
i got "strange lines" in the moviments from top to botton...
like this:
_____
___
_
___
______

yes....like this!

and if i try to use telecide(), tmpgenc(avisynth) show the advice:
"telecide:you must specify the order parameter (0=bff, 1=tff).
refer to hte user manual for how to set it properly.
an incorrect setting will result in incorrect decombing."

...and i think:....oh,...right....i know the result will be incorrect!
:roll:
then i read the manual....and the conclusion is:
:arrow: :imstupid: ...this is my best conclusion after read the manual,
i "can't see a thing"!.......
:screwy: :banghead:

now i'm feeling like a the mad woman in dalmatian2:
i want to kill that dogs! :bruce:
:lol:
i see bubbles,balls and risks in everywhere...
maybe i'm worse than that woman,she can't see "risks"!
:rotf: :lol:

more hints?
...please!
:bawl:

jorel,

there's a tutorial included in the new Decomb v5.0 package which will guide you to proper processing. I didn't want to copy-paste the whole document here since it's quite long. However, it's very simple and easy to follow.

Basically, figure out the field order and the guidance.

Try these two scripts:

#Top field first
MPEG2Source("path\clip.d2v")
AssumeTFF().SeparateFields()

and

#Bottom field first
MPEG2Source("path\clip.d2v")
AssumeBFF().SeparateFields()

View both scripts in VDub. Pick up a scene which includes some motion, for example someone moving across the screen. Which one has smoother motion? If it's the first one (probably is), your video is top field first which means you'll set Telecide(order=1). If it's the second one, it will be Telecide(order=0).

For field guidance see the step 2 in the tutorial.

:)
thanks Boulder..i'm trying now:
using:
AssumeTFF().SeparateFields()
i got 59,940fps and the image is in the top to middle of the screen.
the middle of the screen to the botton is black(very dark green)!
8O
using:
AssumeBFF().SeparateFields()
i got.....the same!
8O

:?

Don't mind the fps - see how the motion looks when you play the script in VDub :!:

right Boulder...
AssumeTFF().SeparateFields()
seems better ! no ghosts or lines!
(but the middle to the botton of the screen is green)
:wink:
what i do now?

But is the motion smooth, that's all that matters! You'll need to figure this one by yourself, I can't help you unless I see for myself. That green area does sound odd, though.

If you can figure out the field order, see the tutorial in the Decomb package. The next step is step 2, finding the pattern guidance.

ok!
thanks!
:D

Bouuuuuuuuldeeeeeeer!
:D

seems ok after read and following the advices...using:
Telecide(order=1,guide=1,post=2,vthresh=30)

i encode a sample and the image is great!
no ghosts,no risks,no marching ants and no blur!

details:
stay in 29,97 interlaced(means that i don't have to use pulldown,right?)
if i understand right how it works seems that using
Telecide(1) will give me the same effect like the line:
Telecide(order=1,guide=1,post=2,vthresh=30)
right?
:wink:

Jorel:

Was this work for your cartoon film? If yes, can you post your script?
Thanks snd regards

Otto

yes Otto but see:
is for Dalmatians 2 (hibrid film) with 01:13:47 and got round CQ70...

mpeg2source("D:\dvd\Dalmatas.D2V")

Telecide(order=1,guide=1,post=2,vthresh=30)
#Telecide(1)

Undot()
ASharp(1,1)

BicubicResize(464, 352, 0, 0.6, 4, 0, 712, 480)

#STMedianFilter(8, 32, 0, 0 )
#MergeChroma(blur(1.50))
#MergeLuma(blur(0.1))

#Deen("c3d",1,10,12)
deen("a3d",3,4,1,4) # light cleaning
#deen("a3d",3,6,1,6) # medium cleaning
#deen("a3d",4,9,1,9) # heavy cleaning

DCTFilter(1,1,1,1,1,1,0.5,0)
AddBorders(8, 64, 8, 64)

i'm still doing tests with deen and waiting the final
observations about telecide from Boulder, Kwag or another master!
see details from my source in this thread,they are very important!
:wink:

Yes, that's true. If you don't decimate, don't use pulldown.

No, the defaults are guide=0,post=2,vthresh=35, so if you put Telecide(order=1), it would be the same as Telecide(order=1,guide=0,post=2,vthresh=35).

If your clip is hybrid content, you might want to try this (from the Decomb reference guide) :

This would produce 23.976fps video if I understood it correctly and you would have to use pulldown on it.

However, if the pattern stays the same all the time, with three clean frames and then two interlaced frames, you should use the Telecide options that you figured out and then add Decimate() after that.

to (great friends) Boulder, Kwag, vmesquita, GFR and all
that help me a lot to solve this problem, teach and help me :cluebat:
to understand what is ivtc,hibrid source,interlaced,telecide..etc:

:ole:

it can be easy for you but was too big and great for me!
you change the :lightbulb: to :sun:

the result is perfect!
8)

thank you!
:D :drunkard: