Is there a way to not have the alpha component passed into the render element channels when exporting to EXR?
mme1_no-alpha.png is saved from the VBF as png but with no alpha, seperate the RGB channel is PS and you have full masks of you selected elements.
mme1_exr-alpa.png is saved from PS as it comes in from proEXR with the alpha component included in the render element which isn’t always wanted (I’m not sure when it would be needed either?), therefore requiring additional steps to create a full mask.
Should there be a ignore alpha tick box in the render element section? (Should I had this to the wish list?)
I should also say that I would prefer to have the RGBA remain as is (with the alpha applied) just not the render elements.
Number 2 is just wrong according to EXR specs (and common sense i guess ?). The alpha should never be automatically premult any color channel.
This is rather how PS (and seemingly proEXR ?) handles the EXR, not how it is saved
yes, as thorsten says, that’s how bad PS handles alphas.. and it’s even more depressing if you think that AE import them correctly. I mean, why one adobe application can, and the other can’t?
@rivoli - I just tried it in AE and it is the same as PS, as in if I change the background colour of the composition my mme elements show the background where the alpha was…(AE_CS3)
@instinct I know it’s wrong, but it is possible to get this same result from the VBF by saving the MME as a png with the alpha checkbox ticked. This is what lead me to think it was max/vray out-putting incorrectly, as like you said, the alpha should never be automatically premult to a render element, but it does!!
I don’t know if proEXR is doing it wrong or it is just doing it the same way it does with RGBA info, since that is what a mme element is…just another set of RGB channels, why shouldn’t it (being devils advocate) have the Alpha applied? Should there be something that indicates it is different?
The PNG variant is a similar issue and interpreted just as wrongly as EXR i guess (tho am not an expert with PNG heh).
There is a PLUGIN by Adobe now to fix it (only for CS5 tho)…Writing a plugin should be the weirdest way to fix a damn
bug i ever saw…
