✎ Latest Free FCPX Effects
Joe M. replied to the topic 'FCPX Crashes, freezes, kernel Panic... All of them' in the forum. 5 hours 55 minutes ago

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:

www.dropbox.com/s/g1ltyhvsl2j2s5h/KP%20c...0July%204th.rtf?dl=0 ....

Any kernel panic or total system hang is not the fault of an application. The problem cannot be fixed by pursuing things at the application layer. It is a hardware or kernel-mode driver issue.

Your last kernel panic seems to reference graphics-related actions. IOKit is how apps in user-mode request functions which are implemented in kernel mode. MacOS appears to have trapped (ie crashed) in kernel space when executing a page fault. A page fault is when bookkeeping structures called page tables indicate the requested memory is not resident and must be paged in. I think there are only certain cases in kernel mode where that is permissible.

As previously indicated, if the Terminal command "kextstat | grep -v com.apple" does not show any 3rd-party kernel extensions, this is most likely a transient hardware problem. E.g. RAM, GPU, etc.

A kernel panic or total system hang cannot be caused by a user-mode app or plugin unless there is something wrong at the system layer. It cannot be truly fixed by removing or re-installing user-mode plugins or apps.

The machine likely needs to have multi-day bench diagnostics run by Apple. You could try wiping the system and installing Mojave, but if there's a transient hardware problem there's no guarantee that would work.

Almost any machine would be OK for your work. You don't need any special machine to avoid crashing. It shouldn't crash no matter what Mac you have, and won't be fixed by a special Mac configuration such as more/faster CPU or GPU or more RAM. The fix would come from a machine (old or new) which doesn't have the apparent hardware problem.

That said, any late-model x86 MacBook Pro would be OK. I prefer the 15/16" models due to more ports and larger screen. Apple will be releasing an ARM-based MacBook Pro by the 4th quarter of this year, which should be lighter, cooler and faster than previous x86 units, plus it will run iOS apps unmodified. All current Mac apps inc'l FCPX and Logic are already running on ARM, so those will be available from day 1 of the release.


Joe M. replied to the topic 'Empty file after selecting Share' in the forum. yesterday

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.


Joe M. replied to the topic 'Organization in large recurring projects' in the forum. 3 days ago

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!

In general try to avoid the tendency to over-categorize material using libraries or events. The limits of FCPX are very high. I have edited documentaries with 10,000 clips in a single event, using only keywords, favorites and rejects to organize the material. That worked well.

I also edited a large documentary on FCPX with 8,500 4k H264 clips in a single library, spread across just three events. This included 220 camera hours, about 130 multi-camera interviews, occupying 20 terabytes. Machine was a 2017 iMac 27 with several Thunderbolt 4-drive arrays.

In theory you don't even need multiple events -- you can perfectly well categorize and query material based on keywords. However events are handy, just don't over-use them. Current versions of FCPX can do library-wide queries so (unlike older versions) the events are not "hard fences" that prevent wide-scope queries.

You cannot do cross-library queries so that is an issue for archival queries. I think there might be a 3rd-party product which does this but I can't remember. Maybe someone else can.

You generally want to use a "lean library" so all media is imported with "leave files in place" and the cache is stored in a designated location outside the library using FCPX library inspector>Storage Locations>Modify Settings>Cache. This keeps the library very small and it's easy to back up by duplicating it in Finder.

That said, for a true archival situation there is the risk the referenced media trees accidentally might not be archived with the librrary. To avoid this some people make a final archival library using "copy to library". The library will be large but at least everything you need will be there.


Joe M. replied to the topic 'HEVC (H.265) files go black in viewer and timeline.' in the forum. 3 days ago

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.


Joe M. replied to the topic 'FCPX Crashes, freezes, kernel Panic... All of them' in the forum. 3 days ago

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.



Joe M. replied to the topic 'Sharing Failed' in the forum. 5 days ago

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.


Joe M. replied to the topic 'HEVC (H.265) files go black in viewer and timeline.' in the forum. 5 days ago

