timeline just red

Oh, also, we proved it wasn't related to media (in my case) because I reproduced the issue with the media for the entire library offline. Just loading the offline project created the same issue.

I have had this problem in multiple projects, but happens mostly when I was use ProRes4444 exported from Motion for an animation with transparency. Somewhat embarrassing when the client is sitting in the room with you while you edit.

Compounding my troubleshooting woes was the addition of a new LG 4K monitor as my second display and my suspicion that maybe the new monitor install was causing the fuss. Maybe not enough cowbell in the system to run the new display?

iMac (Retina 27in, 2017)
(8 GB Video Ram -Radeon Pro 580)
32GB 2400MHz DDR4 Ram on board.
SSD Internal Drive.

Solutions:
I used Digital Rebellion's FCP Remover and re-installed FCPX. Seemed OK for a day, then the problem returned. I added an AAC Music track and FCPX crashed to the desktop. Maybe the music sucked too much to be in my project, When I restarted... Eye bleeding Red Timeline. After exiting I opened Digital Rebellion's Crash Reporter. It suggested I run HouseKeeper. which I did. It blew away all caches which I surmise is different from ditching your preferences.

After a week my timeline seems to be (255, 0 ,0) Free.

Maybe the answer... I don't know. Now If I could just figure out why my G-Drives can't send me 4K video over Thunderbolt without dropping frames... hmmmm

Hi all,

Long-time fcp.co reader and FCPX user here. I am experiencing this issue with now two distinct libraries and cannot replicate the issue consistently. Initially, when it happened, I created a new project (in a library containing many snapshots and projects). I went through the usual trashing of preferences, disk first aid, safe mode restarts, all to no avail.

Because I was on a deadline, I exported an XML from the working project (I can select projects and all my referenced media is intact) and then imported that XML into a new library. That fixed the issue for a few days and it returned last night.

Today, I am in the field with a client (on a different mac, different project) also running High Sierra and the latest build of FCPX, and it happened again.

This is incredibly disheartening as FCPX has been a workhorse for us, and we've never had an issue before, even when running gigantic, complex, projects.

I sent Apple feedback through the appropriate channels, and I hope the 10.4 release is truly imminent. Otherwise, I'm not sure what my options are.

Best,

Fabián
--
theunderstory.co