Quote:
100% Agree with CQ being better. I never go below 544x576 (and i don't use blockbuster) so i can't comment on the other resolutions. Have you tried CQ with any TV captures? I find using CQ at High quality motion search gives far better results than CQ_VBR at MUCH smaller file sizes. The Encodes are absolutley perfect! I was ready to give up on tv captures whilst using CQ_VBR. Jim |
Quote:
|
Quote:
-kwag |
Quote:
-kwag |
@ Sansgrip
Edit: Forgot to say, it's at the same URL as before :). Btw, I also got rid of the version parameter.[/quote] i can't download the _test.zip........"says" file not found. :( |
@Kwag,
Kwag wrote: Quote:
using motion estimate search fast. I want to try a clip using your settings (e.g. dither, CQ, motion search, etc.) Some are having good results and some poor. Maybe Tmpgenc, as SansGrip suggests, could be responding differently when CQ reaches certain levels. All of these fixes are to fix shortcomings of Tmpgenc's encoder or any encoder. There has to be some common settings to get predicted results. I don't believe were not there yet :? -black prince |
Hi black prince,
You're right!. I think we're not done yet 8) I'm using Blockbuster(method="dither", variance=.4, seed=1) for 528x480 with CQ, fast motion estimation, and the new BETA-1 matrix. I'm also using MIN=300 and MAX=2,500. Here's my script: Code:
LoadPlugin("C:\encoding\MPEG2DEC.dll") But I do use TMPEG to get my borders size and film pixel area. It just looks "cleaner" around the edges that Vdub when closing in. I get the same values with both procedures. Edit: I'm still doing some comparisons between "dither" and "noise" :!: -kwag |
@Kwag,
You forgot your CQ setting. It's important because a higher CQ, say 70+ could be when Tmpgenc reacts to Blockbuster dither. Below 70 it might be ignoring dither. :) -black prince |
Quote:
Dither IS working at that value. At least at 528x480. -kwag |
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
If it uses its own home-grown motion estimation algorithm I would not trust it. If I knew for sure it used either of the abovementioned algorithms then I would be much more inclined to use it. Until I know what algorithm it uses, I'd rather stick to a thorough full search, as provided by the other (non-estimation) settings. |
Quote:
thanks! :wink: |
Quote:
|
Quote:
|
Quote:
Edit: And what were the spoilage settings in the CQ tests? |
Quote:
# --- AVS Script Created by AVSMaker --- # AviSource("D:\Captures\MSMurders\capture_1.00.avi" ) + AviSource("D:\Captures\MSMurders\capture_1.01.avi" ) + AviSource("D:\Captures\MSMurders\capture_1.02.avi" ) + AviSource("D:\Captures\MSMurders\capture_1.03.avi" ) Trim(1114,31165) ++ Trim(37463,55052) ++ Trim(61352,80395) ++ Trim(86662,113947) ++ Trim(120219,143573) ++ Trim(149852,180242) #Trimmed Frames make new movie LoadPlugin("C:\Program Files\DVD2SVCD\MPEG2Dec\MPEG2DEC2.dll") Fluxsmooth(15,15) TemporalSmoother(2,2) # --- End of AVS Script Created by AVSMaker --- # By combining Fluxsmooth with temporalsmoother with these parameters, I find that all the noise is gone and the encode looks nice and sharp on the TV. By setting the CQ to around 72 ish and using B picture spoilage as 20, I can get an Hour of Full Screen TV capture at 544x576 on one CD, although at that lower quality you can see the odd artifact here and there. If the TV Cap is widescreen I set the CQ to 80-85 and then I can get 1 hour per CD at fantastic quality! Jim P.S - If you are wondering what the AVSMaker nonsense is in the above script, for some time now i've been writing a program called AVSMaker which is designed primarily for TV Captures because i hated using virtualdub. It allows you to load in multiple AVI files and offers a fill GUI to delete adverts and use any of AVISynths functions like tweak etc. It even includes frame previews using your filters like virtualdub does. I haven't finished it for 2 reasons. 1) All the goalposts for resizing and cropping etc using AVISynth seemed to be changing by the hour! and 2) My wife keeps getting me to do things around the house! |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.