NMM视频技术(旧)

 找回密码
 成为会员
搜索
查看: 8372|回复: 10

[AVS插件] 现在的除躁滤镜都有哪些。。。。

[复制链接]
发表于 2008-4-8 14:54 | 显示全部楼层 |阅读模式
RT。。。除了fluxsmooth和fft3dfilter还有哪些。。。。感觉这两个效果不是很好。。。有专门用于压MV的除躁滤镜么
发表于 2008-4-8 19:11 | 显示全部楼层
可以试试dfftest和TNLMeans
前者速度和效果都还不错,后者是制品最赞的,但是速度简直是慢的和蜗牛一样
 楼主| 发表于 2008-4-8 21:54 | 显示全部楼层
哈..你是漫游酷的..我看到过你
发表于 2008-4-16 08:48 | 显示全部楼层
= = 我觉得TNL和dfftest好像差不多效果 OTL
难道我DVD问题?
发表于 2008-4-17 13:49 | 显示全部楼层
差距还是有的,否则TNL那么慢就没意义了~
发表于 2008-4-20 13:12 | 显示全部楼层
原帖由 lalala 于 2008-4-8 14:54 发表
RT。。。除了fluxsmooth和fft3dfilter还有哪些。。。。感觉这两个效果不是很好。。。有专门用于压MV的除躁滤镜么


估计LZ实在是受不了 FFT3Dfilter的奇慢速度 才问问大家有没有别的什么降噪滤镜吧 虽说质量是最优秀的 去除噪声后 不会留下人造痕迹
至于MV的降噪滤镜 你可试试FFT3DGPU+GrainOptimizer 这样可以 (看上去)保持原有画面的特征(包括噪声特征)实质上是降噪了  如果你使用XIVD编码 可以下降25%的码率
但是 如果源的噪声比较大 最好保证比较充足的码率 把deblocking关闭 这样出来的画面看上去就比较完美了
举个AVS的脚本使用实例

SOURCE=MPEG2Source("C:\VTS_01_1.d2v", cpu=0)
DeNoised=fft3dGPU(SOURCE,sigma=10, bt=4, bw=32, bh=32, ow=16, oh=16)
GrainOptimizer(SOURCE,DeNoised).Crop(56,14,-56,-18)
undot()


GrainOptimizer本质上是只是个 只能去除时间噪声的插件 必须配合 空间降噪插件 才能发挥它真正的威力 而且它可以通过空间降噪插件 得到的画面 自适应的对画面进行降噪 基本上不需要对参数进行调整
使用GrainOptimizer 前请先确认是否安装了 MICROSOFT VISUAL C++ 2005 RUNTIME LIBRARIES 否则无法运行
作者还说这是一个实验性的插件 可能会有问题

[ 本帖最后由 crazyoung 于 2008-4-20 13:22 编辑 ]
发表于 2008-4-20 13:17 | 显示全部楼层
下面是 GrainOptimizer 使用说明
=============================================================
New Filter: GrainOptimizer (2.02 -- Bug fixed with certain temporal denoisers)

--------------------------------------------------------------------------------

>>>GrainOptimizer 2.02<<<

The only temporal-only grain reducer!

Simple summary:

This filter "slows down" the progression of grain over time to vastly decrease the bits required to encode that grain. On a per-frame basis, the filtered clip will look almost exactly the same as the original.

Pros: Huge bitrate drop over unfiltered clip (up to 40-50%+), and often higher image quality due to better bit distribution in encoding. Keeps the grainy look of the original source.

Cons: Temporal grain pattern isn't exactly the same as the original. Not as effective at lowering bitrate as a real, strong denoiser, if used alone. Less effective in very high-motion scenes; doesn't usually have negative effects but doesn't reduce the grain as effectively as in stationary scenes. Requires a powerful denoiser to input the denoised clip, so while fast alone, it isn't as fast in practice.

Full information:

One of the main problems with film grain is it is completely uncorrelated with the grain from the previous frame. This means that in low-detail blocks, such as the background of a frame (usually most of the blocks), the encoder is forced to use intra blocks instead of inter blocks, since the current frame's block is almost completely unrelated to the previous frame's block.

This filter resolves that by removing grain temporally but not spatially, in a manner in which the visual difference between the result and the original is minimal, and not even necessarily a negative difference. Using a combination of heuristics, it decides which areas of the frame should be acted on, and then which blocks should be retained between frames. As far as I have found in my testing, no visual artifacts are created by this technique as long as the proper heuristics are used.

This filter is somewhat motion-adaptive but not motion-compensated, and as a result it is quite fast (real-time on SD footage easily, even though it has no assembly code and is completely unoptimized). However, this also means it is not very effective in moving areas. This isn't really what the filter was meant to do to begin with though: its goal is to deal with background grain eating up bits, and that's what it does.

The end result is a basically "free" bitrate reduction of up to 50% at the same CRF/QP for high-grain sources, assuming that your bitrate is high enough that the encoder actually does attempt to preserve the grain--this is particularly important in x264, known for decimating grain at all but the lowest CRFs. Note that theoretically this filter will work for all encoders, not just x264--the benefits aren't as large in non-H.264 codecs, but both VC-1 and Xvid have shown bitrate drops of nearly 25% in my tests.

Note that you should have at least a few bframes and p4x4 blocks enabled to take full advantage of this filter. If it isn't clear at this point, the GrainOptimizer is intended as a preprocessing algorithm for a video encoder.

