SpaceRay
![]() |
I have seen that on most (or all) the filters I have seen it has activated the Antialias 5 samples Edge Only
Is this Antialias activated by default when installing Filter Forge ? Are there any filters that have the presets with the antialias NOT active ? I wonder WHY is this activated ON ALL the filters when perhaps is not ALWAYS needed and this is very important for optimizing the render speed. I think that you should be ABLE TO CHOOSE if you want it activated or not as this it realy matters a lot AND you CAN´T change the Antialias setting as it is included already inside the factory preset of the filter and you can´t modify or update a factory preset Yes, I know that you can turn off the Antialias BEFORE rendering, but while trying different presets you can´t turn it off because each time you click on a new preset it will be changed back to Antialias 5 samples. AND there can be a great difference in rendering time 2000 x 2000 Actual Size Mode Antialias 5 Samples, Edge Only Ambient Occlusion ON 8.53 minutes 2000 x 2000 Actual Size Mode Antialias Off Ambient Occlusion ON 1,50 minutes Test done with Simple Stone filter with intel i7 2600K 3.5 Ghz |
|||||||||
Posted: July 10, 2012 7:51 pm | ||||||||||
Carl
![]() |
I often have it turned off on appropriate filters I submit to the library [ such as Romancing the Gorrilla ] some filters definately don't need it ![]() |
|||||||||
Posted: July 10, 2012 8:19 pm | ||||||||||
SpaceRay
![]() |
Thanks Carl, good to know that you have taken care of turning it off when it was not needed.
|
|||||||||
Posted: July 11, 2012 1:24 am | ||||||||||
SpaceRay
![]() |
The main question here is
Is this Antialias 5 activated by default when installing Filter Forge ? I mean if it it this way, then this is active without you knowing that it is active and this affects much to the speed so you should be able to know that this is active and that not always is needed. |
|||||||||
Posted: July 11, 2012 3:03 am | ||||||||||
Carl
![]() |
yes it's default to 5 when you start building any filter, if you have added any presets and want the filter to have AA turned off, you have to update each preset manually
![]() |
|||||||||
Posted: July 11, 2012 3:28 am | ||||||||||
SpaceRay
![]() |
Thanks Carl for letting me know that FF has AA 5 by default when building any filter, I did not know that and I have seen that this is very important for render speed and perhaps you are hurting much the perfomance of the filter when really the AA may not be needed.
Yes, this is a bad thing, but this is this way, UNLESS you turn it off when you begin making the filter, BUT if you turn it off when you begin you probably do not know if you will need to have AA, because it would be the same afterward, if you make the presets afterward you would to manualy turn the AA ON of every preset manually BUT what is worst of all is that YOU CAN´T MODIFY the AA preset of factory presets |
|||||||||
Posted: July 11, 2012 3:46 am | ||||||||||
Skybase
![]() |
... don't you just mean you want anti-alias settings globally instead of locally?
Meaning you want to be able to just turn off AA overall instead of doing it on a per preset-basis. I'd find that a desirable feature. |
|||||||||
Posted: July 11, 2012 4:04 am | ||||||||||
GMM
Moderator
Posts: 3491 |
Carl is right: AA settings are stored in the filter presets. Filter Forge by itself doesn't have a default AA setting, it uses the value stored in the preset.
On the contrary, Filter Editor does suggest a default setting of 5 AA samples. As only few filter authors care to select the optimum AA value, most filters retain this default setting. |
|||||||||
Posted: July 11, 2012 5:31 am | ||||||||||
SpaceRay
![]() |
YES, exactly, it would be very good to be able to choose and have the option of turning OFF ALL AA overall even overriding the preset inside the filter so it keeps always OFF if you want to. I agree that this is a desirable feature
As said above, it would be good if FF could have a checkbox with a AA default settings 1 - Use preset´s AA (this would be by default as it is now) 2 - Use your own AA configuration (if you put 10 AA would be applied on all presets even it is stored 5 AA on the preset) 3 - Turn off all AA overriding any presets configuration (so you if you want to just test and make some experiments that do not need much quality, you could be able to turn off any AA configuration stored on the presets)
Curious that the 5 AA samples setting is put in the Filter Editor and not in the FF normal use, that I suposse uses for the presets whatever AA setting you have in that moment. I agree with the idea of the default 5 AA Samples to keep the quality of the filter, but I suggest that also when USING this filters presets we could choose to override this settings if we want
Well, I would care If I could new what could be the best and optimum AA value in each filter, and how to choose the best setting in each filter and see if it is not needed or it would need a higher one, knowing that this is very important also for the speed of the filter but also for the quality, so there should be a balance of the two. |
|||||||||
Posted: July 28, 2012 11:00 pm | ||||||||||
SpaceRay
![]() |
In the FF Help you can find this explaining the Anti-Aliasing menu and what each option does but there is not much about how to use this in an optimum way and how to choose the best setting depending on the filter you are making
|
|||||||||
Posted: July 28, 2012 11:04 pm | ||||||||||
Skybase
![]() |
what?
![]() AA is totally up to you, it's a consideration of quality vs time. I mean sure, there is a optimum way of looking for that one AA setting that works with both time and quality but my point is you'll just have to do it manually. Fortunately there are some rules of thumb. When you see Jaggies or "edges that look pixelated" you raise AA one notch. If those wonky pixels go away you can stop and call it "optimal." Here's a example, if your filter has a ton of hard edges densely packing one small area, you'll need to increase AA samples to avoid fuzzy pixels. You can also attempt to solve part of this issue by enabling "Jitter sampling" in your FilterForge Options > Render tab but that doesn't get rid of every problem. ![]() |
|||||||||
Posted: July 29, 2012 2:13 am | ||||||||||
SpaceRay
![]() |
Thanks for your answer Skybase and is useful
You are right Skybase, I think I explained it badly, because as you say well the AA is up to you and depends of what yourself think is optimum and how much quality vs render time you want What I wanted to say above is that on the help page, the antialias are described all the options and settings well, BUT there is no tips, hints or suggestions on what is the best way to configure the settings according to speed and how much would increase the quality vs render speed and how to combine in the best way all the possible setting of AA From your own experiences that FF users may have, I wanted to know what combinations of the 3 settings would work best and is a starting point to work with and combined it with AO if needed ![]() What I was asking is as you say some rules of the thumb you mnay have, or hints and tips. Fortunately there are some rules of thumb or like this useful advice and comment about how AO works Anti-alias and ambient occlusion (bad result) |
|||||||||
Posted: March 2, 2013 4:38 am | ||||||||||
Skybase
![]() |
Here are some "rules"
1. If you get fuzzy edges (see post above) and you don't like them, your samples are too low, bring it up a notch until you don't see fuzzy messy edges in high contrast areas. 2. Edges only is a good measure. It's faster than all pixels since it only applies anti-aliasing where it needs to be. 3. Use diagnostics to see what FilterForge is doing so you get a better sense. There are times when FilterForge will do wonky things. The point of "show diagnostics" is to display the data driving the anti-aliasing. If you don't get what you're looking at and what you should do with it... don't bother with this tip. 4. Default settings are generally good enough for everything. 5 Samples, edges only... preeettyy much the best. I've rarely set my sample count above 17 and rarely use all pixels. 5. If it looks good, so be it. There are "Happy settings" you'll always land on just keep that to yourself. |
|||||||||
Posted: March 2, 2013 6:29 am | ||||||||||
SpaceRay
![]() |
Thanks very much for sharing this useful tips and "rules"
The great problem I have is that FF is in some cases slow or very slow previewing the result to see if it would need more AA or if it would not be needed, as ALL the filters have 5 samples AA, but not always is that really needed. And also the same with AO Will have to test and experiment more with this AA and A0 settings and follow your rules and see what I can do to make a better workflow. Thanks again |
|||||||||
Posted: March 2, 2013 6:40 am | ||||||||||
Skybase
![]() |
You know you can do AA in post? outside of FilterForge?
|
|||||||||
Posted: March 2, 2013 6:48 am |
Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!
33,712 Registered Users
+19 new in 30 days!
153,534 Posts
+31 new in 30 days!
15,348 Topics
+72 new in year!
7 unregistered users.