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.
I think I already mentioned it, but when troubleshooting a problem like this, don't use any external hardware like monitors, audio, or even bluetooth wireless headphones. Each item is an additional complication. Yes they should all work, but for debugging we want the system as simple as possible.
If possible don't even use an external hard drive. You might need that for real work but if the problem suddenly goes away when the drive isn't plugged in, that's telling us something.
O'my Free, what a headache:(
I'm really leaning towards hardware/chip issue.
As mentioned, booting from external drive and consider using Mojave as OS might show if issues persist to be hardware related.
I did see something in the logs you reported in response #108145 that I don't think I have ever seen generated by a system log and that is emoji being shown like here… /Applications/Coremelt/VTwinFx.app/Contents/PlugIns/VTwinFx.pluginkit/Contents/PlugIns/VTwinFx.fxplug/Contents/Frameworks/libjpeg.dylib
0x115a37000 - 0x115a98ff7 +libtiff.dylib (<img src="//daxfo0ox0rob7.cloudfront.net/media/kunena/emoticons/cool.png" width="20" height="20" alt="" title="" class="bbcode_smiley" /> <83125AD2-EF2A-3D84-B0A0-E9DEED49ABA7>
Screen shot of how it looks on my screen…
Several others are showing up. Anyone ever see this in a log file before?? Is this a problem?
Despite the re-install of Catalina, I think you may still have a corrupt OS install, maybe?? Fresh install of external ssd drive should eliminate that possibility, especially if you try Mojave.
One last diagnostic you can do is examine each crash/panic log and look for common crash links/causes. I am not seeing this with available info, but if the same causes show up then that will point to suspect process/code or even possible hardware.
As Guru says, if you have tried everything suggested here, then time to take to Apple.
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 is clear cut and no application is responsible 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 current 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. They now use a separate process per tab. 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 interprocess communication is fast and easy. The alternative is have a separate host process for the plugins and use a more difficult cross-process IPC method, which may have performance impact. However decades of software development experience has shown the "in processs" model of extensions is problematic from a reliability and support standpoint.
Hi there. so I decided to let go a week ago of editing video beacause it was too frustrating not being able to progress in the last almost month.
I just reading all replies since june 27th!
I don't know why I didn't see them earlier, I did check... I guess I'm still not used to the structure of the forum. (Oh, there are 2 pages of replies now! XD)
Anyway, thanks again for you unconditional and repeated support.
But I've been trying to edit a new video the last couple of days...
I started in iMovie but ended up sending it to FCPX, coulnd't help it.
The thing is it seemed to work well for a while, but then... Everything is happening again.
As I said, on installation a week ago, and with only the FXFactory plugins, FCPX crashed on me twice. Hanging also.
No Coremelt plugin or else, besides the FXFactory ones have been installed in this new fresh OS install.
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?
Last couple of days I didn't have any crash, but a couple of freezes.
The curious fact is that I also have problems with Photos app, I've even contacted Apple for that. If I try to move photos that I have edited in the Mac app, it freezes forever, 100% of the times. It also happens with a brand new library and doesn't happen in a new user. It also stops happening for a while (like a day or so) every time I reset the VRAM...
Finder has also frozen a couple of times.
Funny that I reinstall everything and stuff keep happening (doesn't make me really laugh...)!
Finally, today while having FCPX open (and hanged a couple of times, but kept working), I opened a few apps (when working, it happnes that you want to do some other stuff to be able to import it!), I was editing a pic in Photos app and Boum!
FP again, the first one since I installed everything fresh couple of weeks ago:
There are also "troubles" verifying one of my external drives (nothing related to FCPX work though) that's the oldest couple of years old 2 TB traveler HDD.
CleanMyMac can't do it sometimes. But no other problem than that.
Disk Utility can. (it's a 2 partition disk, FAT32 and Time machine).
At this point it could be quite a few things...
- A hardware problem that would only show up sometimes
- A Catalina bug
- A plugin bug that would enhance underlying troubles (I don't think it'd be causing all of it ATM)
- Some kind of problem with my user, that somehow has carried on with my files, since I have installed evrything clean
- Could also be some kind of problem with my external drives I guess (though I don't think it was connected with all this troubles)
I might have missed some.
In any cases, at this point, the next things I'd need to try are:
- Try to troubleshoot without ANYTHING attached to my computer, I can't tell for sure that there wasn't something connected while things happening, mouse, earphones, iphone, external drives)
-Uninstall all the plugins and start over again way more carefully indeed. (but I am not sure that this would mean Photos problems and Finder freezes would be then another whole problem)
- Change user (which seems redundatna after having reinstalled evrything just a week ago, but I do have troubles with Photos app that don't seem to happen in a new user...)
- Downgrade to Mojave (kinda sucks, I just upgraded from High Sierra, tht has been working for me for 2 years, but I wasn't doing ANY video editing, Logic was working without any of this troubles though)
- Take to Apple (not gonna happen) or simply wait til I can get a newer and nicer one. (And pray to binary gods everything will get solved by miracle then)
Plan is anyway to buy a newer nice 13" pro, though it might happen end of the year or early next year. I will be traveling until then, so won't be able to do all this troubleshooting with patience. Any advice on a setup that would give me a smooth and happy FCPX with lots of plugins flow and working with other apps flow?
sadly, that might also mean I won't be doing too much video edition until then.
You guys rock.
Even if it takes months to solve it, I'll update this thread.
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:
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.
Wow! Those are indeed exciting news!!
I've been wanting a newer and faster macbook pro for years now.
I was looking at the 13 MBP series, since I travel full time.
I actually left my 15" 6 years ago at home, sold it 4 years later without ever touching it again. Traveled 4 years without a laptop, then 2 years ago I got my Air 11", so 13" would already be a major upgrade in my backpack.
The only thing that was worrying me it's they do not come with dedicated graphics!
I would expect that if I spend 2-3000 bucks for a laptop (I wouldn't spare on specs, but only in size and weight), it should have that to be able to edit videos without any concern!
Still looking forward to do so, I had never needed that much power before, but video editing has made me decide for the leap.
I might wait for that 13" MBP ARM- bases model then instead of rushing to the last release. I'd be concerned though that the first model could have problems until they get it straight...
I guess I'll research and ask around when they get out not to make a mistake with such an investment, that would be a catastrophe.
Do you think the first MBP 13" release should be reliable enough?
Would they be more or less expensive than the Intel models?
I can't wait 1 or 2 more years though, this new computer has to come late this year or early next one. I guess then, if the fresh new ARM model isn't reliable enough, I'll just get a second hand couple of years old one instead and hang on for another couple of years.
I agree with FCPX.guru that some of the MotionVFX drop zone templates (though these are all the freebies) slow down the project quite a bit, but they're so cool and easy to use! I had to try and install them.
I'm gonna stick with the idea that all this KP come from problems that aren't related to the apps or the OSX, but I do thnk the constant hangs and freezes on Photos, FCPX and even Finder come from other layers.
Anyway, I'll keep trying and working with what I have.
Oh shoot! I just realised that I do have kernel extensions still in use...
So, I was using LuLu happily coz I found an open source alternative to Little snitch, but swithced to other apps to try and not have any kernel extension.
But researcing now, I see that all the apps that I could try use this system!
Little snitch, LuLu, HandsOff and Radio silence (the one I installed in this case), all do...
Is there any alternative without Kexts?
So I guess I did all this and still can't be sure that it isn't caused by having 3rd party Kexts...
Thanks for reading my replies and my poetic crash logs! XD
Do not buy the 13” MBP at this time. There are significant problems with FCP, macOS, and these machines with integrated graphics. Personally I would never buy a machine without a dedicated graphics card, not for professional work.
I agree with Tom. Ideally get a mid-level MacBook Pro 16, and there are some on the Apple refurbished site.
Re the ARM MacBook, the first one will supposedly be released 4th quarter of this year, but nothing is known about it. The speculation is it will be lighter, cooler, have much improved battery life, yet will be very powerful. It will run almost all iOS apps. But I have a 2019 x86 MBP 16 and it's very good.
Re Kexts, these will be further deprecated in Big Sur but supposedly will still mostly work. An x86 Kext won't work on ARM, not even using Rosetta 2 emulation. The developer will have to supply an ARM version of the Kext, but those (whether ARM or x86) will possibly not work after Big Sur. Developers will need to re-write their Kexts using different frameworks, which I assume will not run in kernel mode:
Well, this was helpful, bc just reading this lmk i am in way over my head. how annoying that I can't export an mp4 from FCPX. all other shares work. Just as soon as I clicked that "computer" button on the settings of Master File... CRASH.... over and over....Anyway, I just ran around my ignorant backhand and downloaded imovie, exported as my video as a .mov from fcpx, imported into imovie and exported from imovie as an mp4... one hour gone, but now I have the solution since I have very minimal to no understanding of computer speak. Is there a bug fix with fixing anything? another fixed version of fcpx available?
Olnance wrote: ... how annoying that I can't export an mp4 from FCPX. all other shares work. Just as soon as I clicked that "computer" button on the settings of Master File... CRASH.... over and over... Is there a bug fix with fixing anything? another fixed version of fcpx available?
If you are not on 10.4.8 it's probably best to upgrade to that. It has many fixes over older versions. If you are already on 10.4.8, and if FCPX is crashing (not MacOS), this should not happen.
If you have any HEVC media, there is a narrow case where certain variants of that codec can crash FCPX. If you are running the Chrome browser (or any browser based on Chrome) this mis-uses the Mac VideoToolBox framework and can crash FCPX. Do not run Chrome.
To locate HEVC media you can add a codec-specific search to Finder. In Finder do CMD+F, then change "Kind" to "Other", then pick "codecs" This will add a codec search to Finder. Then repeat that but select Codecs contains HEVC, and for search scope pick "This Mac". This will do a Spotlight indexed search of metadata in all files for those using HEVC encoding. If found and if used in an FCPX library, select those clips in the FCPX event browser, right-click and transcode them to optimized media. If it hangs or crashes during the transcode, then report that here.
If you are using any 3rd party plugins these can crash FCPX if they contain bugs. To rule this out, make a snapshot duplicate of your project, open that, select all clips with CMD+A then remove all effects with Edit>Remove Effects. Then try to export that.
If there is a bug in a 3rd party plugin causing FCPX to crash, inquire of the developer if there is an updated version. If you are on the latest plugin version, the developer will have to debug that. They should be able to inspect FCPX crash reports as a first step. Developers can also use the XCode LLDB debugger to remotely debug an application on your machine, although making a custom instrumented build of the software is usually a better approach.