Buk wrote: ...When I worked in Final Cut Pro 10.4.6, I had crashed os at all...

Could you please re-state and clarify this?

There is an FCPX bug in handling some types of HEVC files which began with 10.4.7 on either Mojave or Catalina. We don't have an exhaustive list of what works and what fails. The 8-bit 4k HEVC files from a DJI Inspire 2 will definitely fail. I don't know about the newer DJI HEVC formats.

The failure is typically an FCPX hang or crash during playback and skimming, but also when transcoding to proxy or optimized media. In October 2019 I forwarded this info to Apple Pro Apps Support, along with all files needed to reproduce the problem.

In your case if it works after transcoding to optimized media, just use that. If you use proxies it will still have to read the original files for the final output and a problem might happen then.

Another solution is externally transcoding before import using Handbrake or other tools.


Joe M. replied to the topic 'Exporting video to Iphone' in the forum. 5 days ago

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.


Joe M. replied to the topic 'Apple Keynote WWDC New FCPX and ARM processors' in the forum. 6 days ago

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....

Greg, your post started me thinking. It appears the Mac ARM transition may be unlike the two previous transitions (Motorola 68K to Power PC, then to Intel x86), In those cases the CPU changed between CISC and RISC, but the system-level architecture did not change. E.g, the major functional blocks were CPU, memory, and a discrete GPU. It is possible the upcoming ARM transition may be different, but in a beneficial way.

The Fujitsu 48-core A64FX ARM CPU might give hints about this. It is specifically optimized for supercomputer use, but it does show that ARM architecture can scale to high-end Xeon and beyond. So desktop Mac users need not worry that future ARM-powered desktop Macs will be power efficient but slow. Indeed it currently appears there is no fundamental roadblock to making an ARM-powered Mac Pro which is considerably faster than the current 2019 x86 design.

If current trends in higher-end ARM CPUs are any guide, it it possible the overall system-level architecture may change over time. We might differentiate it this way:

Current x86 computer approach:
- Discrete CPU, GPU and memory
- Limited hardware accelerators (e.g, Quick Sync)
- Limited CPU cores, e.g, less than 16 on lower-end machines, less than 32 on higher end machines
- All CPU cores are symmetrical and "heavyweight", with good single-thread performance but high power consumption
- Scalability of CPU cores is hampered by energy cost of moving data around

Possible Future Apple ARM computer approach:
- ARM CPU may use on-chip memory, enabled by the smaller real estate of the CPU core
- Core scalability and power consumption greatly improved due to data locality enabled by on-chip memory
- Higher (maybe much higher) core counts
- Heterogeneous (not symmetrical) cores. Greatly expanded use of the high power plus low power cores used in mobile devices.
- The large flock of ARM cores if properly designed could eliminate need for a discrete GPU. E.g, A GPU is mainly a large # of lightweight cores. Given enough ARM cores a dedicated GPU might not be needed.
- Greatly increased use of heterogeneous hardware accelerators. Think of Quick Sync-like accelerators for many different tasks.
- Faster implementation of future accelerators. E.g, nine years after the debut of Quick Sync, Intel still won't use it on Xeon. If Apple wanted to add a hardware accelerator to their Ax CPU, they could do it immediately.


Joe M. replied to the topic 'Apple Keynote WWDC New FCPX and ARM processors' in the forum. 6 days ago

VidGreg wrote: Worlds fastest computer is now ARM based....

If you mean the IBM Summit supercomputer, it is the world's fastest but it's based on the IBM POWER9 CPU, not ARM. The POWER9 is the descendent of the PowerPC CPU used in Macs from 1994 to 2006. It has nothing to do with ARM or Apple Ax CPUs.



Joe M. replied to the topic 'FCPX Crashes, freezes, kernel Panic... All of them' in the forum. 7 days ago

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.

