KVCD: Does CQ value effect the encoding time?
I was just wondering does the cq value affect the length of the outputted length of the file or file size?? I used the KVCD-CQ-352x576-_PAL_-PLUS template and the film length was 115 mins and the template is 120mins high quality template, I chose 70 as the CQ level, and the outputted m1v was 736mb, how high can I go with the cq level????
|
CQ affects filesize. Use ToK to predict the correct CQ value to fill the space available! :wink:
|
I don't really think so. I've noticed encode time actually go down when CQ is raised. Maybe that's just me.... :D
|
ok, just muxed the audio and vid through tmpgenc as bbmpeg closed itself when I tried to add audio or video via the way described in redm's guide, I now have a overall file size mpg of near 900mb :cry: I used the following code with the template stated in my original post and cq set to 70.
Code:
LoadPlugin("C:\fitcd\MPEG2DEC.dll") |
hmm....I think your muxed file shoulda came out around 851MB. You're not using TMPG 2.59 are you?(it's buggy, so you shouldn't be). Also, you hafta mux kvcd's as Video-CD (non-standard) in TMPG. Maybe you muxed as standard video-cd by mistake? Although even 851MB is too large to burn to one 80min disc, so you'll still hafta split it onto 2 discs or use a 90 or 99min cdr (trimming opening and ending credits off the movie might make it fit too...bbmpeg is handy for exactly that kind of situation).
There's supposed to be a workaround to make bbmpeg work if you experience that problem you described where it closes itself. Do you run Windblows XP, and if so did you install the XP-patched .dll for bbmpeg? That might fix it for you. But if it doesn't, then you can also just click on the "Load" button and then the "Cancel" button on the main screen before clicking on the "Start Encoding" button...this should allow you to continue on and mux with bbmpeg without it closing on you. BBmpeg really is a better muxer than TMPG, so it would be best if you could get that program working for you. Good luck, :) -d&c |
the file size in windows explorer it sadi 851 but in nero it had 891mb. I didn't know anything about a xp pathed dll file, where can I get it?
|
see this thread for a link to the xp-patched .dll for bbmpeg: http://www.kvcd.net/forum/viewtopic.php?t=3272 .
You unticked the "create standard-compliant" vcd setting box in Nero right? -d&c |
of cause I had unticked it. and cheers for the link.
|
well just done a successfull mux in bbmpeg only prob is I now have 2 mpg files, one 795mb and the other 68.5mb, I think the problem is when I encoded the video, maybe the cq is set too high, but if i have it set at 60 the quality becomes blocky, is it the script that makes the m1v so big? anyone suggest a better one?
|
Hey, glad you got bbmpeg working. 8) Just make sure to use the right settings when you mux your file though. If it came out to 851MB when TMPG muxed your audio and video together, then it should probably be about the same muxed with bbmpeg. There is a thread somewhere in the bbmpeg forum that shows a screenshot of the correct settings to use. I think all you need to do is select VCD, tick VBR, and set Forced Mux Rate to 0.
It sounds like maybe your file came out too big because you didn't use filesize prediction? If you didn't, you really need to use filesize prediction (either with Tok, or the manual way with a calculator), so that your file will turn out to be the right size to fit on your disc at the best quality possible. Otherwise, you're just going to have to play a game of hit-and-miss and keep re-encoding your movies many times with different CQ levels until you finally get lucky and find the correct CQ value to fill up or fit onto your disc. This is not a fun way to do things...it's like throwing darts with your eyes closed until you hit the bullseye. :lol: If you did use Filesize Prediction and your file still came out too big...well, this just happens sometimes...rare, but it happens (the prediction method used here is not a perfect science, but darn close :wink: ). Fear not...you still might be able to fit that movie onto one disc. What audio quality did you use? 128kbps, 112kbps, 160, etc??? Try using 112kbps audio if you didn't already...this will save you some space and still sound very good(if created with Headac3he)...I wouldn't drop to 96kbps unless you really have to and don't feel like re-encoding your video. Also use the "Start second" and "End second" settings in bbmpeg to trim off as much of the beginning and end credits of your movie that you can. By doing this, you might be able to trim enough megabytes off of your file so that you could fit it onto 1 disc. Also, if your burner supports overburning, you can usually overburn as much as 825MB onto an 80-minute disc (depending on what brand you're using, and how good they are...Fuji cdr's are usually very reliable for overburning up to 825mb). I'm affraid that's all the advice I've got for you. Hopefully, you won't have to re-encode your movie. As for your question about the script, Kwag's latest Optimal Script works great!...is that the one you used? I'm putting 2-hour movies onto 1 disc and they look great on my standard 30-inch tv (and I even have to encode @ 29.97fps instead of 23.976fps like in the kvcd templates!...so I have even less bitrate to spare than most people around here). Using the Optimal Script, I've found that I can use a CQ as low as about 54 and it still looks very good to me on my tv....but quality is subjective. You can try using some of the commented-out filters that are listed in kwag's optimal script if you're really desperate for more space, but more filters usually means less quality, so I'd avoid it if/when possible. Cheers, :drink: -d&c |
no I never used file predicition as last time when I tried it it just went totally wrong and I tried tok and got lost with it, the audio is 128 and the script I used is mentioned above this one. I will give the new kwag script a go and see what happens.
Edit: tmpgenc says STMedianFilter.dll is not a valid avisynth 1.0 plugin. I have version 2.08 installed. |
Quote:
-d&c |
I'm suppose to put the filters in the avisynth plugin folder? I've had them all in the a seperate folder with fitcd program.
|
ok the little bugger that is avisynth now says mpeg2dec is not a valid 2.5 filter.
|
Quote:
Quote:
-d&c |
I'm using 2.51 of avisynth, anyone know where I can get a newer version of mpeg2dec that works with 2.5?
|
I'm using 2.51 of avisynth, anyone know where I can get a newer version of mpeg2dec that works with 2.5?
|
Riddle me this:
You said you .m1v file was 736mb and you .mp2 audio file was 105. Basic math tells me that it should add to 841mb. I'm not sure what multiplexing the two files add to the total size of the file. That means you are only 10 mb off. The thing you have to do to get the file smaller is to re-mux the audio to a lower bitrate or re-encode. What was your bitrate for your audio to achieve the 105mb file? You also mentioned that you chose 70 as your CQ. Now realize that without CQ predicition you cannot just choose a CQ value and expect it to meet your needs of time / filesize. How did you determine the CQ value? RACER99 |
I loaded the d2v file in tok it said best cq was 60, I done a sample file and it produced a kinda fuzzy sample file, so I just upped it by 10 didn't think it would matter :roll: shows me don't it. I encoded audio to 128kp/s.
|
Quote:
If for some reason you'd still prefer to use 2.5x, then I think you need to use mpeg2dec3, not mpeg2dec or mpeg2dec2. There's links at www.avisynth.org for nearly everything avisynth-related you'd ever need (aside from maybe a few filters that are scattered here and there). Quote:
-d&c |
I tried mpeg2dec 1,2 and 3 and got the messsage not a valid 2.5 filter, no I didn't burn the m1v file off to cd didn't think when I saw the quality. I tried using kwags latest script but it comes up saying unfilter is not a valid 1.0 filter.
|
Quote:
http://www.kvcd.net/forum/viewtopic....3c32b6faf06339 and... maybe we have to wait a few days cos avisynth 2.51 is beta and got some problems using this version. :( |
cheers jorel, downloaded it and it works fine with 2.08 managed to get it going.
|
after thousands tests:
a hint for filters, size, CQ and time to encode: 1- every filter that you put in the script(how many) 2- more resize(352x240/288, more than this..etc) 3- more CQ will got more time to encode.ever! (the order of the filters in the script change the final time and size) :!: |
Code:
LoadPlugin("C:\fitcd\MPEG2DEC.dll") |
:wink:
it's ok! a question: do you really need spacedust in the script to encode this movie?...is not from a dvd source? ....i think that you can remove this line: SpaceDust() # Optional - for some "not so clean" DVDs or use #SpaceDust() # Optional - for some "not so clean" DVDs and your encode will be faster. :!: |
it is a dvd source, I'm doing a copy for a mate I only put spacedust in to try and get rid of the fuzzyness oin the picture.
|
Personally, I would probably try not to use both STMedianFilter AND SpaceDust because, at least to me, it just smoothes the picture a bit too much using both of them (making it blurry). Also, Kwag recently dropped STMedianFilter from his recommended Optimal Script because some people were saying they thought it decreased the visual quality too much. In my opinion however, I think it should be left there and used by people only when necessary (on longer movies or when you need to raise your CQ level a bit more). Using ANY kind of filters usually diminishes the quality to some degree...but it's the price you hafta pay sometimes to fit a long movie onto one disc.
Again, this is only my opinion, but to me the best usage of kwag's optimal script (for clean dvd sources) would be something like this (keep in mind that with the unfilter over-sharpening and subsequent mergeluma/chroma blurring methods used by kwag's current script, you can get away with using a pretty low CQ level, possibly in the range of mid-to-high-50's in my experience, and it should still look pretty good on standard TVs, because the noise looks more natural than it used to in his older recommended scripts that used lots of filtering): Code:
mpeg2source("C:\movie.d2v") Anyways, hope you find something useful in all of that. You can always give it a try and see if you agree or not :wink: . Let us all know how everything works out for ya now that you're using prediction and have figured out your avisynth woes and are well on your way! :) -d&c p.s. if your friend's dvd player will handle the x3 template resolution, you should try to use that one..it will look much better than 352x576. It will give you the best compromise between picture quality and the amount of minutes you can fit onto one disc. |
again i wrote dazed&confused:
you're not confused or dazed my friend! :lol: you're correct here too: "(keep in mind that with the unfilter over-sharpening and subsequent mergeluma/chroma blurring methods used by kwag's current script, ......" and: "Using ANY kind of filters usually diminishes the quality to some degree..." great observations. :!: |
the script there is kwags latest script from the script section, I just activated spacedust to try and sort the fuzz out
|
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.