Activity › Forums › Adobe Premiere Pro › .MXF files in Premier Pro
-
.MXF files in Premier Pro
Posted by Rex Summerfield on June 12, 2010 at 4:07 amWhat do I need to do to get .MXF files into CS3? Right now its giving me an incorrect file format error. Does CS4 handle them better? I’m on a 32 bit machine so that is my upgrade limit.
Larry Seibert replied 13 years, 1 month ago 8 Members · 14 Replies -
14 Replies
-
Todd Kopriva
June 12, 2010 at 5:16 amAs Alex implies, MXF files are somewhat generic container files. There can be all sorts of things in there. As of Premiere Pro CS3, the CS3.1 update gave Premiere Pro the ability to import a certain kind of P2 media in MXF files. See this page.
With CS4, support for some other kinds of media (Avid and XDCAM HD) within MXF files was added. See this page.
———————————————————————————————————
Todd Kopriva, Adobe Systems Incorporated
putting the ‘T’ back in ‘RTFM’ : After Effects Help on the Web
———————————————————————————————————
If a page of After Effects Help answers your question, please consider rating it. If you have a tip, technique, or link to share—or if there is something that you’d like to see added or improved—please leave a comment. -
Rex Summerfield
June 12, 2010 at 4:48 pmI downloaded a .MXF file from another site which, aparently I am not allowed to mention here. It was a .MXF file from the new Canon XF305 series camera. Canon claims wide spread NLE support for the file but it gave me an error when I tried to bring it into CS3.
-
Rex Summerfield
June 12, 2010 at 4:50 pmYou can find the files in question by searching for Native XF 305 .MXF files from Nick Wilcox-Brown
-
Ann Bens
June 12, 2010 at 7:53 pmCS5 support the new Canon.
Dont think CS3 can handle 50 Mb/s format. -
Tim Kolb
June 13, 2010 at 5:23 amSince the camera wasn’t in existence when CS4 came out…I’d say ‘doubtful.’
TimK,
Director, Consultant
Kolb Productions, -
Rex Summerfield
June 16, 2010 at 2:32 pmYou are probably correct. I was hoping that when Canon said it was “already compatible with most NLE’s” they were using a known Codec we could drop right in. Maybe that is asking too much. What would we do without conforming, converting, and employing a multitude of work arounds for the first 12 months of every new camera release?
-
Tim Kolb
June 16, 2010 at 4:33 pm[Rex Summerfield] “I was hoping that when Canon said it was “already compatible with most NLE’s” they were using a known Codec we could drop right in.”
Well…keep in mind that CS5 is the current version of PPro, and you can drop it right in. As all these things develop faster and faster, keeping all the aspects of your workflow up-to-date in the moment will become more and more important.
Production Premium costs less than AE alone did when I used to buy it on 5 or 6 floppy disks and it didn’t even have a “comp” timeline…
…it’s hard to say that all this progress hasn’t benefited the user in some pretty significant ways.
TimK,
Director, Consultant
Kolb Productions, -
Rex Summerfield
June 16, 2010 at 8:11 pmI hear you and I don’t disagree with you basic take on it. Its just that CS5 means a whole new system to get up to speed with 64 bit. New camera, new system, all new software. A very large chunk to bite off all at once. I was hoping CS4 could handle it for a year so I could piecemeal the upgrade as finances became available. I may have to pass on the new Canon for awhile.
Reply to this Discussion! Login or Sign Up