Syntax: GrainOptimizer(clip,denoisedclip,blocksize,strength,tdist,minrep)
Colorspaces supported: YV12 only (YUY2 and YV24 are possible in the future, RGB24/32 are not possible without drastically changing the algorithm.)

denoisedclip is the clip used for most of the internal heuristics and as such is very important. The better the denoiser you use, the better results you will get. A strong denoiser is recommended--losing details doesn't matter in this case, what matters is temporal stability. Inspect your denoised output if the filter doesn't seem to be working as well as it should; the denoised clip should have no noticable grain at all for maximum effectiveness. FFT3DGPU with a very high sigma (10+ for strong grain) + TTempSmooth works quite well, though I assume others like RemoveGrain(19) will work well also. Note this clip must be YV12.

blocksize is the size of the block (width/height) used for the block retention algorithm. 4 and 8 are the values currently supported, and 4 is the recommended default.

strength is by default 1 and is a decimal value. Note that as of version 2.0 the strength is automatically determined on a frame-by-frame basis--this number is simply a multiplier for the value determined internally. Don't change it unless the default has problems.

tdist is the maximum temporal distance, in frames, over which a block can remain static for due to the retention algorithm. It is by default 6: higher values will make the grain seem to move "slower", and lower values will make it seem to move "faster". A value as low as 2 will reduce the effectiveness of the filter somewhat but keep the grain's appearance almost exactly the same as the original. Higher values result in slower and slower grain, making it appear more like a static dither.

minrep sets the minimum number of grain replacements per macroblock. This is by default 8--higher values result in fewer blocks acted upon but more efficient action on those that are acted upon. Values cannot be above (256 / Blocksize^2) or below 0. The old behavior of the program, before this option existed, was equivalent to minrep=0.

Recommended: keep it at 8. Perhaps different values might be better with other codecs? Lowering the value will decrease efficiency but might make the result look more grainy.

This filter is experimental--report bugs and cases where it creates problems here, but don't complain about it doing so!

New version 2.02
New version 2.01
Old version 1.2

Version History:

2.02 -- Some temporal denoisers have very overly strong effects at scene changes, which tend to confuse the GrainOptimizer. This has been compensated for in most cases.
2.01 -- Bugs fixed with 2.0.
2.0 -- Rewrote over half the code. It now automatically determines the strength necessary on a frame-by-frame basis, to deal with changing grain patterns. The biggest change is that it requires a denoised clip as a second input, for much more accurate motion detection. Chroma option was removed for code simplicity.
1.2 -- Major improvements. Randomized starting array, resulting in slightly nondeterministic behavior but no "solid" appearance for the first few frames of an encode. A lot of improvements were made to considerably lower the bitrate by optimizing specifically for MPEG-4 ASP/AVC encoding styles and dealing with the residual costs of macroblocks. Additionally quality should be slightly improved, and some quality bugs fixed. New option added. Blocksize can now be 8, but is not recommended (though it should work).
Functional changes: the new version now should decrease bitrate on almost all input sources, including some reduction on already-denoised sources.
1.11 - Minor algorithm updates
1.1 - Major bugfix: GrainOptimizer now works correctly on longer sequences. Chroma heuristic added.
1.02 - Feature improvement: non-mod16 resolutions now supported.
1.01 - Minor bugfix: non-mod16 resolutions now correctly result in an error instead of a crash.
1.0 - Initial Release

--------------------------------------------------------------------------------
Last edited by Dark Shikari : 20th November 2007 at 00:43.
 楼主| 发表于 2008-4-23 07:45 | 显示全部楼层
好的去试试,,,,
发表于 2008-4-23 17:38 | 显示全部楼层
我也很想多了解一些滤镜呢....具体来说我还分不清柔化锐化和降噪有什么区别...
请大家指教指教...
另外请大家能介绍几款处理画面的好滤镜(最好能写上AVS脚本...先谢了)....在下压片总是画面很深沉....色块也很大....
郁闷呐...

[ 本帖最后由 wai5888 于 2008-4-23 17:56 编辑 ]
发表于 2008-4-24 18:51 | 显示全部楼层
降噪滤镜还可以试试FFT3DFilter,效果还行,也是速度慢了点
显卡好的可以试试FFT3DGPU,这个的算法和前者一样,不过是靠GPU来运算,在我的86GT上能实时给DVDRip降噪
发表于 2008-4-24 21:30 | 显示全部楼层
我的X3100用不了FFT3DGPU T_T
话说,我觉得柔化和降噪实际上区别还是很大的。“柔化”字面上看来是一种艺术效果,让画面所有部分无差别地变得模糊、朦胧。而降噪则是有针对性地进行柔化,即仅仅针对画面上的噪声进行柔化,而保持细节和边缘的清晰。目的还是有很大不同的。
目前单纯的柔化滤镜很少,毕竟追求艺术效果的人早就用premiere或者after effects去了。avs里面大多数都应该是降噪。
您需要登录后才可以回帖 登录 | 成为会员

本版积分规则

小黑屋|手机版|NMM视频技术

GMT+8, 2019-10-15 09:24 , Processed in 0.040015 second(s), 14 queries .

Powered by Discuz! X3.4

© 2001-2017 Comsenz Inc.

快速回复 返回顶部 返回列表