@jagabo, yes, I figured out that missing-parts business. And thanks for that tip on I/B frames, it makes sense.
@pdr, this is the first I 've heard of that requirement for RemoveSpots(). But since I'm still in the world's earliest stages of learning masktools, I might try figuring that one out....well, I'll give it a try, but something like mt_makediff is the only thing I can think of that might work.
No, wait, why should makediff work, as opposed to something else? OK, I give up.
+ Reply to Thread
Results 31 to 53 of 53
Last edited by jagabo; 24th Feb 2013 at 17:27.
I think you're misunderstanding me. It's not a "requirement"
What I'm saying is all the dirt/spot removal filters will ALWAYS remove important objects to some extent. Things like eyes, shoelaces, beltholes, fingernails, stray hair, etc.... It depends on your tolerance level whether or not it's "acceptable". Just compare (either interleave(a,b) 2 versions , or compare in different tabs in avspmod). They ALWAYS cause damage to some extent.
The masks I'm talking about are semi-manual in a compositing application like AE, Nuke, etc.. There is no way to do this "automatically" in avisynth "perfectly" . Those filters will either miss some spots, or take away important stuff on some frames. The reason is there is no algorithm that can effectively distinguish between what is a "unwanted spot" vs. an important detail to be retained. The way to do this "perfectly" is to composite layers with masks (e.g. you might use strong filter on one layer, weak on another, medium on another) . It's still way faster than the alternative (e.g. photoshop only)
Right, poisondeathray, I've seen the effect with RemoveSpots a number of times and had to use other means in drastic cases. Out of curisoity (again, since I don't know what the heck I'm doing), I tried an experiment with mt_adddiff() in MaskTools2.
In the image below, a section of frame 744. The top image used RemoveSpots(). The bottom image used this code:
In the bottom image it almost looks as if the broken line was restored. But in fact the "break" is filled with a less-black line. And of course the colors are the added difference between the original and the new frame: brights are brighter, darks are darker. Oh, well....I'll understand masktools one of these days.
As it happens, this frame didn't have any unwanted dots.
Now, I have tried to fix the film with some avisynth filters.
Picture from the source on top, and from the filtered film on the bottom:
There are 2 things that I find strange. For the first that the picture from the source is frame 570, while the second picture is frame 572. It's the same clip, the second picture is just from the film loaded with an .avs script.
And for the second, the colour is changed in example nr. 2. Is it Mpeg2Source() which causes the change in colour? The carpet is more red in pic 2. I know it isn't any of the other avisynth plugins, because the change in colour is present even if I remove all the other plugins.
I've used CPU=6 in Mpeg2Source
and I think the result is quite good. The carpet isn't loosing too much details either.
Last edited by jagabo; 26th Feb 2013 at 16:36.
VirtualDub and VirtualDubMod use rec.601 whenever they converts YUV to RGB.
BT.470-2 B,G is the same as rec.601 for our purposes here.
Yes, that is what mine is showing too; BT.470 - 2 B,G*
So that means that the DVD is rec.601
I used "snapshots source frame" (shift-1). In VirtualDubMod.
It is VirtualDubMod which shows the colors wrong here. (Scarf orange).
DGIndex and VLC are both showing what you mean are the right colors (the darker tone).
But when opening the .avs script file in VirtualDubMod, then it shows the right colors. That would be the .avs file without the colormatrix code.
As far as I know, VirtualDub and VirtualDubMod always convert YUV to RGB using the rec.601 matrix. In AviSynth you can specify which matrix you want with ConvertToRGB(matrix="rec601") or ConvertToRGB(matrix="rec709"). If you don't specify which you want you will get rec.601. If the source specifies the colorimetry you should follow it. If the colorimetry isn't specified and you're not sure which to use the general rule is to use rec.601 for standard definition, rec.709 for high definition.
Last edited by jagabo; 26th Feb 2013 at 18:09.
What's that mean? That you first opened the VOB directly in VDubMod and got wrong colors, and then later opened the AVS and got the right colors?
So it seems that it isn't the film which have any wrong color. It's just how VDubMod shows it.
When I use ConvertToRGB(matrix="rec601"), I get right colors in VDubMod. This indicates that rec601 is what the DVD is. And when I use ConvertToRGB(matrix="rec709"), I get the wrong colors in VDubMod.
But when I don't use anything it seems that VDubMod is choosing rec709 by default.
But this is not a big problem, just a strange observation.
What is more important, is to get the right filters to get rid of unwanted artifacts in the film.
Also I'm wondering if anyone knows of a program that can show mp4 frame by frame, the same way that VDubMod does with mpg2.
Last edited by brusno; 27th Feb 2013 at 12:05.
In VirtualDubMod select Options -> Preferences. Go to the Display tab. Disable the Use DirectX for Display Panes option. Exit and restart VirtualDubMod. I think you'll see the colors correctly now. If this is the case, your graphics card is converting the colors using a rec.709 matrix. Do the same in VirtualDub to avoid future confusion.
changing the directX settings as you suggested didn't help. Colors are the same.
If the graphics card used rec.709, then the other programs would be affected by this I think.
I don't know what version of VirtualDubMod you're using but the version I have (188.8.131.52) always uses a rec.601 matrix to convert YUV to RGB or vice versa. Exactly the same as VirtualDub and DgIndex.
hello everyone, i have a similar noise / artifact issue but it is only on video or pictures on line, dvd i play are perfectly good!!!???!!
this is something new, since i changed my modem
comcast said they needed to update system and required a dociss3 modem
[Attachment 17029 - Click to enlarge]
[Attachment 17030 - Click to enlarge]
[Attachment 17031 - Click to enlarge]
I doubt the modem has anything to do with your problem. Right click on a video while it's playing and select Settings. Change the state of the Enable Hardware Acceleration option.
Exit and restart the browser.
Also, update to the latest WHQL certified driver for your graphics card. And the latest Flash player.
Whew, ya'll boys been workin' hard.