✎ Latest Free FCPX Effects
Joe M. replied to the topic 'Sharing Failed' in the forum. yesterday

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

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

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. 2 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. 3 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. 4 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. 4 days 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. 4 days 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. 4 days 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.


Joe M. replied to the topic 'Best SONY FS7 Workflow' in the forum. 6 days ago

Tom Wolsky wrote: You wouldn’t still happen to have links to that media? I’d like very much to try it out. Thank you.

Tom if you mean me, the media I found is at the previously-posted Google Drive link. You should be able to download it from here: drive.google.com/open?id=0B2YfoQqKYTrTVDJ4WVd1d1dhZkU

It's a 1.1 GB ZIP file that contains a folder named "FS7 Card", inside of which is the usual folder tree and two MXF files. The larger one is 4k XAVC-I, and the smaller one 4k XAVC-L.


Joe M. replied to the topic 'Best SONY FS7 Workflow' in the forum. 6 days ago

Franke wrote: but this happens to me basically with every FS7 footage I ever got (i guess mostly with that same resolution and codec). I just feel its not that smooth for being on so modern machine and working off an SSD.

OK, I scoured the internet and finally found some FS7 test material I could download. It appears that 4k XAVC-I is relatively fast on my 10-core Vega 64 iMac Pro, but 4k XAVC-L is quite sluggish. This is regardless of whether they are imported using copy to library or "leave files in place".

I then externally re-wrapped both using EditReady2 and imported with "leave files in place". That made no difference - 4k XAVC-I was fast and 4k XAVC-L was very slow. That is often seen, since Long GOP codecs are typically harder to decode. There are exceptions such as Panasonics 10-bit All-I codec from the GH5 and S1 is very sluggish on FCPX, and their 8-bit Long GOP codec is faster.

If your FS7 material seems very slow, I suspect it is XAVC-L not XAVC-I. See attached output from Invisor which shows the difference.

I also tested both FS7 clips on the latest version of Premiere 14.3.0 on the same machine. Both were slower than FCPX 10.4.8, esp regarding lag time to JKL input. That was with Premiere set to 1/4 resolution.

I then tested both FS7 clips on the latest version of Resolve Studio 16.2.3 on the same machine and it was similar to FCPX - XAVC-I was fast and XAVC-L was sluggish.

In general with 4k Long GOP codecs you will need proxies or optimized media for the smoothest, most lag-free performance - even on higher-end hardware. There are exceptions to this and there is wide variation in how H264 material is encoded, how well the computer's hardware acceleration works for decoding, and how well the specific NLE leverages this.

But for the 4k XAVC-I and XAVC-L clips I tested, they followed a familiar pattern: the All-I clip was faster, the Long GOP clip was slower, FCPX and Resolve were much faster than Premiere.


Joe M. replied to the topic 'Best SONY FS7 Workflow' in the forum. 6 days ago

The info you posted says 1080p, but your first post said 4k. Which is it?

Also we still cannot tell the needed codec details. I suggest you use Invisor, which allows side-by-side comparison of various media files in a grid. After installing it, in Finder you do right-click on the file>service>Analyze with Invisor, At the top select the Comparison button. You can then click/drag other files in Finder to that window and view the characteristics: apps.apple.com/us/app/invisor-media-file...or/id442947586?mt=12

This will not only be useful for this case but in the future when people send you material you can examine it.

We need to know (1) the actual media file details, including whether it's XAVC-I, XAVC-L or what. (2) The resolution you are actually using, whether 4k or 1080p.

Using Invisor will tell us that. Or if that's too difficult, upload a small test clip to DropBox and post that here. We can analyze it and report back.


Joe M. replied to the topic 'Color Finale 2 Pro Crashing FCPX -Any tips?' in the forum. 7 days ago

truelife2 wrote: .. The developer told me this only happened on Mojave but when I upgraded to Catalina the problem continues.

Developers have the ability to debug this. They can examine crash logs, or send you a custom instrumented version of the product with additional debug code. They must take responsibility for their own code and aggressively pursue it.


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

Free wrote: - Is there a chance that having enabled server performance mode has done anything bad ?
- Trying to understand what amount of swap memory is too much (etrecheck).
- I’ve deleted all 3rd part kernels but why would they start giving troubles now when they’ve been working fine for 2 months after installing? LuLu has been running 100 % of the time.
- If I start a new project, why is FCPX keep hanging and being slow (beachball) if I don’t really have many plugins?
- Is FCPX super slow only by having a lot of plugins installed even if not using them?
- The whole idea of retaking this big library was to try and work with Proxy files to see if I could avoid all these slownesses… Way are there clip I can’t transcode to Proxy? Some only allow me to transcode to optimised...

You've taken a lot of methodical steps. Thanks for being persistent. You must be patient and continue, even though it is frustrating.

Do not make changes like server performance mode. That is unlikely to help and it introduces additional complications.

Use Activity Monitor's memory tab to check memory. If the memory pressure graph is green, your memory situation is generally OK.

