![]() What if you then export the XML of that project w/o effects, create a test library and load that project XML (minus effects) to the test library? Does it happen then? What if you duplicate that project, open the duplicate, then delete all effects by CMD+A then Edit>Remove Effects. I had one user send me his 1 hr timeline and he had a ton of compound clips and was using Color Finale. Tangier, I've seen this reported a few times, inc'l Intel, M1 Max and M1 Ultra. Playback and scrubbing are fine, but manipulating clips in the timeline are choppy and slow. Tangierc wrote: You all know how FCP can be very fluid and free manipulating clips on the timeline? I've had issues where large projects significantly reduce timeline editing performance even projects where all of the video in use are ProRes proxies. I found similar problematic performance from the same project on an M1 Mac as well using a faster thunderbolt connection to the RAID I was using and form a single drive with the same project.ΔΆ013 Mac Pro / M1 Pro MacBook Pro.same results Even on an older 2013 Mac Pro this was not an issue working on multicam 4K projects. Think manipulating heads and tails of clips, moving them around. I am specifically targeting timeline editing performance and Not the application as a whole (though there are some beach balling issues at times). ![]() Most searches online yield the same results about making FCP faster, but none of them have worked for me. Playback and scrubbing are fine, but manipulating clips in the timeline are choppy and slow counter to what many longtime FCP users are used to with the application. You all know how FCP can be very fluid and free manipulating clips on the timeline? I've had issues where large projects significantly reduce timeline editing performance even projects where all of the video in use are ProRes proxies.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |