![]() I'd always try trashing preferences first by pressing alt + cmd before opening FCP. ![]() You can exclude/confirm problems with external drives (or cables!) by unplugging them and by creating a small test Library on the system drive, exceptionally.īTW: reinstalling FCPX rarely solves the problem. Every now and then, you should delete this junk. Background rendering is not the devil, but it's for people with a surplus of disk space. If that's the case, the (inexpensive) paid version of FCLM allows you to delete Render, Optimized and Proxy media from within that app. FCLM also hints to problems in the Libraries, like missing files asf.īeachballs also appear if you're running out of disk space, a deadly sin. If not, the problem has nothing to do with any corrupted files within an old Library. Close all Libraries before you quit, always. Once FCP is running - at least for now - check if you have a long row of Libraries open. By double clicking the latter in the FCLM-list, (thereby launching FCPX without ballast), you should be able to start FCPX. (highly recommended) allows you to create a new, empty Library.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |