Need help brand new 2017 Imac fresh install of latest Final cut the issues that keep occurring can be seen in the attachment pics any idea how to solve this? it happens after every time I zoom in and out on timeline
If this is a brand new install, follow these steps:
1. Reset you FCP X preferences. Close FCP X and launch it again while holding the ALT and CMD keys pressed down. You will get a message asking if you want to delete the FCP X preferences. Confirm and let FCP X launch. See if you still have this glitch. If this doesn't help:
2. Remove FCP X from your computer and re-install the app. If this doesn't help:
3. Create a new admin user, then launch FCP X with the new user and check if you still have the problem. If you still have the problem, report back.
Hey Ronny, thank you for your help I have tried all of the tips you gave me above and I'm still running into the same issues. I don't know what to do about it I'm at a complete loss. please see attached photos of my trippy unworkable timeline as before and the spaces of my Mac.
On my old MacBook 2011 Final Cut works fine the reason I upgraded was because the Mac is slow.
I've never encountered a final cut issue like this before so any other advice please please help
This is indeed strange behavior. Looks like corrupted cache files, but there seems to be an UI related issue as well. Unfortunately such a problem is hard to troubleshoot without actually being at the computer.
Can you download and install Teamviewer (free) on your iMac?
I can then log into your computer to check a few things.
rgpearson wrote: ...I'm also using a new 2017 5k iMac (580 GPU), so I wonder if it's an issue with the AMD GPU drivers. I never had this issue with my 2012 iMac (Nvidia GPU).
I have a 2012 and 2013 iMac with nVidia GPUs, and top-spec 2015 and 2017 iMacs with AMD GPUs, plus 2015 and 2016 MBP with AMD GPUs. I have never seen any stability problem like that described by the OP attributable to the AMD GPU or drivers.
The OP had a hardware failure, not a driver problem. We don't know what component failed -- it could have been VRAM.
Yeah I was just speculating, maybe it's more likely an FCPX bug since the prefs deletion fixed it (for now anyway). Or maybe my iMac does indeed have a hardware problem, guess we'll see how it holds up in the coming weeks.