ignore alpha in Combustion and show color in there


#1

Hi!
Well, now I’m confused:
I got footage (tif-Sequence) with a alpha-channel, where my sky is keyed out by the alpha.
But now I want to import this footage in Combustion and want Combustion simply ignore the alpha, i.e. show the color-channel with the sky!
I could swear, I did that already a thousand times simply switching my footage-controls from color&alpha to only color, but it doesn’t work!
Where am I going wrong?


#2

Eh, don’t know what to suggest. Simply switching it from ‘color+alpha’ to just ‘color’ worked perfectly for me. :shrug:
However, even if this did start working for you, I don’t think it’s going to give you the effect you want. When a TIFF is saved with an alpha channel, the information that is being masked isn’t saved separately; unmasking the area will only reveal black. And so really, maybe that’s what’s happening in your case. Since the default background is black, it may just seem that disabling the alpha channel of the TIFF sequence is having no effect.
If you really want the sky in there, you’ll need the original footage.


#3

Yes, that seems to be happening, the colorchannel doesn’t change, but looking at the alpha channel everything gets white. But there must be the colorinfo of the sky somewhere, because looking at the image in Acdsee there is a sky!


#4

Just found out that on rpf-images it does what I want. When you turn to only Color here you get the sky!


#5

Well, seems like this should be an issue to the programmers of combustion!

I keep coming to that point all the time. We often render our sequences with alpha for the sky just in case sky could get fixed later. And all the time I miss my sky then in Combustion. At the moment my workaround is to convert the whole sequence to tgas without alpha in x-packed, then import this sequence as long as the sky doesn’t need to get touched. But this workflow gets really boring as it blows your diskspace up as hell as you need all the sequences twice.


#6

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.