From documentary to music video.I have done it all now with it and once the OMF-export and broadcast-preview is fixed I will see no reason at all to use FCP7 ever again. This was probably the last post about this was successful and FCPX has found its way into my workflow. At the same time you can export out of FCPX to ProRes, because that export uses the GPU(!!!) so you won´t feel a decline in speed in the compressor render.so if you are once in a pinch you can export with both programs. At the same time you can work on in Motion.
In render-busy times I also found this workflow: In Motion I can export with a Compressor setting Motion then uses the CPUs. Closed FCPX to free up the RAM.suddenly the fans in the Macbook jumped to live and Motion started working again! So Motion needs RAM to use the quad core. Motion renders slowed extremely down again. I then opened FCPX with a big project and maxed out those 16GB again. Once I had the 16GB built-in, Motion started flying and used 13GB of the RAM. One more thing about the 16GB: I had a motion project and my new machine was maxed out with the 4GB-RAM and Motion was rendering slow. I played around for 2 hours now without a major hiccup. In FCP7 such a timeline would often crash on me.
You can choose items and the cursor jumps in a split second to that clip waveforms and thumbnails are turned on BTW.
#Preference manager fcpx movie#
The timeline of the final movie has 1004 items according to the Project-Itemlist. So I equipped it with 16GB just like my Mac Pro.and now it works great. The Peakbreak project which is still my biggest on FCPX with over 7500 clips didn´t do too well on that new machine either. Well, finally got a new Macbook (2.2GHz quad core, Feb 2011 edition)
0 kommentar(er)
