Evening "brickwalls :banghead: hitters" (you guys)
I've ben after this fact for the longest of times (eons) and in many areas of concirn.. ..to develop a consistant "testing platform" for new developing ideas like CQM !! Too many peoles have too many variables / differences in their setups and processes and so on and so forth. Somthing "generic" has to be implemented, or else things will get more involved, issue'wise :!: I'll spare you all my regimin, and assume someone already has a working flow plan ? Anyways, I agree that we need something like this for these kinds of testings, AND to minimize the countless headaches that could plague us all (mostly the developer) in achieving a goal. Are you Matic, cause I'm Matic (jellen) anyways.. -vhelp |
vhelp,one my opinion:
first we need one reference, after everybody got perfect results with the same progs,scripts,etc,... we can try some variables or this work will be so hard! then after this perfect "reference", the "generic" will be easy with some little changes! see that if the same dvd movie is ntsc or pal, give differents results. :) |
@ Jorel..
Quote:
Preferebly, a movie that everyone has.. then we can MAP out the issues as well as the success (pros and cons) EDIT: - - this way, you build a "template" or "gauge" to use in future testings.. :idea: -vhelp |
Well, I finished my test with the same movie. This is going to be a pain :!:
Look at the results: I encoded "Red Planet" with this script and CQM 1.1.02: Code:
## DLL Section ## First test: 352x480 MIN=523.83 MAX=2,000 CQ found: 80.25 Encoded file size: 834,313KB Second test: 352x480 MIN=300 MAX =2,500 CQ found: 74 Encoded file size: 643,633KB Both CQ values are incorrect :!: The wanted file size by Moviestacker is 726,338KB Now that is what I call a problem :!: Look at the difference in file sizes, just from CQ 74 to ~80 8O Here's my CQMatic log, with MIN=300, MAX=2,500: Code:
http://www.kvcd.net Here's the same .avs processed with ToK using MIN=523.83 and MAX=2,000: Code:
============================================================= Code:
------------------------------------------------------------- In both cases, ToK predicted almost the same CQ, but by looking at the CQMatic log, a CQ of ~80 with MIN=523.83 and MAX=2,000 we know that the file will be over 100MB in size :!: So at 79.093 it will still be way over. Then, probably with the same CQ, but MIN=300, MAX=2,500 it will be smaller. So here we have it. Complete different results, by just a change in MIN and MAX, throws off file size in the range on hundreds of megabytes :!: Now, I really believe that an alternate prediction method should be investigated, because the sampling method used in ToK, acp and CQMatic obviously doesn't work every time with TMPEG, and we've been lucky every time we hit a correct target. That's what I think. -kwag |
Hi kwag..
If I can jump in here for a moment.. member how you favored so well, AVS v2.08 ?? Does that STILL apply today, or R U saying that this version was wrong all along too ?? :roll: Cause, if you're not saing so, then perhaps it's just an AVS v2.52 issue as I've theorised all along. Ok, so you've testd AVS v2.52 w/ CQM.. HOW ABOUT TESTING AVS v2.08 w/ CQM (at least w/ prediction only) to get an idea of what's what ?? At least try the above out, and see, so that you don't go pulling your hair out over an NEW prediction method. bye for now.. -vhelp |
@ Kwag..
Hay, I can't believe I'm actually quoating myself, for the first time.. anyways.. Quote:
w/ EXACT same script you used in above test w/ same params and things !! -vhelp |
Quote:
I'm going to do an encode of "Red Planet", but directly from the .d2v project, bypassing AviSynth completely. Thanks for bringing this up :) -kwag |
@ Kwag..
Quote:
yes.. excellent !! great movie too, and I have on DVD :) ..note, I'm only trying to help, if I can - no matter how small :roll: And, you're welcomed :flip: -vhelp |
Don't know if this is relevant or not but I had some problems with the July 17 version of AviSynth 2.52. I went back to the previous version and all is well again.
|
Hi everyone.
@ Kwag.. I think I may have a "possible" cause of the issues w/ prediction havoc :!: The answer may lie in viewing what happens to shorter-length clips ie, 1 VOB encodes or ~25 min. ( ie, movie, "Matrix" ) predicitions. I won't say what happens, because I think you may jump the gun, and claim it's something else or my debug in flawed :roll: But, I must say, I did notice something, that I think might shed some light, on the matter - maybe. But, I'll have to run some more tests. I'm heading on to "Get Karter" cause I also did that one in 1 VOB format (21 minutes) Below are my "process" params.. follow it to the letter, to obtain the same results as mine. But, first, here is the LOG file, followed by the process: Only you will/might know what the issue(s) are after viewing/trying out the test for your self, since you are the developer of CQM :wink: Please let me know what you think about this (after you've performed the test(s) yourself) - K ?? Thanks for your attention, -vhelp . . Quote:
Quote:
|
Hi vhelp,
You entered 136 minutes for a ~25 minute VOB :!: That's why CQMatic gave you a CQ of 90. You must enter the correct time in CQMatic, as it is used to calculate the size of the sample needed for the real target. -kwag |
Hi Kwag..
Quote:
In any case, I'm off to try "Get Karter".. just to see the results, to see if I get the same experience I got w/ "Matrix" In any event, I'll also try YOUR suggest w/ BOTH these movies afterwards :!: Question: * given the above, and your response to my movie lenth (136min) what or how should I count-balance w/ respect to BITRATE.. assuming I want to fill a CDR ie, 800mb w/ a 25 minute (Like I'm gonna do that, but you never know) ... for BITRATE distribution, how should I "balance" it ?? * also, to minimize the amount of time spending on testing your CQM and predition debuggin, how should I set the bitrate (if it needs to be) and the time required, if I have ie, 25 minute VOB I want to test predictions with, rater than waiting 55 minutes for prediction tests, maybe cutting it down to something like, 5 to 10 minutes ?? Pretty lame questins, but can you give anything for each for them ?? Thanks for the assist and all, -vhelp |
Quote:
Because 25 minutes even at CQ=90, won't fill a CD-R ( with MIN=300, MAX=2,500 ) :!: CQMatic will always calculate a CQ of 90. 25 minutes is just too short, so even at CQ=100 and a resolution of 704x480, you won't fill a CD-R. Maybe, just maybe at 704x480 you get slightly under 90, but I don't think so, unless you set your audio to 224Kbps and MAX=4,000 :idea: :roll: -kwag |
@ Kwag..
w/ respect to below, ok.. thanks.. I understand now.. and, it makes LOTS of sense 8O dah.. One more thing.. about CQM, could you add in an option somewhere's (even during copy to clipboard dialog box) a feature to CLEAR the contents of the LOG, so that I can restart another predict test, w/out having to shut it down, and start it up again w/ an empty window (minues your (c) .. ) ?? Thanks again, and testing "Get Karter" w/ CQMatic-1.1.02.exe anyways.. -vhelp . . Quote:
|
Quote:
-kwag |
Hi Kwag..
Quote:
I'm going to use the single VOB's time length.. ie, 21 minutes for the movie "Get Karter" in this next (doing now) I'm trying to cut down on the length of time it takes to test, in hopes that the test will still hold up to "prediction" debuggin. If it does, great!! But, if it does not, ..oh well, we'll have to live w/ the longer debuggin time :) and use the full-length of movie, for testing/debuggin for ya :) Sorry about the premature hype earlier. But, it did get up hehe 8) -vhelp |
Kwag..
Just wanted to let you know, that CQMatic-1.1.03.exe did a better job at finding a CQ value (for the 21 min test clip) - - gave me 50.17 in 22 minutes time vs. 55 minutes in previous testing of full-length movies. I hope that it does't matter what length we use (shorter in my case) for the prediction testings because of this. Please le me (us all) know if this does taint the prediction process. The way I read it, CQ 50.17 will fit my whole movie of "Get Karter" w/ 103 min. onto one 800mb CDR !! (if I read/understood that correctly) ..yes ?? Listen, if using shorter length movie test clips is proved to be no valid for CQM testing/debuggin, then WHY NOT USE IT ?? Will take less time to work out the issues, not to mention, less headache :roll: There's a bonus to useing shorter length test clips though :wink: I'm off to give "Matrix" another go, but this time w/ 25 minutes.. Below, is my "Get Karter" LOG and Process, using only a 21 minute test VOB (via psuedo .avi for source) w/ latest CQMatic-1.1.03.exe: -vhelp . . ----------------------------------------- Quote:
Quote:
|
That looks good :)
Now everyone come in, and join the fun ( or the disaster :mrgreen: ) http://www.kvcd.net/CQMatic-1.1.03.exe -kwag |
hi Kwag..
I got a stupid question to ask.. Is there any way to get TMPG's old encoding back, so that I can encode JUST THE AUDIO portion of that last test sample I did ?? I haven't done anything to TMPG yet. I just want to change it to Audio Only and then I'd like to MUX them (aud/vid) to one file. I want to fix the glitch that's causing it to studdre in Windvd. Powerdvd plays it fine, but for those that play it in windvd would not benefit from it otherwise. Is there anything that I can do (regarding above) after finishing a CQM test, just to get the audio portion of the SAME and last encode from CQM ?? Hope you understood that. Thanks, -vhelp |
Select "Prediction Only" in CQMatic. When the process is finished, run TMPEG. You'll have the last CQ already set. Just clear your range, select "System (Audio+Video") and add your audio in the "Audio Source" of TMPEG.
Now you can encode full Video + Audio. -kwag |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.