Comparison of two 16:9 DV avi files - about 6 secs 20 megs.
Original untreated
http://www.fileden.com/files/2008/3/11/1809238/test.avi
Same file run through Thalen DeShaker.
http://www.fileden.com/files/2008/3/11/1809238/test_deshake_problem.avi
Notice the artifacts very noticeable around the orange "tiles" on the roof and the "Storm Struck" sign.
Any idea how I can get rid of this?
Thanks
Try StreamFab Downloader and download from Netflix, Amazon, Youtube! Or Try DVDFab and copy Blu-rays! or rip iTunes movies!
+ Reply to Thread
Results 1 to 30 of 114
Thread
-
-
Can't get your files.
No free lunch.
Removing camera shake results in artifacts. You are re-processing every pixel.
Next time use a tripod.Recommends: Kiva.org - Loans that change lives.
http://www.kiva.org/about -
Originally Posted by edDV
No free lunch.
Removing camera shake results in artifacts. You are re-processing every pixel.
Next time use a tripod.
So why are the artifacts more noticeable under certain circumstances? It seems they show up primarily around the edges of objects. -
I don't see your files on the page linked.
Recommends: Kiva.org - Loans that change lives.
http://www.kiva.org/about -
Originally Posted by brassplyer
I'm guessing this is not your camera?
Or at least this one?
-
Originally Posted by edDV
-
Originally Posted by hech54
The question wasn't "why doesn't my $200 Handycam produce images like high-end pro gear" but what if anything can be done about artifacts with a particular Virtualdub filter. -
Are you talking about the comb artifacts?
That's normal for interlaced video. Note that Windows DV decoder will normally perform a simple BOB deinterlace when playing DV so you will see jagged, buzzing edges instead of comb artifacts. If you're going to make a DVD leave the video interlaced.
Be sure to use DeShaker in interlaced mode. -
Originally Posted by jagabo
It's harder to point out with individual frames since it appears more prominently when the video is in motion, but compare for example the long right diagonal edge of the blue roof at frame 1869 between the two. See how much less distinct that edge looks? Look at that same place with the files in motion. Also notice the sign in the background.
You don't see what I'm talking about? I've got the deshaking set very mildly, so it's not just because you lose resolution due to the "zoom" imposed by the filter, there's very little frame lost in this example. -
You have to keep in mind that each frame contains two half images. Each of those half images is missing the other half of the image. The deshaking can't work as well with that and you get more aliasing artifacts, ie, buzzing edges.
It might work better if you bob deinterlace first. That will turn each field into a full frame. Deshaking that may work a little better. You can the take the output from the deshake, split it into fields and weave them back together. Here's a VirtualDub filter chain that works:
Using a better deinterlacer like AviSynth's TempGaussMC_beta1() should give even better results:
Code:import("C:\Program Files\AviSynth 2.5\plugins\TempGaussMC_beta1.avs") AVISource("test.avi") ConvertToYV12(interlaced=true) TempGaussMC_beta1() SeparateFields() SelectEvery(4,0,3) Weave()
-
TempGaussMC_beta1() requires a bunch of other filters. You'll have to download and install them all if you want to try it out. See the docs for details.
-
On that Vdub filter chain, how are you doing it? Are you leaving all filters active during the initial pass with the Deshaker or turning them off on first pass? Are you hitting the output button or using the "run analysis pass" command?
You say you used the "default" DeShaker settings, but that specifies square pixels, progressive scan and the wrong dimension for DV avi. Can you clarify?
I tried it and just got different artifacts. -
Because TGMC is so slow, it would be prudent to encode to a lossless intermediate first, to avoid heavy processing on multiple passes
So:
AVISource("file.avi")
TempGaussMC_Beta1()
Encode that to a lossless format e.g. huffyuv, lagarith, UT
Then re-import that lossless AVI into vdub and use deshaker.
Vdub and avisynth assume square pixel, but the frame size should be the same. It's your export format that specifies different PAR setting (setting an aspect ratio flag that tells the player to "stretch" the pixels upon playback)
What is your final format goal? If it's some progressive format e.g. for PC or internet distribution, there is no need to re-interlace it -
With the VDub filter chain I set up all the filters, including Deshaker set to Pass 1, then ran File -> Run Video Analysis Pass. Then I changed Deshaker to Pass 2 and ran File -> Save As AVI.
Yes, setting Deshaker to Anamorphic NTSC should help. But after deinterlacing the video is progressive, so you should leave Deshaker set to progressive. -
Originally Posted by jagabo
Screenshots
-
What DV decoder are you using? I wonder if it might be putting out YV12 which VirtualDub will screw up. Try forcing VirtualDub's to use its internal DV decoder.
And as noted before, you will never get rid of those buzzing edges completely. -
The simple answer is, your cam is to blame. This is an old issue, having to do with the way dv cams record 16:9 widescreen, cropping/resizing incorrectly, etc. My Canon ZR10 had similar bad function like this. I found that the only way around it was to shot 4:3 and crop it, and fake 16:9 through croping as long as the viewers didn't know this little trick, its a mute point. I'll let someone else explain that issue.
But there's also another issue I see with your sample dv clip. It looks like it was processed. Since you didn't say you did anything to it, I'll assume that your cam is also to blame. The image looks like it was filtered, the evidense seems to point to some temporal algorithm in your dv cam. In another dv cam I own, it seems to produce very similar results like your clip. Hard to explain, but almost chisely like..the pixels. Very similar indeed. I blamed that on my cam, too.
May try an experiment in your house. Shoot footage in both 4:3 and 16:9 modes, and run them through the same paces, then review. Post them (untouched) up here if you like.
Use avisynth for the best 16:9 setup, but try and stay away from other filtering because in the long run it'll just get worse, and just encode to your desired format, mpeg-2 or whatever. Your cam already did several levels of damage. So leave everything else alone, set your encoder to 16:9 and use as high a bitrate the standard calls for in your destination format. For mpeg-2, I topped at 9 MBits. If you skimp bitrate because you want to fit on a cd you'll see the results later on when you least expect to. That's been my experience, and is why I mostly go with high bitrates in such circumstance.
-vhelp 5305 -
Since "YUY2 disable" isn't checked you're probably getting YUY2 in VirtualDub. Unfortunately, VirtualDub doesn't seem to report the colorspace it negotiated with the DV decoder. But try using VirtualDub's internal DV decoder anyway:
Options -> Preferences -> AVI -> Prefer Internal Video Decoders... -
Originally Posted by jagabo
I'll have to try the 4:3 - 16:9 comparison and see what happens. That would suck to find my 16:9 video won't respond well to this filter under any circumstances. -
My DV encoder can't set the 16:9 flag but here's what I get with the earlier VirtualDub filter chain:
http://kotuha.com/file/HxjVA-deshake.html
When I was examining your samples earlier I was looking only at BOB'd output on the screen. But I zoomed into the actual source and see a worse problem. Your deshaken output has corrupted the two fields. There are no longer distinct comb artifacts everywhere where they should be. Here's a 2x zoom from your deshaken (left) output vs mine (right):
Mine looks like the source. Yours had corrupted the two fields. Did you do some other filtering? -
I couldn't reproduce your issues with the same filters, but I'm using a different DV decoder and encoder, cedocida.
If you export a lossless format, like huffyuv or lagarith, do you see the corruption? If not, then it suggests the encoder is at fault. If it still is corrupted, then it suggests the decoder or your filters are at fault
Your mainconcept dialog box is old, you might be using an outdated version, it might be corrupting your video somewhere along the line (either decode or encode). I have a newer mainconcept DV encoder (directshow, not vfw) , and it worked normally as well on a lossless export from vdub
It wouldn't hurt to try cedocida, since it's free. You can use vcswap to temporarily disable your mainconcept vfw dv configuration -
Originally Posted by jagabo
-a minute later-
I just triedconverting your file to 16:9, it results in what appears to be the same artifacts as I'm getting originally.
I also notice that media info isn't reporting the Mainconcept DV codec anywhere on my DV files, it's saying Sony. -
Originally Posted by poisondeathray
I'll give this and your other suggestions a try. -
Originally Posted by brassplyer
Originally Posted by brassplyer
Originally Posted by brassplyer -
Originally Posted by brassplyer
Similar Threads
-
VirtualDub/Deshaker trouble
By she-ra in forum Newbie / General discussionsReplies: 2Last Post: 10th Oct 2012, 09:12 -
Virtualdub with Deshaker problem
By snafubaby in forum Newbie / General discussionsReplies: 4Last Post: 20th Aug 2011, 10:39 -
Problem when using Deshaker Virtualdub filter
By snafubaby in forum Newbie / General discussionsReplies: 1Last Post: 4th Jul 2011, 01:41 -
Vdub Thalen Deshaker Gets To Certain Point And Stops
By brassplyer in forum EditingReplies: 0Last Post: 31st Dec 2009, 08:12 -
VirtualDub + Deshaker weird diagonal line
By z4ce in forum Newbie / General discussionsReplies: 4Last Post: 30th May 2008, 11:30