![]() |
Is this guide going to be translated?
Totonho03 |
kwag:
This is just an update. I used CQmatic to predict another film, and this is the result: Quote:
Thanks Totonho03 |
CQMatic suspended until further notice :!:
Please don't waste time testing, as the current results are completely unpredictable on some movies. I'm re-designing the complete prediction algorithm, and until I get at least a ~2% final file size difference on every encode I test, I won't post another version. All versions on the site have been deleted. Thanks, -kwag |
Kwag,
Quote:
I am making 2 disk KDVD 720x480's for miniDVD's. I use vcalc set at 1000, not 1024 and 1400 disk size. I set file size as 698 in BBMPEG to have room for chapters in TMPGEnc Author. I've attached one log and avs used: http://www.kvcd.net CQMatic Version 1.04 Release. Copyright Softronex Corporation, 2003. All rights reserved. Time: 18:13:17 Date: 08/01/2003 Ready! Project: H:\sol\sol.tpr Creating: CQMatic.tpr H:\sol\sol.m2v Execute. Movie Time: 99 Average Bitrate: 1709 Full Encode mode Executing Prediction Phase... Process started at 18:13:39 On 08/01/2003 Entering CF phase. Using CQ of 50.00 FAST source analysis... Process time: 0.85 minutes. Encoder end. Correction Factor = 1.2545 Exit CF phase. Using CQ of 70.00 Encoder started... Process time: 13.02 minutes. Encoder end. File size difference = 1.236973 Last CQ = 70.00 Current CQ = 78.29 CQ difference = 8.294052 Using CQ of 78.29 Encoder started... Process time: 12.78 minutes. Encoder end. File size difference = 1.092968 Last CQ = 78.29 Current CQ = 85.57 CQ difference = 7.278839 Using CQ of 85.57 Encoder started... Process time: 12.80 minutes. Encoder end. File size difference = 0.902651 Last CQ = 85.57 Current CQ = 81.93 CQ difference = 3.639420 Using CQ of 81.93 Encoder started... Process time: 12.72 minutes. Encoder end. Encoding set to Full encode. Full encode start... CQMatic complete! Total minutes of process: 52.18 Process ended at 19:05:50 On 08/01/2003 LoadPlugin("c:\video\dlls\MPEG2DEC.dll") LoadPlugin("c:\video\dlls\sampler.dll") LoadPlugin("c:\video\dlls\decomblegacy.dll") LoadPlugin("c:\video\dlls\dustv5.dll") LoadPlugin("c:\video\dlls\legalclip.dll") LoadPlugin("c:\video\dlls\unfilter.dll") LoadPlugin("c:\video\dlls\fluxsmooth.dll") LoadPlugin("c:\video\dlls\GripFit_preview.dll") LoadPlugin("c:\video\dlls\STMedianFilter.dll") MPEG2Source("d:\sol\sol.d2v") telecide() decimate() LegalClip() unfilter(50,50) GripCrop( 720,480 ) GripSize(resizer="BicubicResize") STMedianFilter(8, 32, 0, 0, 8, 32) # SpaceDust() # Optional - for some "not so clean" DVDs. temporalsmoother(1,2) mergechroma(blur(1.50)) mergeluma(blur(0.1)) # Convolution3d or DCTFilter for extreme worse cases. GripBorders() LetterBox(16, 16, 16, 16) LegalClip() #Sampler(length=24) ##MPEG size = ((Total frames/MovieTimeInMinutes)/24) * MPEG sample file size ## MP2 size: 92,406 M2V size: 1,240,594 Temp00.mpg 713,622 Temp01.mpg 678,552 Close enough for me. |
@ nicksteel,
Boy, I'm glad that "something" is working well in VCALC -- pfew!! Oh, I finally figured out where I saw the 1000 vs. 1024 being used, and why I added it as an option! vcdhelp's java calculator. Has the option, but it doesn't quite explain each use - oh well. http://www.dvdrhelp.com/calc.htm: Quote:
@ nick, you might very well be the only person meeting w/ success w/ VCALC !! (and still going through some more changes/revisions, as I write this) Continued success to ya, -vhelp |
Vhelp, if you add more options, a preferences file would be most appreciated. For example, I always use 1024 and 1400. I'll let you know how usage works out in the future.
|
Hi nick,
Thanks, but please, can you suggest that in my thread instead, so not to taint this one ?? Thanks, -vhelp |
hi nick..
I made a post in the vcalc thread, your question.. -vhelp |
|
Quote:
|
Quote:
I use MAX of 2,000 and MIN of (0.57 * Average). -kwag |
Quote:
|
Quote:
-kwag |
Hi J-Wo..
I think Kwag uses MS in his projects (even tests) and most of his calculations and things are based "off" of MS's. But, as you and others here have demostrated, other calculators can (and do) work in a given scenario.. thanks in part to the "variables" of one's projects ie, source, source quality, users methods and filtering techniques etc etc and the list goes on. I'm speaking from my own personal view - - after reading Kwag's many articles, its not hard to deduce what he uses in tools :) and 8) Its all ---> C8)8)L -vhelp |
Hello Kwag:
This is the result of the latest CQmatic run. Quote:
Regards Totonho03 |
Here's my results for a 91 min movie, avg bitrate 1078 (from moviestacker). Script used was your MA from July 8, 528x480
Wanted file size: 728,194,990 bytes (from moviestacker) Encoded file size: 749,221,556 bytes (2.89% over) Vcalc reports an avg bitrate of 1008 (that's using 1024k and no MS precision), so I'll see in the morning if that gives me a more accurate file size. Oh BTW kwag, I'm positively elated how much faster 1.1.0 is at prediction cycles!!! :lol: |
Quote:
Still not within my wanted ~2%, but close :twisted: Quote:
It should now stay that way :cool: -kwag |
~ one hour to go.
Here's the prediction: Code:
http://www.kvcd.net |
Quote:
Ok, your movie is only 23 minutes long. Why such low average :?: Are you encoding multiple segments on a single CD-R :?: -kwag |
Quote:
|
Site design, images and content © 2002-2026 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2026 Jelsoft Enterprises Ltd.