View Full Version : straight vs pre-multiplied
12-29-2009, 05:03 AM
What is the difference between straight vs pre-multiplied alpha?
In practice, when using AE, when should i use one or the other, and what is the workflow?
Generally, I render elements with an alpha channel, from my 3D package. Then I use "pre-multiplied alpha interpretation" upon import to AE, because this removes fringing, ie the background color that bleeds into the anti-aliased edge of the rendered element. Seems to work, but still I'm not sure this is the best prctice, or exacly what is happening.
thanks for reading!
12-29-2009, 06:17 AM
See this page:
"Alpha channel interpretation" (http://help.adobe.com/en_US/AfterEffects/9.0/WS3878526689cb91655866c1103906c6dea-7f7ea.html)
12-29-2009, 07:20 AM
Very helpful! thank you.
01-15-2010, 04:33 PM
I always use "straight" because if you have effects etc you don't necessarily want the added "fringe" from the background color. Straight matte is best in my opinion. You only really would use "Pre-multiply" if the comp you're pulling it into has the same background as what you rendered from but even that is a little dicey.
01-16-2010, 02:46 AM
hmmm, it is still confusing.
In after effects, the interpret footage dialogue allows you to "interpret footage as" pre-multiplied or straight. with footage created with the default settings in my 3-D app, which is very commonly use, I need to use "interpret as pre-multiplied" in order to get the results you describe. Otherwise I get fringing. What I do is interpret as pre-multiplied, then I select the background color, the color that is rendered into negative space, generally black, as the pre-multiplied color. The results are perfect, as far as I can tell. But then again everybody keeps saying use straight, not pre-multiplied, so I'm just wondering what information I am not understanding.
01-16-2010, 02:57 AM
The 3D application would have to export the render as straight to make the difference. If the 3D application can export straight, you might give it a try. It should fix the problem when you import with Straight interpretation.
Theres also a good video that explains the whole straight vs. premultiplied thing at:
I like the way it's summed up. Straight is better, but scares clients. Premultiplied looks great, but can cause issues. ;)
01-16-2010, 02:57 AM
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.