- Posts: 175
- Thank you received: 5
3 Post Moderation Rule for New Boarders (25 Jan 2021)
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
FCPX 10.4.5 Crash on 4K Export
- CBlakeston
-
Topic Author
- Offline
- Elite Member
-
I thought I would check the preferences were the same having installed it fresh and going to destinations and clicking / highlighting each one It crashes without fail when I select Apple Devices 4K. Every time.
Please Log in to join the conversation.
- CBlakeston
-
Topic Author
- Offline
- Elite Member
-
- Posts: 175
- Thank you received: 5
Does anyone know a way of resetting the FCPX sharing destination?
Please Log in to join the conversation.
- CBlakeston
-
Topic Author
- Offline
- Elite Member
-
- Posts: 175
- Thank you received: 5
For me FCPX crashes every time I try to export to 4K. Is anyone else seeing the same?
Please Log in to join the conversation.
- CBlakeston
-
Topic Author
- Offline
- Elite Member
-
- Posts: 175
- Thank you received: 5
Please Log in to join the conversation.
I would suggest that you uninstall FCPX using Digital Rebellions FCP remover, rather than just deleting the app. Maybe something corrupt is still intact even after reinstalling. Also, be sure you have the latest Pro Video Formats v2.07 installed. You don't specify what OS you are using, but I tested this on the latest Mojave 10.14.2.
Creating history....one edit at a time !
Please Log in to join the conversation.
- CBlakeston
-
Topic Author
- Offline
- Elite Member
-
- Posts: 175
- Thank you received: 5
I'll follow your advice now and try using the Digital Rebellions remover. Thanks.
Please Log in to join the conversation.
- CBlakeston
-
Topic Author
- Offline
- Elite Member
-
- Posts: 175
- Thank you received: 5
Please Log in to join the conversation.
Control-click in the Destinations list, then choose Restore Default Destinations.
Also see this document: support.apple.com/kb/PH12719?locale=en_US&viewlocale=en_US
Creating history....one edit at a time !
Please Log in to join the conversation.
- CBlakeston
-
Topic Author
- Offline
- Elite Member
-
- Posts: 175
- Thank you received: 5
Please Log in to join the conversation.
Creating history....one edit at a time !
Please Log in to join the conversation.
- CBlakeston
-
Topic Author
- Offline
- Elite Member
-
- Posts: 175
- Thank you received: 5
I added two custom exports back that I use. Opened a project I was working on and thought - I'll just check. And it crashed again selecting any of the exports. I restored to default again and it still crashes no matter what I select.
I made a brand new project and that crashes too. I'm confused. It worked just minutes ago.
Please Log in to join the conversation.
- CBlakeston
-
Topic Author
- Offline
- Elite Member
-
- Posts: 175
- Thank you received: 5
The first time I launched FCPX it worked and could export as normal. But then closing down and open any other project including the same one again now makes everything crash without fail when selecting any of the Apple Device presets. 720p, 1080p, or 4K.
Please Log in to join the conversation.
If you have ample drive capacity, then I would try repairing permissions on all connected drives. Are you using any specific 3rd party plugins that may be out of date ?
Finally, if the above still doesn't help, create a new ADMIN user account on the computer. Launch FCPX from that new user account and see if the problem is still present. If it reliably works with a new user account, then the issue is likely your current user account. There is a specific way to repair that, but test it and post back your findings.
Creating history....one edit at a time !
Please Log in to join the conversation.
Please Log in to join the conversation.
- CBlakeston
-
Topic Author
- Offline
- Elite Member
-
- Posts: 175
- Thank you received: 5
Because I couldn't use those device presets listed as default - I imported the device presets from compressor and figured I'd use those. That seemed to work ok. Then later this morning my muscle memory went to the default ones and it worked. I opened up preferences and tried clicking on all the export options listed to highlight them.. no crashes. that worked too.
I thought it might break again but still seems to be ok now a reboot or two later. The only thing I can think is I lethargic when it started working again I had iTunes open playing music from a wireless hard drive.. and noticed when it was working the 'what to do when finished' option was set to add to iTunes library. I changed that for each preset to 'do nothing'. Maybe that was why? And updating to 10.4.5 set it back to default and when highlighting it when iTunes wasn’t open meantime it couldn’t find the iTunes media folder?
But for now at least.. things seem to work again... *touches wood*
Please Log in to join the conversation.
CBlakeston wrote: ... iTunes open playing music from a wireless media drive when I went to click on the settings.. and the 'what to do when finished' option was set to add to iTunes library. I changed that for each press to 'do nothing'. Maybe that was why? ...
In 10.3.x there was a bug whereby FCPX would immediately crash upon raising the file *import* dialog box if a certain file was in the import folder. In my case it was an .M4A audio file from iTunes. This was difficult to perceive because there was a small but variable delay in the crash. You could sometimes click on a video file, then it would crash, which gave the impression it was that file. In actuality was was the .M4A file in the import folder. The file was not apparently corrupt or damaged.
Since the import dialog remembers the last folder location, every subsequent import attempt would crash upon launching the dialog or almost immediately thereafter. You couldn't navigate to a different folder -- it would usually crash when enumerating the files in the import folder. In my case the solution was to identify and remove that iTunes .M4A file. I vaguely recollect other people had this with different files, not just .M4A.
For your *export* case, I wonder if something similar is happening? IOW something in the export folder or the composition/length/characters in the path to the export folder. You can rule this type of bug in or out by setting the default exporting to a different location containing no other files. Ideally an empty thumb drive or portable drive with nothing in it, and just export to the root of that (as a test). You want a totally different, short path to the empty export location, and (as a test) make sure there are no odd characters or spaces in the path to that location. Also make sure any export drive is HFS+. APFS should work fine but it's new. NTFS you can't write to, and for exFAT, other operations are needed to split the resource fork metadata to hidden files.
Please Log in to join the conversation.




