Hi Russ, Ben and Dave, good work on that indeed lads 🙂.! Having not ever used this workflow, I learned this too with some tests as well and I too was somewhat perplexed that alpha channel was not preserved from image sequence in Compressor.app
It just seems to be by design ? (hopefully not a flaw) that the ALPHA CHANNEL is NOT preserved by compressor.app (even V3.0 according to older posts too also COW etc) from a source image sequence.
To confirm: After reading the posts in this thread.. In compressor.app I also tried it with and had no success 😮 with using;
- ANIMATION and INTERMEDIATE codecs
- using OPENEXR 32, TIFF, PNGS 16 etc sequences (from 3D app)
and.. yes no alpha channel was preservered from the image sequence source.😢
Some Other Alternatives: Nuke (r+W), Older Quicktime PRO 7.app (open image sequence), PS.app and certainly Motion (Import Image Sequence) do a good job as an alternative. I'm sure there are many MORE (AE etc etc)
TIP: (for those that care), We use (our workflow) Compressor.app for Apple Motion.app projects (.motn) to RENDER the .motn (pple motion) projects as we turn them around (3rds, banners etc etc), and to pass that PRORES4444 on FCPX etc. The Compressor.app (import File / motion_project.motn) works great😎 and renders "in the background" allowing use of the Motion.app UI for creative work.
sadly the Motion (.motn) project is confines (localised) to a Cluster on et same machine.
- A Qmaster distirbuted cluster will not work and ...
- now in Compressor.app V4.1, the UI will NOT allow the selection of the distributed Cluster to RENDER the .motn project
Warwick
Hong Kong