-
Exporting is Slow Compared to Premiere
Hello guys.
I just got a brand new mac pro 2×2.4 GHz quad-core Xeon, 16GB RAM DDR3 and I used FCP for the first time but I was disappointed by how slow it takes to export a simple 720p clip compared to Premiere which I’m used to.
I did a test and exported the same clip from FCP then Premiere. Same machine. The exact same compression and export settings. Each time premiere is almost 8 times faster.
When I export via [QuickTime Movie…] it’s super fast. But whenever I use a compression method via [Using QuickTime Conversion..] it becomes ridiculously slow.
Maybe I’m missing something here. Any help?
-
19 Replies
-
Export via Quicktime Conversion is VERY slow. I never use it. I recommend NO ONE use it.
Export the self contained…take that into COMPRESSOR and use COMPRESSOR to convert it to what you need to convert to.
Shane
GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
Read my blog, Little Frog in High Def -
I just tried the Compressor method. Exact Same settings, it’s faster than Quicktime Conversion but it’s still horribly SLOW compared to Premiere Pro. I mean, not a slight difference. It’s very significant.
-
Well, the new Premiere has that Mercury Engine under the hood. Tough thing to compete with.
If you enabled QMASTER to utilize all your processors in Compressor…you’d notice a difference.
https://lfhd.net/2009/05/06/qmastercompressor-troubleshooting-tip/
Shane
GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
Read my blog, Little Frog in High Def -
Thanks for the tip buddy.
I don’t know. To me it’s not normal to wait 15mins in order to export a 720p raw clip compressed on h.264 while you can do that within 2 minutes using another software.
-
Is the clip rendered in FCP? Is the clip rendered in Premiere?
-
[Bret Williams] “Is the clip rendered in FCP? Is the clip rendered in Premiere?”
Better yet is it the exact same file you are using in FCP vs Premiere?
If so I’m betting the slowness is caused by you not using a FCP friendly codec in FCP.
**Hindsight is always 1080p**
-
No it’s not rendered in both cases. Does it make any difference?
-
It’s the same file. What I understand from you, is that you have to convert any file to be FCP friendly first? A bit inconvenient don’t you think?
What are the FCP friendly codecs?
-
[Ala Mctoom] “What I understand from you, is that you have to convert any file to be FCP friendly first?”
Yes that is correct.
[Ala Mctoom] “A bit inconvenient don’t you think?”
Well if you take a file captured with FCP to a premiere system, you may not be about to use it at all. For example most if not all prores formats wont work in premiere.
That just the way video systems work, they are each designed to work with a set of codecs, working with codecs outside that set may cause you headaches.
[Ala Mctoom] “What are the FCP friendly codecs?”
Anything listed on the easy set up list.
Learning about video codecs, wil help you out a lot if you are serious about video. Not just knowing what codecs work with your editing system, but the advantages and limitations that each codec has will be most helpful.
**Hindsight is always 1080p**
-
There’s no doubt that if you have the Mercury Engine enabled, Premiere will render faster than FCP with the same files. We use CS5 and FCP on the same Mac pro, and have now switched 95% of production to CS5. Sequences which will play in real time with Premiere just will not play without rendering in FCP.
We are using AJA LHe/Quadro FX4800 with P2 AVC-Intra, and just applying the simplest filter or Magic Bully/BCC effect will stop FCP, but not PPro. That said, I’m still glad we are able to use both Final Cut and Adobe on the same Mac Pro. We have the best of both worlds on the one system.
Peter Corbett
Powerhouse Productions
http://www.php.com.au
Reply to this Discussion! Login or Sign Up