Page 1 of 1
neat video in virtualdub not previewing correctly after seek
Posted: Mon Mar 03, 2014 5:48 am
by lansing
I'm using virtualdub 1.10.5. I loaded in my 1080 video, added the neat video filter and done remving the grains with it. And back in the preview window, everything is normally as it shows input and output panes. However, after about 6 seeks in the time line, the output pane start showing grains again, not as much as the original.
If I open the filter dialog box and click ok, the output pane preview correctly again.
And if I open the filter dialog box and click cancel, it will add more grain to the output pane. Repeating this will add even more grains, eventually making it identical to the input.
Posted: Mon Mar 03, 2014 12:47 pm
by NVTeam
1.10.5 is a beta version of VD. Could you check if you can reproduce the problem in 1.10.4 (release version)?
Thank you,
Vlad
Posted: Mon Mar 03, 2014 3:28 pm
by lansing
tested 1.10.4, same thing happened. No problem with other filters.
Posted: Mon Mar 03, 2014 3:41 pm
by NVTeam
We cannot reproduce this in 1.10.4 so far. We keep trying.
Vlad
Posted: Mon Mar 03, 2014 4:02 pm
by lansing
Ok I think I know where the problem came from. It's the adaptive filtration option that was causing this. When I turn it off, everything work as normal.
Posted: Mon Mar 03, 2014 4:21 pm
by NVTeam
Thank you, we will check that.
Vlad
Posted: Wed Mar 12, 2014 3:06 pm
by lansing
any update on this issue?
Posted: Wed Mar 12, 2014 3:24 pm
by NVTeam
No, we could not reproduce the problem so far. It is quite likely to be clip-specific.
Does the clip that you process actually require adaptive filtration?
Vlad
Posted: Wed Mar 12, 2014 6:08 pm
by lansing
Well I don't really know what adaptive filtration do, I just leave it on.
And after testing a few more videos, looks like the problem only exist in my dragon ball z level set blu ray clips, where they have huge amount of grains.
Posted: Wed Mar 12, 2014 6:18 pm
by NVTeam
Please check the description of that option in the user guide to make sure you use it correctly. I do not recommend to just enable it everywhere, that is not right. Which is why it is off by default.
Thank you,
Vlad