KVCD: Cropping in TMPGEnc method
Working with a 720x480 PVR250 16:9 capture to encode with KVCDx3 as 480x480 SVCD. In TMPGEnc clip, the left and right borders are not very good. I'm trying to crop the left 6 pixels and right 13 pixels.
In TMPGEnc, when I clip out the bad borders and clip the top and bottom, I have the following: 701x348 Left 6 Right 13 Top 63 Bottom 69 When I open MovieStacker, I see: Film pixel: 720x480 0 left border 0 top border :?: Should I change to 701x348 6 left border 63 top border? BicubicResize(480, 366, 0, 0.6, 14, 63, 684, 348) AddBorders(0, 57, 0, 57) LetterBox(16, 16, 16, 16) :) Thanks in advance. |
Hi Nick,
just to avoid misunderstandings you cant capture analog in 16:9, ju just got a Letterboxed 4:3 (so a 16:9 look with black borders added). Now your question. First you do it the right way by finding the cropping values via TmpgEnc. So note them (left value, top value, and image value). - Enter Moviestacker - Choose your source and determine it as DVD (as captured mpeg full size) - In "Film Pixel" enter your image values (701x348) - In "Left Border" enter your left value und in "Top Border" your top value - Choose in Cropping "Accurate" and round to 8 - In "Resize" choose round to 16! - In "Destination" choose your Target - Now go to the "Avisynth Script" Tab and choose under "Resize" MACROBLOCK Align! These round to and Align Values do preserve that the whole image architecture will be mod 16 based! So you obtain a full macroblock optimated Image archticture which gives even better compression when encoding afterwards. Edit: Btw. you know that when entering Moviestackers options tab and there the avisynth version tab... you can uncheck this Avisynth Version detection just to avoid this everytime boring AVS detection error message when starting Moviestacker on an avs 2.5x configurated system. |
:D Thanks, Incredible.
|
Quote:
Or how do you think I got the exact values above? I took them from your first post where you figured out them by using TmpgEncs Clip option. :) Yep, the PVR 250 does really good captures. I wanted to get one this spring, but as I know now that that one got audioproblems, ... Ill still stay with my DC30 which gots the ame quality but uses its onborad mjpeg hardware codec = larger Filesizes. :wink: |
Quote:
How about capturing the audio at the highest bitrate you can, and then using HeadAC3he to re-encode the audio :?: Have you tried that :idea: -kwag |
Did you search in the www for reports about that?
Maybe the cards onboard sound digitizer gots a bug? My DC30 i.e. only delivers the mjpeg video which is directly muxed with MainboardAudio device Sound input. Cause the DC30 i.e. gots such a bug at the right audio channel. A noob won't hear this but there have ben some oscilloscope tests around the web which proof this. Almost 80% of all consumer TV/Video capture cards got a not that good quality audio divice. BTW Nick, you should never! use the same compression as the one u use when reencoding .. in here the 128kbit! This is also a problem when doing reencodings from Dvix/Xvid to KVCD or an amount of KVCDs to one KDVD. Always give the bitrate in its source state room to "breath". Or do reencode using a higher bitrate just to keep the quality. |
Quote:
|
So does this cropping method only apply to Captured material? Or is it a good idea to use it on DVD sources too?
|
Quote:
|
Ok, but it is normal that I get different resize values for DVD sources when I use this cropping method right? :roll:
So it can't be bad to use this, even IF the edges are clean right? |
Quote:
|
Quote:
almost 20% of my orig DVDs got bad edges on the sides. Example: "Das Boot" :arrow: very light stuttering right edge So if you use that resized overscanning in Gripfit you'll see the bad edges if they do exist. The best is to watch the edges in the preview of DVD2AVI to determine whats the best to do. @ Jell I do all my encodings (no matter if Capts. or DVDs) crop manually before (figuring out that using VDubs resizer or the method above). If you do it right!, the right AR will be delivered to FitCD or Moviestacker when typing in the cropped image resolution as explained above. And by doing a mod16 Resizing/BorderAdding you will end up perfect. BTW you can decide if doing an resized or an overlapped Overscan (in case of 2.35:1 I always choose overlapped overscanning. But that all Im doing because I do only trust in classic resizings ;-) If you trust in GripFit it also gots mod16 internal routines. So that's a philosophy and you decide for yourself. |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.