Newsroom Update
Final Cut Pro transforms video creation with Live Multicam on iPad and new AI features on Mac. Learn more >
Final Cut Pro transforms video creation with Live Multicam on iPad and new AI features on Mac. Learn more >
Hi,
I've updated my MBP 15 to FCPX 10.4 & HighSierra and since then I can't work with Coremelt SliceX (and some ohter coremelt product). I'm in contact with coremelt but they say the plugin was updated and should work.
I also have really more crash like for exemple with psd files.
I try delete pref, re-install plug-in and usual first fix but no change.
Does somebody experience the same kind of problems ?
cheers
seb
Final Cut Pro X, Mac OS X (10.7.1)
Found the problem :
it's a 10.3 bug that happen with some Macbook pro (mine is a 201 15" touch bar) that are plug into a Thunderbolt display 27" and closed. If the macbook pro is alone it works, if it's open on the 2 displays it works...but if macbook pro is closed and you start fcpx and apply any coremelt plugin... it crash quit fcpx.
Found the problem :
it's a 10.3 bug that happen with some Macbook pro (mine is a 201 15" touch bar) that are plug into a Thunderbolt display 27" and closed. If the macbook pro is alone it works, if it's open on the 2 displays it works...but if macbook pro is closed and you start fcpx and apply any coremelt plugin... it crash quit fcpx.
I use Cormelt's X products all the time, not having any issues. If you're getting crashes with other thing, also, then it's probably not the plugin, but something else on your system.
What PERCENTAGE of free space is left on your drives?
Hi BenB, Never had problems with coremelt products that I use for years but all start after moving to HighSierra & 10.4. I try all sort of things, re-install FCPX, re-install SliceX, still not working. all other plugin have no issues. 200 Go empty space on SSD MBP 2016...
very strange...
Mac OS 10.13.2 with FCPX 10.4
MBPro 2016 with apple 27" thunderbolt display
Unfortunately it looks it still there on my configuration..
at least I find a way to work by just letting the MBP open until apple fix this...or I buy a new display..
thx
Are you running 10.3 or 10.4? And what version of the OS?
I believe this happened in 10.13.1 with FCP X 10.3.4, but 10.13.2 and 10.4 should have fixed it.
Can you report this to feedback? This was supposed to have been fixed in 10.4.
Yes, my contact at FCPX support is doing so.
with OS 10.12 and FCPX 10.3 I had no problems.
FCPX 10.4 & High Sierra crash with sliceX
