Kraellin
![]() |
there is an assumption that is made when mapping a transparency into another component. i was going to post this as a bug, but it's probably not really a bug and may just be i need an explanation.
if you look at the posted picture, my assumption would be that the component on the right shld be showing the transparency of the component on the left. but, it doesnt. now, i know the alpha channel is a separate channel from the HLS, so from that standpoint the transparent part wouldnt show in the HLS. but, that leaves the question of where did the alpha channel go? and in the 2nd image i'm posting here, i added a get alpha but it's all white. and that just leaves me confused. do some components not pass the alpha channel along? arent all the components operating in 32 bit, 4 channel? the blend component seems to work fine, but some of the others seem odd in this respect. but like i say, it could just be that i dont understand what's going on here. ![]() If wishes were horses... there'd be a whole lot of horse crap to clean up!
Craig |
|
Posted: April 12, 2007 5:56 pm | ||
Kraellin
![]() |
||
Posted: April 12, 2007 5:57 pm | ||
Crapadilla
![]() |
It's obviously not a bug.
Look at the image below. Although the new alpha gets multiplied into the source image for the thumbnail display purposes, the 3 Extract RGB components can still extract the unmultiplied RGB channels. So there you go, we have a clean 32bit RGBA. ![]() --- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|
Posted: April 13, 2007 3:07 am | ||
Crapadilla
![]() |
Now lets look at the first (topmost) Extract RGB component from the last image, which extracts R.
Trying to extract the RGBA channels from it shows us an expected behaviour (see below): The original R channel now resides within the R, B and G channels, constituting a grayscale image. The alpha, naturally, is completely white. ![]() --- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|
Posted: April 13, 2007 3:11 am | ||
Crapadilla
![]() |
Conclusion: Since the Extract XXX components only ever extract one channel, regardless of any alpha present, naturally, they don't pass along the transparency.
At an Extract component, 3 of the 4 channels are basically discarded, or rather, the three image channels are overwritten with the contents of the selected channel, and the alpha is discarded. --- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|
Posted: April 13, 2007 3:15 am | ||
Kraellin
![]() |
'get discarded'... ok, that's what i think i was wrongly thinking there. they get discarded, not passed through and not showing in the preview. ok, that makes sense. so after any extract the get alpha is going to be all white, since it's now basically a new, blank alpha.
If wishes were horses... there'd be a whole lot of horse crap to clean up!
Craig |
|
Posted: April 13, 2007 2:02 pm | ||
Carl
![]() |
Very enlightening and well explained, thanks for the knowledge
![]() |
|
Posted: April 14, 2007 11:04 am | ||
Vladimir Golovin
Administrator |
The transparency passing isn't uniform across all components, every component handles transparency differently. The exact description can be found in the help article for the component.
|
|
Posted: April 16, 2007 5:53 am | ||
Kraellin
![]() |
thanks, vlad. yes, i've noticed this about the transparency passing. drives me nuts at times trying to figure what gets passed and what doesnt, but i'm getting there.
If wishes were horses... there'd be a whole lot of horse crap to clean up!
Craig |
|
Posted: April 16, 2007 2:41 pm |
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
+27 new in 30 days!
15,348 Topics
+72 new in year!
25 unregistered users.