View Full Version : Suggest a Fast Anti-aliasing Filter
MajorX
18th September 2010, 01:52
Aliasing is big problem in my encoding..so anyone can suggest a fast Anti-aliasing Filter. Recently one of my friend told me to use an Anti-aliasing Filter named as AAA() but it is too slow ..for example it took 8hrs to encode a only 25min of video(720*480) with low settings.
cabac=1 / ref=5 / deblock=1:2:1 / analyse=0x3:0x133 / me=umh / subme=8 / psy=1 / psy_rd=0.40:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=6 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / constrained_intra=0 / bframes=5 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=250 / rc=2pass / mbtree=1 / bitrate=280 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / aq=2:0.60
My system:
Core 2 Duo@2Ghz
2GB Ram
Windox XP SP3
:confused:
Sharktooth
18th September 2010, 14:20
those are not low settings... however if your source comes from a videogame you better enable AA from your videocard drivers.
MajorX
18th September 2010, 21:51
i have no video cards(inbuilt card). I test with these settings with a 25min video(720*480, anime) without AAA() it done in 1.30hrs but with AAA() it took 8hrs with same video.I use this script
Import("C:\Program Files\megui\tools\avisynth_plugin\AAA.avs")
Loadplugin("C:\Program Files\megui\tools\avisynth_plugin\UnFilter.dll")
Loadplugin("C:\Program Files\megui\tools\avisynth_plugin\MaskTools.dll")
AAA()
Usedocne
18th September 2010, 23:29
i have no video cards(inbuilt card). I test with these settings with a 25min video(720*480, anime) without AAA() it done in 1.30hrs but with AAA() it took 8hrs with same video.I use this script
Import("C:\Program Files\megui\tools\avisynth_plugin\AAA.avs")
Loadplugin("C:\Program Files\megui\tools\avisynth_plugin\UnFilter.dll")
Loadplugin("C:\Program Files\megui\tools\avisynth_plugin\MaskTools.dll")
AAA()
Of course its going to take 8hrs. Your filtering and encoding to x264 at the same time. If your going to use Avisynth then you might want to encode your filtered video to a lossless format (HuffYUV) first. Then you can encode your lossless file to x264, saving you a helluva lot of time.
burfadel
19th September 2010, 00:08
You state that aliasing is a big problem in your video, first of all I think you need to find out why aliasing is a problem. What are you trying to encode, and at what resolution? Has the resolution been changed from the source? is the source material interlaced or progressive? if the source is interlaced and you are using a deinterlacing filter, which one are you using and what settings?
If your current settings are correct, and you want to anti-alias just 'flat' anime content, tisophote can be a good choice http://web.missouri.edu/~kes25c/ there are links to a before and after pic there, see if that is the effect you are looking for.
But like I said, don't use that until the other things (deinterlacing etc) are sorted!
Dracaena
19th September 2010, 16:02
Of course its going to take 8hrs. Your filtering and encoding to x264 at the same time. If your going to use Avisynth then you might want to encode your filtered video to a lossless format (HuffYUV) first. Then you can encode your lossless file to x264, saving you a helluva lot of time.
At the risk of going OT, out of curiosity, how would that save time?
Usedocne
19th September 2010, 17:30
At the risk of going OT, out of curiosity, how would that save time?
By filtering and exporting to a lossless format first, the cpu usage goes mostly to the filters, instead of to encoding (x264) and filtering at the same time, causing a kind of "bottle neck" (lack of a better name). Also if you encode in 2pass mode, the filters are being used twice, once for 1st pass, once for second, slowing the whole process down considerably.
Assassinator
20th September 2010, 02:08
By filtering and exporting to a lossless format first, the cpu usage goes mostly to the filters, instead of to encoding (x264) and filtering at the same time, causing a kind of "bottle neck" (lack of a better name).
This bit makes no sense. If the filtering is going to bottleneck the encoding, that is, CPU usage not at 100%, splitting it off will only make CPU usage even lower. Then you'll have to do the actual encoding after that finishes, making the whole thing take longer.
Also if you encode in 2pass mode, the filters are being used twice, once for 1st pass, once for second, slowing the whole process down considerably.
This on the other hand, is very true.
The main reasons why people use lossless intermediates is either for multipass encoding (to save on filtering multiple times) or to section their filtering into multiple stages (sometimes that's useful).
Usedocne
20th September 2010, 15:34
This bit makes no sense. If the filtering is going to bottleneck the encoding, that is, CPU usage not at 100%, splitting it off will only make CPU usage even lower. Then you'll have to do the actual encoding after that finishes, making the whole thing take longer.
It doesn't seem to make too much sense to me either, but after testing (multiple times), it seems to hold true.
1000 frames (720x480i)
Avisynth-TGMC >> HuffYUV(2m.45s) >> x264-CRF(1m.08s) Total time: 3m.53s
Avisynth-TGMC >> x264-CRF(4m.39s) Total time: 4m.39s
Test it yourself, if you don't believe me.
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.