Deleting 3rd party kernel extensions is a normal troubleshooting procedure if you're having kernel panics. If software that once worked OK would never crash, then we'd never have crashes. Software is extremely complex and the underlying internal state cannot be easily perceived. An airplane can have a design defect, yet fly for years before it crashes.

You have a lot of plugins installed, apparently including CoreMelt. While removing plugins from the timeline is a first troubleshooting step, they can still affect FCPX stability even if not used in a timeline. This is an unfortunate aspect of current FCPX plugin design. There is no FCPX "safe launch mode" which disables all plugin code. Plugins run within the FCPX memory space and any bug by any plugin can hang or crash FCPX. This will hopefully be fixed in the upcoming version of FxPlug 4 framework, but that is in the future.

The FCPX plugin ecosystem is also burdened by lack of consistency. There is no single standardized method of fully removing them. In some cases you must contact each plugin vendor to get "clean removal" utilities, which may not even be publicized. Just determining the version no. of the plugin can be difficult. Unlike MacOS which specifies all Mac apps have the "About" menu that states the version, there is no such consistency for FCPX plugins. For all these reasons, do not install FCPX plugins in a cavalier manner. Use only plugins from respected companies with good support. Make sure all plugins are updated to the latest version. If you end up not using a plugin, fully de-install it.

If you have FxFactory (like an App Store for plugins), you can run that and do Actions>Show FxPlug Plug-ins in Finder. If you don't have FxFactory just go there in Finder, which is /Library/Plug-Ins/FxPlug. Examine those and remove old or unused ones. See this Larry Jordan article. If anyone else has alternate suggestions on how to reliably remove plugins, please speak up: larryjordan.com/articles/how-to-remove-p...rom-final-cut-pro-x/

That said, a normal troubleshooting step is making a snapshot duplicate of the project, selecting all timeline clips with CMD+A, then remove all effects with Edit>Remove Effects, then examine behavior and see if the problem still happens. If yes, repeat that but do 1/2, then 1/4, etc. of the timeline until you find the problematic effect.

If the problem happens with no effects (as you imply by just creating a project), it could be a memory-resident effect or a lower-level system problem. The fact you're having many MacOS total system hangs and kernel panics imply there's a lower-level problem which cannot be fixed at the application level. Even if it doesn't hang or crash *today* doesn't mean that problem is gone.

Be double-certain that you aren't using Chrome or any browser based on Chrome, such as Brave, Vivaldi, etc. This is known to destabilize FCPX but it should not crash or hang MacOS.

If you cannot transcode clips to proxy that is abnormal. If the option is greyed out that implies proxies already exist or there's an FCPX database glitch. There is an FCPX data management bug which can cause this when copying clips or projects between libraries and if you answer "no" to the copy proxy dialog. That will disable ability to create proxies in the new library for those clips. The solution is delete all proxies (even if none exist), then re-launch FCPX, which should restore the ability to create proxies.

Starting with Catalina there are some disk permissions issues that can effect FCPX if using a designated storage location for media (inc'l proxies) and cache. In the library inspector if you do Storage Locations>Modify Settings>Media (or Cache), then try to create a new folder, FCPX can hang. The workaround is first create the folder in Finder, do Get Info, scroll down to Sharing and Permissions, unlock it, and grant read & write to user "everyone", then click the gear icon and select "apply to enclosed items". Only then use FCPX Storage Locations>Modify Settings.

Specific comments on your FCPX crash log:

- The crashing thread was thread #0. Note any thread in a multi-threaded process can crash the entire process. All threads have full access to memory. 3rd party plugins run as threads within the FCPX process.
- The crash involved" 'rateConformEffect' on invalid proxy object". This might be related to your inability to create proxies, possibly the previously-mentioned database issue. Delete all proxies and all optimized media, re-launch FCPX and try to re-create proxies. If not possible, state the exact behavior you're seeing.

The call stack of the crashing thread indicate the Event Browser was in filmstrip mode, a mouse drag event happened, a slide-back animation was triggered (probably normal FCPX UI), a share lock was requested (locks are used to coordinate activity between multiple threads), then an exception was encountered, maybe involving a Motion effect, then the exception handler kicked in to produce the crash log.

There are references to OZFxPlugTimingAPI. Ozone is apparently the Apple Motion render engine.

Keep in mind there are two separate problem layers. The system layer involving MacOS hangs or kernel panics, which cannot be fixed at the app layer. Then the app layer issues involving FCPX crashes which can be caused by system layer issues but sometimes we can reduce the frequency by following that trail.

It currently makes sense to pursue the proxy issue, review (and maybe remove) plugins. Then re-examine the FCPX behavior. If still a problem do the above test about a duplicate snapshot and remove all Fx from the timeline, then examine & manipulate that and observe behavior.

If none of that works you may have to back up your data, wipe the machine and do a clean MacOs install, then re-install FCPX but no plugins or only a highly curated set of plugins.