Calcumatic audio setting
I am trying cqmatic and calcumatic again and am wondering which audio setting I am supposed to use in the calcumatic application. Am I to put in the setting for my target file or am I to put in the source audio bitrate. If source audio bitrate is what the input is supposed to be, then what do I put when ithe source is 5.1 channel ac3? Would it be better to just encode the audio first then use it in my project and not worry about it?
|
You put the target bitrate there. How else could the application calculate the target bitrate for video? :wink:
By the way, the number of channels in the track doesn't determine the bitrate in any way. |
ok. I also am wondering why it will not raise and lower the bitrate for video. I just ran a test run on the Final Cut and it was set for 80 minute cd in calcumatic. the result was: it just kept the bitrate I gave it and raised the cq level from 80 to 89.73. the movie was going to encode (again) to around 600 mb. I have to raise the bitrate up to 700 min and 3000 max and raise cq to 100 to get around 750 at least with this film. "I know from experience dude"(in my best chris farley voice).
|
Post your script and settings.
Calcumatic will only calculate the average bitrate for the video based on the values you feed in it. The average bitrate will remain the same whether the movie compresses extremely well or very badly. It's just a simple calculator, CQMatic is the one doing the predicting etc. |
ok here goes. I don't use a script. I use only tmpgenc. I am using 352x240 ntsc plus template for kvcd. I have it set for 352x240 reolution. I have video arrange method set for center (custom) 352x144 for this particular film. I have bitrate set for the film at min 700 and max at 3000 i have cq set for 100% I also have inverse telecine set. I am 36% done with my encode and my file is 265mb. With this I can predict pretty closely that my final size will be very close to 736 mb if I continue with the encode as is. I would have to raise the bitrate higher to get any more out of it. I would like to be able to get all my encodes up to 812 mb. I have had to suffice with getting them between 700-812 without gettin into re-encoding many times. Usually I will get to 10 percent and get a pretty good guess as to what the final size will be and then judge from there what to set my bitrate and cq at to get within the 700-812 area. I have gotten pretty good at that but i was hoping cqmatic and calcumatic would be able to get me closer. It looks like a big NO to that though.
|
I would also like to find a reason for using a script. I have found no reason to frameserve at all and would like to learn more about it so maybe i can understand the reasoning. I have been able to get great picture and sound and size of picture with only the tools that tmpgenc has to offer. I have been able to load every movie source I can think of at it and it encodes beautifully. Is it more colorful or clearer thatn what I am getting? I would like to see a difference so I can judge for myself whether it is worth it to switch over to avisynth. Does the encoding process take less time? I am encoding movies with an average of 1 1/2 -2 hours for 90 minute movie. Is that longer than with avisynth?
|
Quote:
Using CQ=100 just produce a bigger filesize than CQ=90 with no real enhancement in the quality. For this reason, CQMatic do not predict above CQ=90. You should use a bigger resolution for that movie, you will have a lot better result AND you will fit your 800 MB. |
I know that calcumatic is not the one doing the predicting. I was trying to find out why cqmatic would not raise and lower bitrate to when that is needed to reach a final size of 800 mb. It only takes the bitrate that you have already put in tmpgenc and tries to get a cq value that works for it. It happens to not work for this film I am trying. The bitrate needs to be raised in tmpgenc to higher level. hell, cqmatic gave it a cq level of 89.73 when i had it set to min 500 and max 2500 bitrate. which was only bringing the final size up to around 600 mb.
|
thanx phil I will try a higher resolution.
|
Quote:
With Avisynth scripts you can also denoise the video, DVDs are usually not very clean. |
|
Quote:
Quote:
The purpose is not to fit 800 MB, the purpose it to have the best quality and stay under 800 MB. Here the best quality is obtained with 600. There is no better quality than 'best" one :) |
Quote:
Phil, I caught on to what you said after I already made that post you mentioned. Hence, me saying I would try a higher resolution. Karl, I have no idea what any of that stuff means. all that stuff hit me in the face and knocked me off my already partly broken, piece of crap, chair. Linear, STMedian, radius, temporal filter...etc. Man I guess I need to do a lot more reading on this stuff. It is all greek to me and I don't know any greek. |
Of course the program can resize, I didn't say that. I say that the program uses some extra crappy resizing method like "nearest neighbour", and using that for going from 720x480 to 320x240 is not a good idea. You're much better off with Lanczos, it will result in a sharper and more detailed result.
|
Quote:
|
Quote:
- a instruction to load the source (it can be avi or or DVD, but you have to use a intermediate step for that - DVD2AVI). - some lines for the resize - some lines (optional) for filtering The script is used as source in tmpgenc, and it will call avisynth by itself. Don't worry about how this works, finally thi s is not important. Quote:
Quote:
http://www.avisynth.org/index.php?page=YourFirstScript |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.