Recording Video: Capturing interlaced + filters
Hi,
I began to do captures, and I am wanting to codify interlaced, for that I am using the script: Code:
captura="capture1_huffyuv.avi" I am capturing with huffyuv in 704x480 -> YUY2 (my capture card is a bt878). I wanted to know a GOOD script to remove noises among other parameters to improve the image and compression. I will pass for KDVD. All of the parameters to codify interlaced they are right? Thanks. |
Can you tell us where you find these "JDL_*" fonctions ?
|
@ Phil
http://www.avisynth.org/stickboy/ ;-) @ Ginoboy Unfolding/folding fields does make ONLY sense when filtering interlaced inputs! So if you do NOT put any filters between these Xfoldfields commands, they are useless. |
For some tips, see http://www.kvcd.net/forum/viewtopic.php?t=13768 .
|
Hi, i'm back.. Thank's for reaply's
please, verify for me: Quote:
it seems to have been.. somebody recommends good filters to me for VHS capture of average quality (average for good)? thanks! |
Your script looks OK to me, for some more filtering try this:
Code:
AviSource("captura_vhs (2004-11-07 at 13-50-59).avi",false) You might also want to check if the chroma is shifted, which it probably is because you have a VHS capture. http://www.doom9.org/capture/chroma_artefacts.html |
These days I encountered a VERY big Problem with the Remove series!
I treated "Fahrenheit 9/11" as capture for a mpeg2 encoding. It was broadcasted as a fieldblended conversion directly from a telecined 29.97 state to 25.000 PAL. I could have used Restore24() but for me actually fieldblended restorings to progressive via restore24() is actually no more an issue as Its ok if these kind of catures do fit on one CD in a extreme good quality. And as we do encode to mpeg2 for TV Purposes, a interlaced keeped encoding is ok for me. Now the problem: These Remove... Filters do mess up when interlaced stuff is delivered! Do check a station Logo, ... I tried a lot of changes in the script but it doesnt helped. Did you also encountered such Problems?? BTW: In the script above I wouldn't do the bobber using Kerneldeint() as you only perform an anti noise treatment. For that denoising routines you should ONLY use a "stupid" bob. As that bob() doesnt enhance captured artifacts like noise etc. So a.... bob() DenoiseingFiltersHere() separatefields().selectevery(4,0,3).weave() # 4,1,2 for F'order change KernelBob(...) ResizingFiltersHere() separatefields().selectevery(4,1,2).weave() # or 4,0,3 for F'order change ;-) |
Hi Inc,
Wouldn't it be better to change: ResizingFiltersHere() separatefields().selectevery(4,1,2).weave() # or 4,0,3 for F'order change To: separatefields().selectevery(4,1,2).weave() # or 4,0,3 for F'order change ResizingFiltersHere() At the end ot the script :?: -kwag |
No, because the material is reinterlaced..and resizing an interlaced video is a no-no :wink:
I use KernelBob because it keeps more details. A stupid bob bobs everything whereas a smart bob leaves the non-combed parts intact and treats them as if they were progressive. You might want to ask Scharfi about detailed explanations as he's tested these things a lot. A softer bob would be TMCBob() or KernelBob with sharp=false parameter. I have used only RemoveGrain lately with mode=1 or 2, fed with smartbobbed video but I haven't noticed anything strange. I'll have to check that tomorrow, I've got one capture clip to be processed. Actually someone said that Bob() is lossless only if b=0, that is Bob(0,x). The defaults are Bob(1/3,1/3). That might be worth remembering :idea: |
Quote:
The screen letters are getting mixed up :lol: -kwag |
Quote:
http://www.digitalfaq.com/archives/error.gif it observes the red shirt, these pink risks would be "chroma's shifted" ? I tested some filters cited in link, but I did not perceive difference.... what it would be this? @ Inc about: http://www.vmesquita.com/forum/index.php?topic=66.15 for NTSC, pixelview bt878 (driver's btwincap WDM) and huffyuv codec, the correct resolution to capture would be 704x480? thank's all.... |
Quote:
But Scharfi at Gleitz.de explained me/us that in case of a denoising a stupid bobber like bob() does it better as ... bob().separatefields().selectevery(4,0,3).weave() is a NOP ;-) And denoising in an untouched condition would be the best. Resizing is another issue where a smart bobber is shurely a better choice, thats why I "quoted" that 2 bibbing-example from gleitz.de. Quote:
Like that gauss() function from MugFunky, as he downscales with that the iage to a quarter of it size and rescales it using a special kernel in bicubicresize so the blurring gots a very good quality one. Thats also why there some ones have been asked for a medianBlur() function as Avisynth actually gots no high actig gaussian blur function, only that blur(1.58) or unfilter(-100,-100) or asharp with negative values used. @ Ginboy Where did you got these cropping/bordering parameters??? Code:
crop(8,0,696,480) At least you should process borders at MOD16. |
Hi Inc,
I captured in 704x480... Code:
crop(8,0,696,480) then he was 696x480... Code:
addborders(12,0,12,0) and... Code:
letterbox(12,12,0,0) :arrow: Final resolution = 720x480, no resize and a good overscan. :wink: thank you very much! |
these may help, whatever you can do in Vdub can probably be done with avisynth.
http://www.doom9.org/index.html?/cap...artefacts.html http://www.doom9.org/index.html?/cap...sing_vdub.html |
@ Ginoboy
Leave the 704x480 finally at 704x480 as its a d1 cropped compatible DVD format, NO need to force a 720 encoding afterwards of captured sources - no sense! So Avisource("Your704x480capture.avi") Letterbox(16,16,16,16) Does it all you need, means overlaying MOD16 based 16px all around for getting rid of border garbage and beside this applying the 16px around overscan area. |
Quote:
-kwag |
In deed Karl
Quote:
Well only one "block" doesnt make that much sense (maybe a bit) as meg encoding at main level is done in 4:2:0 and there the chroma is half the resolution of luma (in both directions) and so you have to choose a 2blocks Overscan, so 16px each side as 16 devided by half chroma is 8 and thats the gain :D EDIT!: Ahhh, you mean a resized overscan! Yep shurely in case of captures incl. black horiz. borders like 1.85:1 ones you will gain from even more compression - right! |
Hi,interesting things to read here,
Boulder wrote: Code:
and resizing an interlaced video is a no-no will mess up the interlaced structure I read somewhere in this forum. Then I guess we can say the same about cropping,only do that in deinterlaced mode :?: If yes I may have understood something :lol: So I made a test encoding yesterday with a stupid-bob before de-noiseing and a smart-bob before resizing: Code:
LoadPlugin("C:\programfiler\AviSynth 2.5\plugins\kerneldeint.dll") bob values:bob(0,0) Is this the way to do it lossless :?: Another question,I bought some hollywood-movies on VHS, is it the same with this as with DVD,that 99% is framebased(progressive) film :?: I captured one of them("Trinity Is Still My Name" :roll: ),and could not see any combing effects at all. thanks ----------------------- viking |
Quote:
Quote:
Quote:
|
Boulder wrote:
Code:
You can crop interlaced video, there's just a couple of things to remember. See the Avisynth docs' Crop section for them. Code:
In order to preserve the data structure of the different colorspaces, the following mods should be used. You will not get an error message if they are not obeyed, but it may create strange artifacts. For a complete discussion on this, see DataStorageInAviSynth width and height in FitCD and the result will be correct. But if I bob() the same video like the in the script of my last reply, AviSynth threats it framebased(progressive),then I will need mod 2 for width and I have no restriction for height,right :?: thanks ----------------- viking |
@ Boulder
yes, the same kernel params of Bob(x,x) are used like in BicubicXXX(x,x). But it would be interesting if someone enlightens me in these maths of those two values used in Bicubic to determine the interpolation! :) As there are no explicit infos at the avisynth page. Also I would like to know how to set rigth a convolution matrix in GeneralConvolution() as IF you/me would get some skills of these convolution-matrix then that filter gots VERY useful as so many nice things could be done (masking/blurring/swapping/shifting/sharpening) with that. Avisynth Docs do point on this explanation regarding to Convolution matrixes: http://www.gamedev.net/reference/pro...proc/page2.asp *wow*!! @ Viking If u use FitCD, KEEP IN MIND to crop at MOD2 in a BOBBED! (temprarely de-weaved to full fieldrate) state and resize to MOD 16. As by this the YV12 stream is temporarely not in an interlaced state. |
Those b and c values are really a mystery..I also wonder why soft bicubic a=b=1/3 has been visually most pleasing in the test the docs mention. One probably has to dig up some research papers if he's to find out the real information. Everyone seems to have copied the same sentence about blurring and ringing constants :wink:
|
I wanted to define a definitive pattern for me to capture, therefore I have many VHS here, and I am looking for the best configuration before converting all, then it would like an opinion, for me to reach a final conclusion...
then, considering that I have a capture card Prolink PixelView PlayTV Pro (bt878), using BTWinCap WDM v5.8 opensource driver, Huffyuv v2.1.1 CCE SP-Patch v0.2.5 codec ( Click here to see the configuration, please ), YUY2 colour format, VirtualVCR 2.69 software to capture, 29.970 FPS (reminding that I live in the Brazil, and the system here is NTSC(PAL_M)), VHS source (signal Video Composite (RCA)). Then, the best resolution (and correct, of course) and definitive for me to capture (and is the destiny dvd) is it 704x480, correct? the script to codify interlaced correctly, is: Quote:
(in case I will codify a musical show, i change "kenelbob order" to 0 and selectevery to 4,0,3 ? ) if I will capture to transform for XviD later (to leave FS and to look in PC) would I capture in which resolution? which the best script for deinterlace ? thank you very much for all :wink: |
Quote:
Quote:
Also remember to convert the colorspace before reinterlacing (put the convert line before the SeparateFields() line). Quote:
What comes to capture resolutions, I'm afraid I can't help you there. I capture happily with my non-scaling PVR-250 at 720x576 and do ITU compliant resizing. You should also make sure that the source is truly interlaced and not telecined. If it's telecined, you can IVTC it and encode at 23.976fps as progressive. |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.