Dennis Radeke
Forum Replies Created
-
No. Adobe does not currently support XML export, just XML import. Premiere Pro also supports AAF import and export.
-
Shane is right, why not just capture in Premiere Pro? In fact, you don’t have to ‘capture’ DVCProHD in Premiere because it understands something other than Quicktime! 😉
In Premiere Pro CS4’s Media Browser panel, you can view the P2 card directly, load the clips into the source view, mark an in/out and take to the timeline. In a pinch, you can edit directly off of the P2 card.
Also as Shane and I have discussed, there is a question about what you need to do to edit FCP ProRes with systems. My understanding is that the later versions of Quicktime already include the ProRes codecs, so downloading the QT decoder isn’t necessary.
-
Why not Prores? or Quicktime? Premiere Pro can use just about any codec the system can see by going to the desktop mode inside of the playback settings. You might find some information with this link:
https://blogs.adobe.com/davtechtable/2008/11/new_cs4_and_final_cut_import.html
Watch a chunk of the video and it should help you out. Good luck.
-
Apple changed something in their latest release and it broke all of the XML exporting to Adobe. FCS2 works fine. Adobe is aware of this and will release an update soon to adapt their support for Apples FCP 7.
Hope this helps,
Dennis -
If you’re using CS4, you should import your FCP project into Premiere Pro and then you’ll have independent clips being put back as MXF.
-
Ashley,
In FCP you have to use log and transfer to convert the .mxf files unless you look at a 3rd party solution that I think was mentioned above. If you’re looking for native P2 editing on the Mac, Premiere Pro and Avid will allow you to edit MXF files. Of course, with Adobe, you need an intel Mac in order to use Premiere Pro. I can’t tell you if Avid will still work on a G5.
-
Why is the monitoring of AVCHD on Premiere Pro bad?
-
While it is true that only Photoshop (PC only) is a true 64bit program, it is an error to assume that Premiere Pro and After Effects do not benefit from a 64 bit environment. The single greatest advantage to a 64 bit system is the ability to address more memory and that’s what Premiere Pro and After Effects do. You can access up to 4GB per core which means on a 4 core system, you could use 16gb.
Where this is useful is when you’re using the integration features of CS4. Dynamic Link, multiple programs sharing comps, sending to Encore, etc. These are all instances where the memory becomes a big help.
I straight out recommend that people use Vista 64 with 8gb of RAM if at all possible.
-
What version of Adobe CS are you using?
What version of Quicktime are you using?I can play most Apple Prores files without difficulty. You need to have a newer version of Quicktime. The latest is 7.6.2. I use 7.5.5 as it’s worked for me.
While the Avid codec is free and awesome, it plays terrible in Premiere Pro, so I cannot recommend it.
-
I’ll try and give you a few bits here.
It sounds like a typical FCP editor that thinks this is ‘native’ media when in fact everything ends up as a quicktime. Chalk one up for Apple marketing. In CS4 you really can edit of the SxS but that’s another whole story.
To set up between FCP and Adobe, you might check out this blog and video: https://blogs.adobe.com/davtechtable/2007/06/adobe_production_premium_cs3_a.html
If you have to convert files, I would convert them to a more hospitable quicktime codec or to an AVI codec depending on what platform you end up editing on. If you’re using CS4, the Adobe Media Encoder will allow you to batch convert. Then for editing, Premiere Pro CS4 should be able to mix and match any of the codecs without much difficulty. If you’re using CS3 and earlier, then I would probably have to decide based on the what the bulk of the material was captured as. If it’s this QT ProRes, the above link should show you how to build a custom preset.
Hope this helps.