Crapadilla
![]() |
I might be missing something obvious here, but it seems I can't get SIMPLE filters to output alpha maps that are anything else but completely white. Naturally, I use Set Alpha to assign the alpha channel, but the alpha map only renders as expected if I turn the filter into a SURFACE filter. Interestingly though, the diffuse maps are correctly premultiplied by the alpha set with the Set Alpha component.
So I tried some simple filters with transparency from the library, and they exhibit the same problem. Coffee Stain obviously has an alpha that is premultiplied into the diffuse map, but the Alpha Map is white when rendered via Render Maps. Same thing with OilFlame. Take a SURFACE filter with transparency, like Solar, and the Alpha Map renders correctly. Then I tried saving to alpha supporting image formats like TGA and TIF to see if that could be of any help. Coffee Stain saves with a completely white alpha, OilFlame too, and so does Solar, which should have a correct alpha! So it seems FF correctly premultiplies a filter with transparency over any image you have currently loaded, but discards the alpha?!? --- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|||||
Posted: November 2, 2006 8:51 am | ||||||
Vladimir Golovin
Administrator |
Here are my results -- to render them, I created an image (File > New) with a completely transparent background. The PNG and TGA ones look correct -- the PNG has correct transparency and the TGA has the correct alpha channel. The TIFF looks weird -- probably, this has to do with the RGB channels of that transparent color I used as a background.
Anyway, I'll forward this to the programmers, they'll look into it. ![]() |
|||||
Posted: November 2, 2006 10:37 am | ||||||
Vladimir Golovin
Administrator |
||||||
Posted: November 2, 2006 10:40 am | ||||||
Crapadilla
![]() |
When using FF from within Photoshop, it works as expected. Filters come in premultiplied by their alpha and get properly comped over whatever resides in the layer.
However, when using FF standalone and looking at Filter > Render Maps > Alpha Map, I get the results described above: The Alpha Map turns out completely white for SIMPLE filters. And File > New Image doesnt help that either, I tested that. Furthermore, as described, alphas are apparently not saved out when using File > Save Image As, regardless of filter type (I tested TGA, TIF and PNG so far). Might be a local thing with my machine/install only, but I doubt it. --- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|||||
Posted: November 2, 2006 10:54 am | ||||||
Vladimir Golovin
Administrator |
All these formats handle alpha/transparency differently -- see my test above.
Here's a screenshot from my machine: ![]() |
|||||
Posted: November 2, 2006 11:00 am | ||||||
Crapadilla
![]() |
||||||
Posted: November 2, 2006 11:06 am | ||||||
Vladimir Golovin
Administrator |
||||||
Posted: November 2, 2006 11:09 am | ||||||
Crapadilla
![]() |
Same filter saved as a 32bit TGA with alpha in PS...
--- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|||||
Posted: November 2, 2006 11:16 am | ||||||
Vladimir Golovin
Administrator |
Crapa, can you show me the original image / background you apply the filter to?
|
|||||
Posted: November 2, 2006 11:20 am | ||||||
Crapadilla
![]() |
Vlad, the New Image transparency did the trick! The Alpha Maps work perfectly with this.
--- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|||||
Posted: November 2, 2006 11:20 am | ||||||
Vladimir Golovin
Administrator |
Hehe
![]() |
|||||
Posted: November 2, 2006 11:28 am | ||||||
Crapadilla
![]() |
This is definitely something that is not very obvious using FF standalone, but logical when I think about it in relation to PS layers with transparency. I deserves a mention in big red bold font in the manual!
![]() One should be able to see Alpha Map of the filter, regardless of the alpha existing in the loaded image. --- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|||||
Posted: November 2, 2006 11:29 am | ||||||
Vladimir Golovin
Administrator |
Good point, I'll add that to my list.
|
|||||
Posted: November 2, 2006 11:30 am | ||||||
Crapadilla
![]() |
Oh, and thanks and ten thumbs up for the great real-time support!
![]() ![]() ![]() --- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|||||
Posted: November 2, 2006 11:31 am | ||||||
Crapadilla
![]() |
Well, what remains is this strange behaviour that for simple filters that dont use an image component, the default lifesaver image seems to prevent the filter's alpha map from showing, but for surface filters this alpha seems to be ignored and the 'correct' Alpha Map is rendered.
It seems that the lifesaver alpha is completely opaque. In that case, the surface filter's Alpha Map should be completely opaque as well, if it is a simple OVER operation that determines the final alpha, as it appears to be the case with the simple filters. --- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|||||
Posted: November 2, 2006 12:08 pm | ||||||
Crapadilla
![]() |
The Color Isolate filter, on the other hand, is a simple filter that DOES display the correct Alpha Map, even when the default lifesaver image is loaded. My guess is this is because it uses an image component, whereas in our example Coffee Stain and OilFlame don't.
Again, from an image compositing standpoint it works as expected, as Color Isolate directly works on the source image alpha and Coffee Stain / OilFlame comp their image data over the source image and its alpha, but for the user it might still be somehow confusing. It might be a workable solution for FF standalone to use a completely black alpha channel as default, so that all filters can output their alphas into a 'clean' alpha space so to speak. --- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|||||
Posted: November 2, 2006 12:19 pm |
Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!
33,711 Registered Users
+18 new in 30 days!
153,533 Posts
+31 new in 30 days!
15,348 Topics
+73 new in year!
30 unregistered users.