Hi.last night before i went to bed i tried to let cqmatic do a an encode for me and here are the results
MOvie-ice age.avi Average bitrate-1240 length- 81 minutes Optimal 2.52 script kvcd3-528x480 woke up this morning and the encode was at cq 90 and the file size was 899 mb. :!: This was the first beta release Did i do something wrong or what THanx |
Kwag,
Used yesterday's beta (pre-1.0) on a cartoon for the kids. Length was 71min, avg bitrate was 1414. Used 2000 MAX and 0.57*1414 for min bitrate in tmpgenc (you need to announce that setting in the 'optimal scripts' section... I didn't know about it until this thread began!). OH, and used the optimal script with the GOP of 15 as recommended for cartoons. Anyway, CQ predicted 77.87. Final CD length after muxing with audio: 80min 07sec. Requires a 3sec overburn ;) Talk about accurate prediction! |
Okay kwag... I think I've just found a bug... (It is not the codec!!!!)
My AVI film has 23.976 fps but I encode it as a PAL (like I always do!), that means I have a 352x576 resolution... => it doesn't work (CQMatic doesn't search a correct CQ -> it starts with encoding the film!) The same AVI film, but now I changed the fps to 25.000! I encode the film as a PAL (352x576) and it works! No problems!!!! Perhaps you can stop that with a message in CQMatic or something.... Greetz fn86 |
Quote:
movie-length: 72 min |
Quote:
What you set in TMPEG, is what CQMatic will see :) -kwag |
Quote:
www.kvcd.net/cqmatic-1.0b5.exe -kwag |
Quote:
This prog is the missing link. It's just getting easier and easier. I don't think anyone believes you when you say that you "sleep" Kwag. :lol: Cheers J |
Quote:
Quote:
-kwag |
Quote:
-kwag |
so how do u find out the average bitrate?
|
Quote:
|
I thought it was .75*avg bitrate or is it .57*avg bit rate?
|
0.57*average bitrate. :wink:
|
@Kwag,
CQmatic is doing a great job predicting video filesize, but I wonder about MovieStacker's audio filesize prediction. I tested the latest CQmatic on "Pitch Black", movie time = 108 min, KVCDx3 (528x480), average bitrate = 884, 1 cd (80 min), CQ = 63.47. The encoded video filesize is 690mb and audio filesize 100mb (estimated by MovieStacker). Headac3he estimated audio filesize at 89mb. There is a difference of 11mb in audio sizes. Is there a way to adjust MovieStacker's audio estimates to match Headca3he's :?: Audio was 112 kbs. Video prediction was very accurate and audio sounds awesome. Video + Audio = 781mb. Picture quality is great (DVD like). :D -bp |
CQMatic 1.0 Release Candidate 1!
http://www.kvcd.net/cqmatic-1.0RC1.exe Changes: Fixed: No more looping trying to find CQ :!: Now you can see the "zeroing in" on target after each pass, which should hit the target much faster than BETA 7 (the last beta of 1.0 branch) So when you see the CQ difference = 0.X, where X = under 0.25, you know you're close to the end of the prediction prediction ;) Added: Now you can double click anywhere on the Log window, and you'll get a message: "Clear contents of Clipboard, and Copy Log to Clipboard? Yes/No So you know what to do ;) Now the only thing left before the 1.0 Release, is probably fine tunning the final prediction. And here's a log of two test movies I just did (prediction only), to verify correct CQ exit point of CQ: Code:
-kwag |
When doing the settings in tmpeg, what do we use for the min and max bitrates, or do we leave those alone.
David |
Quote:
MIX = 0.57 * Average Bitrate You get the average bitratee from Moviestacker (or any other bitrate calculator) -kwag |
Ok just like we are doing in Tok. I was using the avg bitrate from moviestacker as the min, thats why I couldnt get a descent CQ :imstupid:
David |
I did a prediction again on ice age(avi) again and am having the same problem
here is the log Quote:
whats going on Edit-just ran the same avs through Tok and it gave me this Quote:
|
Quote:
Let me try an avi here, and see if I can reproduce your problem :!: I did a 57 minute (.d2v) and it predicted correctly without errors, but I haven't tried an avi. And I do see something strange there in your log, that it jumped to 90 initially, but then I see a 76.42 there in the end, so It should have predicted again at around that value, and not lock and encode at 90. I'll take a look at that now. Let me scratch my hard drive and see if I can find an avi :roll: If not, I'll encode one :!: -kwag |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.