![]() Intel Iris Plus Graphics 645 - VRAM: 1536 MBĭisk0 - APPLE SSD AP0512N 500.28 GB (Solid State - TRIM: Yes) MacBook Pro (13-inch, 2019, Two Thunderbolt 3 ports)ġ.40 GHz Quad-Core Intel Core i5 (i5-8257U) CPU: 4-coreīattery: Health = Normal - Cycle count = 218 Kernel extensions present - This machine has kernel extensions that may not work in the future. ![]() Limited drive access - More information may be available with Full Drive Access. This will reduce your performance.ģ2-bit Apps - This machine has 32-bits apps will not work on current versions of the operating system. Heavy I/O usage - Your system is under heavy I/O use. Runaway user process - A user process is using a large percentage of your CPU. System modifications - There are a large number of system modifications running in the background. Apple has said that unsigned software will not run by default in a future version of the operating system. Unsigned files - There are unsigned software files installed. Heavy RAM usage - Apps are using a large amount of RAM.Ĭlean up - There are orphan files that could be removed. These issues do not need immediate attention but they may indicate future problems or opportunities for improvement. Heavy CPU usage - Some processes are using an unusually high amount of CPU. Unsigned files - There are unsigned software files installed that could be adware and should be reviewed. Runaway process - A process is using a large percentage of your CPU. Some newer USB SSDs will exhibit slow and unpredictable behavior if using them on a USB hub or using any other cable besides the short, thick factory cable.Īnything that appears on this list needs immediate attention. If using external storage devices, run a Blackmagic Speed Test to verify performance is as expected. Make sure all storage devices are formatted HFS+ or APFS, not ExFAT or anything else. This can be random and unpredictable, whereby the storage device apparently works OK for a long time, then suddenly it flickers off line. Numerous USB hubs can cause unpredictable behavior, esp. ![]() If using a USB hub of any type, as a test procedure discontinue that. If any of your media is on a NAS, try to reproduce the problem without that, having all media only on directly-attached storage devices. There have been many reports of external interface devices and bluetooth audio devices causing hangs and crashes. This is just a temporary test to inspect whether those are involved. Months ago I forwarded that to Apple Pro Apps Support, along with small files to reproduce this.Īlso - make sure you temporarily disable any external A/V devices such as AJA or Blackmagic interfaces, also do not use wireless earphones or AirPods. ![]() I can easily reproduce FCPX crashes using HEVC material from a DJI Inspire 2. Some of your clips show drone footage, which on recent DJI models is often HEVC. If you are running Chrome or are using any HEVC material, those are also possibilities. That is good, at least no plugins simplifies the situation. Thank you, i dont have eny pluggins at all Try resetting FCPX preferences (item 11 below): Make sure you have at least 20% free space on all hard drives. As needed, manually render the timeline, e.g, select all clips with CMD+A and do a one-time render via CTRL+R. Then delete all cache files via select library and File>Delete Generated Library Files>Delete Render Files>All. Evaluate all plugins you have installed, update them, and totally remove any non-needed plugins.ĭisable background rendering in FCPX preferences. A bug in any plugin can cause FCPX to hang or crash. If it hangs during that task, use an external tool such as Handbrake to transcode before importing.ĭue to limitations in the FCPX plugin architecture, all plugins developed with the FxPlug3 framework run within the address space of FCPX. To prevent this, transcode to proxy or optimized media. There is a narrow bug in FCPX 10.4.7 and 10.4.8 on both Mojave and Catalina whereby certain HEVC codecs can cause a hang or crash. They mis-use the MacOS VideoToolBox framework, often causing FCPX hangs and crashes. Do not run Chrome or any browser based on Chrome such as Brave.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |