View Full Version : Combustion 2 Avid .OMF question
03 March 2003, 08:31 PM
Does anyone know of an .OMF exporter for combustion? We have an Avid system at work and it would be great if I could export to Avid's native .OMF format.
03 March 2003, 02:51 AM
I don't think anything other than an Avid (or ProTools) can actually write an OMF, but I'm not 100% sure. Instead, though, why not get the Avid Quicktime codec here (http://support01.avid.com/support/ProdRef.nsf/AdminProbSolByProduct/ECE84E24EC39450885256A1D00785424) (at least I think it's that one), and render to Quicktime instead. Assuming you've got everything set right when you render (depends on which kind of Avid you have etc), the import will happen in a snap. Wes Plate (http://www.wesplate.com) has a pretty good "how to render for the Avid" tutorial for After Effects that should translate to Combustion w/o too much trouble. Hope this helps
03 March 2003, 11:02 AM
Phred42 is correct. There is no existing method for combustion to accept omf files. The information on the website he suggest is useful and will apply to combustion as well as After Effects.
03 March 2003, 06:45 PM
Probably not that helpfull, but the guys at Automatic Duck have one that allows afterfx to read omf files from avid. You might want to ask if they are working on any other similar translators for combustion.
03 March 2003, 06:48 PM
Thanks for all the help guys. Ideally what I'd like to be able to do is either write an .omf out of either combustion or avid. But I'm looking into Avid qt plugin. Hopefully that works out well. I usually do all the compositing on my machine and then pass it off to another guy who does the final edits on his Avid system, so I was just looking at a quicker solution to save him time bringing in tga's.
03 March 2003, 07:18 AM
You might also check Digital Fusion from Eyeon (http://www.eyeonline.com/) he has a suport for reading and writing *.omf files.
Is a litlle more expensive solution but is good as C2 or AE.
01 January 2006, 03:00 PM
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.