My gut feel is it's a lower-level system issue that simply affects FCPX more frequently because it more rigorously exercises the system layer. Since you totally reinstalled Catalina that could imply a transient, borderline or intermittent hardware problem.

My 2017 iMac 27 once began rebooting randomly, first once a week, then every few days, then every day. It passed all diagnostics. Then at the Apple Genius bar they finally ran overnight "bench diagnostics" and after 1-2 days it failed. The solution was replace the entire logic board.

That said, if you do a fresh OS re-install, I suggest using Mojave (see previously-posted link). While Catalina works fairly well (after 5 updates) its additional security measure can sometimes cause problems.

There is no "safe mode" to totally disable FCPX plugins. I think Apple realizes the plugin system needs improving which is why they are pushing plugin developers to move their products to FxPlug 4, which should make the entire plugin ecosystem more reliable. But that doesn't solve your current problem.

You could also try the free version of DaVinci Resolve which is fairly full-featured. That might be an interesting data point. If it also hangs that would imply a lower-level problem unrelated to FCPX.


Joe M. replied to the topic 'Anyone using Mediainfo to get specs of a video file?' in the forum. 1 week ago

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.


I prefer Invisor which uses MediaInfo internally. It has a "comparison mode" which uses a side-by-side spreadsheet-like display. From Finder you can drag/drop many files into Invisor and compare the specs: apps.apple.com/us/app/invisor-media-file...or/id442947586?mt=12


Joe M. replied to the topic 'FCPX Crashes, freezes, kernel Panic... All of them' in the forum. 1 week ago

Free wrote: I decided to erase the computer and start over fresh.
New last Catalina 10.15.5.
FCPX 10.4.8
Logic 10.5.1
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.
Or something...

Could it be one of the FXFactory plugins instead?

Well, those are interesting results. You have been very persistent, and I'm sorry about the continuing problems. Almost any plugin can crash or hang FCPX. The only 3rd-party audio plugins I have are from RX7 Advanced and I never use them, always use the stand-alone app.

Your last crash log implies FCPX crashed during a file manager call when attempting to create a directory (aka folder). There are known issues with Catalina permissions which some apps don't handle correctly, including FCPX.

Go to System Preferences>Security & Privacy>Full Disk Access, and make sure FCPX is enabled for that.

However even IF that is enabled, FCPX can nonetheless hang if trying to create a folder while in the library inspector>Storage Locations>Modify Settings>Media (or Cache)>Choose, and you try to create a new folder.

The workaround for that is first create that folder in Finder, then use Get Info>Sharing & Permissions, unlock it, and grant Read & Write to group "everyone", then click the gear icon and pick "apply to enclosed items".

That seems to prevent FCPX from hanging in that one case. But there may be other scenarios (maybe driven by an plugin) where FCPX tries to create a folder and crashes or hangs for similar reasons.

As a test you could try granting "everyone" Read & Write on all files on all hard drives. This might diminish some protections against malware, but it's only a test. If it doesn't immediately help you can restore the settings.

If you think it might be the FxFactory plugins, you could use the below tutorial for uninstalling it - just as a test. In general I've had good results from FxFactory support, so don't hesitate to contact them.

If experimentally removing FxFactory and making the above disk permissions changes don't help, another option is to re-install MacOS from scratch using Mojave. You can get that here: You can get Mojave here: support.apple.com/en-us/HT210190

Uninstalling FxFactory: www.youtube.com/watch?v=Zr_vEmyOp18


Joe M. replied to the topic 'MacBook Pro - Over Heating When Using FCP' in the forum. 1 week ago

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...

I have 2015, 2016 and 2019 MacBook Pros, and had numerous Windows laptops. All laptops in that same category are like that. Your 2019 MBP 16 is not over-heating and is working normally. In general the 2019 16" is better than earlier ones, but all high performance laptops behave that way.

Apple is attempting to address this by changing to ARM CPUs, aka "Apple Silicon". The first ARM MacBook will be out this year. We can then examine the difference it makes regarding thermals, battery life and fan noise.