![]() But perhaps what happened is that recent incompatible media was added to FCPX 10.4.6 and then the application was closed before getting the prompt. Before I upgraded to macOS Catalina, I always allowed 10.4.6 to do this because the prompts made sure all of us knew this was coming. Alternatively, a workaround for many files might be to open the library on a computer that still has Mojave and 10.4.6 and make sure it detects and converts all incompatible media it finds before upgrading to Catalina.ĬONSIDERATIONS: FCPX 10.4.6 or 10.4.7 may have not gotten the chance or failed to detect and convert some or all of the incompatible media files in Mojave. Hopefully, this only impacts incompatible media added recently by users, rather than for some strange reason FCPX failing to detect, prompt or convert the media over an unknown much longer period.įIX: You'll need to right-click and disable that media and/or convert it, or simply download and replace it with the 64-bit compatible version of the same media, usually for free if obtained from your paid subscription of a stock media site like Storyblocks. It's probably incompatible media created with 32-bit codecs, often obtained from stock media sites or other such sources. Right-clicking the file and looking at its Get Info in Finder will tell you the incompatible codec the video or other media was created with. You can also confirm the media file is gray in the FCPX timeline, FCPX browser, and the Catalina Finder location.ĬAUSE: If Quicktime can't play it, or it only plays in gray, it's now incompatible on Catalina. TROUBLESHOOTING: Toggle off rendering and see if any of the media in your project is grayed out or "missing" over the dotted lines where rendering stalled. SYMPTOMS: FCPX 10.4.7 in macOS Catalina becomes completely unresponsive while stuck on rendering media in your timeline. ![]() Once I figure out a fix, you'll be the first to know. I've tried multiple troubleshooting but haven't yet tried either of these which are just off the top of my head. Also consider uninstalling and reinstalling FCPX. Take a look at your drive and folder permissions. Regardless of any dismissive comments you may have and the typical everyday FCPX suggestions for fixes, this is a unique problem that you can be sure Apple will be including when they send out their typical post-upgrade fixes over the next hopefully few days. I just wanted you to know that you're NOT insane. I'm beginning to suspect it's a permission error, as the upgrade divides the system partition into two to create a protected partition and a data partition that applications continue to see as a single partition, but that are visible in Drive Manager as two drives with the same name except one has an added "- Data" extension. I haven't yet received the relink file error however. EVERYTHING you've done, I've done with the EXACT same results.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |