Free wrote: ...I haven't uninstall FXFactory plugins yet, and did reinstall a few free project templates from motionVFX that I like... Could these templates be the reason to KP?... I was editing a pic in Photos app and Boum! FP again, the first one since I installed everything fresh couple of weeks ago:
Check System Preferences>iCloud Drive>Optimize Mac Storage. Some cloud storage services will immediately upload the file, then show the file name with zero bytes. It then becomes a "streamable file". You don't typically want that for video files you're actively working on.
For further details see Apple and other documentation on how to configure iCloud Drive.
tvchris wrote: Thank you both for your guidance. Seems like I was on the right track. I've been editing on FCPX for years but never a recurring project like this. Thanks again!
If it did not crash, hang or show black screens using the same DJI 4k HEVC media on FCPX 10.4.6 but does on 10.4.8, that could imply the known HEVC issue.
It works OK with many HEVC codecs including the iPhone but it consistently has problems on DJI 4k 8-bit HEVC and 4k 8-bit HEVC from an Arlo security camera. There was another report of it crashing on 4k 10-bit HEVC from a Panasonic EVA-1, but that user never followed up.
The problem with proxies is you must go back to orig. media for the final export, so it can happen there. As a test can you transcode within FCPX some clips to optimized media and use only those clips in a test timeline, then try exporting that? If the transcode completes OK it thereafter never looks at the original media so should not have problems.
If that works it's the best solution because it avoids external transcoding.
If it does not work you'll have to externally transcode, maybe using Handbrake from HEVC to ProRes or the free version of DaVinci Resolve or EditReady2. I'm not sure the free version of Resolve has HEVC encoding due to licensing issues but you can check.
EditReady2 is an excellent utility, high quality and frequently updated. It is not very expensive: www.divergentmedia.com/editready
In general there should not be a quality problem because the HEVC source media must at some point be transcoded to ProRes cache files, then again to the final output codec. If you externally transcode to ProRes then import, it doesn't really add generational loss.
I think several of those are expected: RemoteServiceDiscovery, Rapport.Framework, RemoteViewServices.framework, etc.
However VTwinFx.fxplug is CoreMelt. I'd suggest totally removing that via their uninstaller, as shown in the below video.
There are two possible issues here:
(1) A system-layer issue causing the kernel panics, total system hangs, etc. That clear cut and no application is reponsible for this, nor can it be fixed at the application layer. Such problems can also destabilize the application layer just like a house with a crumbling foundation can destabilize the rooms above it. Recommended actions: overnight, multi-day bench diagnostics by Apple. Under currentn circumstances that might not be possible.
(2) An FCPX crash/hang due to an FCPX bug or a plugin. Of those, a crash/hang caused by a plugin is much more common. Any plugin can crash or hang FCPX, and it's often difficult to determine plugin version or cleanly remove the plugin. Recommended action: (albeit time consuming) is manually remove each plugin according the each company's unique instructions. Do a clean re-install of FCPX then try typical actions without any 3rd party plugins installed. If after significant testing it does not crash, gradually, carefully, incrementally install each plugin, doing significant testing after each one.
This is an unfortunately a difficult situation and is created by Apple developers who took the quick and easy approach of putting plugins in the same address space as FCPX. This was previously done by browser developers who had all tabs in one process, where any web page would crash the entire browser. The development practice goes way back, where various system extensions, extended procedures, etc would be loaded in the app address space.
The practice is understandable since all threads of a process (inc'l plugins) have full high-speed access to all memory and inteprocess communication is fast and easy. The alternative is have a separate host process for the plugins and use a more difficult IPC method, which may have performance issues. However decades of software developmentn experience has shown the "in processs" model of extensions is problematic from a reliability and support standpoint.
Make sure you have at least 20% free disk space on all drives.
Disable background rendering in FCPX preferences, then delete all render files via File>Delete Generated Library Files>Delete Render Files>All.
Then select all clips in the timeline with CMD+A and do a one-time render with CTRL+R. Observe whether it finishes OK and is playable. If so, then export this way:
File>Share>Master File>Settings, Format: Computer, Video Codec: H.264 Faster Encode, Resolution: 1920x1080.
If that fails, state the error or behavior.
Buk wrote: ...When I worked in Final Cut Pro 10.4.6, I had crashed os at all...
Try these settings: Share>File>Master File>Settings, Format: Computer, Video Codec: H.264 Faster Encode, Resolution: 1280 x 720p, then use AirDrop to send to iPhone. It should immediately appear in your Photo library under "Recents".
You could also use the "Apple Devices" preset but the encoding is very similar.
This is using FCPX 10.4.8 and iOS 13.5.1 on an iPhone 11 Pro. However it should play even on older iPhones.
VidGreg wrote: ...Much bigger and better chips being prepared for the Mac line up....Worlds fastest computer is now ARM based. ARM is an easily expandable RISC CPU processor, so things like core count is only constrained by device size/thermals/$$...Wonder about RAM, will it be universal shared RAM like in current devices or will Apple create separate RAM for Macs....
VidGreg wrote: Worlds fastest computer is now ARM based....
Free wrote: ...Nevertheless, I guess I'll try to uninstall FXFactory, AUs and start over again with it.
Though I feel that the installation of my Izotope plugins was way too weird and suspect them even more...
Just to be clear, I have not even opened a library, so haven't actually used any of the plugins. But I think it was clear. I guess that plugins can crash or hang FCPX even if not in use...But I do need those to work with Logic Pro....Is there a way to deactivate them only for FCPX?...Or at least a way to do so when working with FCPX and reactivate them when opening Logic?... yestarday...it did crash twice, hanged quite consistently but also done soemthing that never happened before:...At opening, FCPX just froze before being able to do anything but without the beach ball, not allowing to touch anything without the "Funk" sound...I'm also having smaller hangs on other moments, such as opening Firefox and troubles connecting with my VPN... Not sure it's related though.
Jonathan Levin wrote: Or is there another method either in Compressor or FCP to get all this info? Just thought I'd check before going there.
Free wrote: I decided to erase the computer and start over fresh.
New last Catalina 10.15.5.
No 3rd party kernels, no server performance mode, no chrome or any derivates...
I did install a bunch of AU though, including, but not only, Izotope ones that did give me a little headache on install and had to reboot to have them working.
(I even had two of the installers staying forever on the dock, and actually had to press long the ON button to be able to restart the machine and get rid of them)
Could AU give problems to FCPX? BTW, those specific Izotope plugins weren't installed in my previous OS.
...FCPX crashed twice already, takes long to open and hangs way too often...
Logic seems to operate fine. Finder does hang a little sometimes.
Everything else seems fine so far...
I have uninstall FCPX with FCS Remover, reinstalled it... Same.
Here is the only crash report I've managed to get:
I think I'm gonna need to give up on video editing for a while, it's been over two weeks trying ONLY to solve this and my creative mojo has gone long time ago. I might get a newer computer later this year or the next one and try to start over again and hopefully I'll be luckier then.
I might tomorrow try to run it from a different user see if anything changes there.
Could it be one of the FXFactory plugins instead?
blakeylewis wrote: ...you can hear the fans working & the metal casing of the laptop becomes very hot. MacBooks are great but I think that is the only let down that when editing on FCP, you can't even have your laptop on your lap as it becomes too hot...