[Ron Hurtibise]

Love this, from the comments after the article:

“there is a lot of good and a lot of honest to god effort on Apple’s part these last five years but – and I think most of what was wrong has been addressed – but: the keyframing system is still a garbage fire. If you work in short form and you work regularly with little push pulls and type animations, FPCX is an unusable nightmare with the insane keyframing apparatus that appears like a leaning tower of piza over every clip you want to work with. If you make little keyframe moves all the time, the idea of doing that inside X is akin to wearing big rubbery gloves put on backwards. it’s just not a goer.”

[Ron Hurtibise]

Thanks, I just downloaded it and tried to run it but could only get the first 25 to 30 clips to export to a text file. My project has more than 700 clips using the Save As >Clips as Chapter Text command. Is there a way to export a list with all the clips and timecode?

[Ron Hurtibise]

Yes, I tried that last night. It didn’t work.

[Ron Hurtibise]

Thanks. I removed the Quadro (but not the drivers) but it still crashed. I’d hate to remove it permanently because it improves my Adobe CC performance and has no detrimental effect on FCPX 10.2.3

[Ron Hurtibise]

Oh well. Trashing all render files didn’t stop it from crashing after I load a previous project to the 10.3 timeline. Guess I’m going back to 10.2.3 until this gets fix\d

[Ron Hurtibise]

I’m using a 2010 Mac Pro with 16 G memory, Sierra, and two graphics cards: the supplied ATI Radeon and a NVIDIA Quadro 4000 for Mac. I updated to the latest available Quadro and CUDA. That didn’t work. Then I removed the Quadro (but not the drivers or CUDA) and it still kept crashing. I was thinking there might be a compatibility problem with the latest Sierra version and the Quadro drivers but when I’m not having any problem with these same projects on 10.2.3 with the same configuration and both cards

[Ron Hurtibise]

10.3 kept crashing every time I tried to load a project that was rock stable in 10.2.3. I trashed my preferences and unused render files as well as opened the application by clicking the library, but it’s been crashing every time. On the application forum, it was suggested that I also delete ALL (not just unused) render files. Will try that tonight and see if it works.

[Ron Hurtibise]

OK guys, I watched the first three videos in the Ripple Training package, plus the Working with Libraries video. And I’m still not wrapping my head around it. (I never worked extensively in Legacy, so I’m not familiar with Bins). In 10.1, I get that we’re creating Libraries, ostensibly to serve as holding containers for all elements associated with what we used to call Projects. And we can move those Libraries across drives or store them on network drives to enable shared access. Within those Libraries are Events. Events are created to store distinctive types of clips (Interview A, Interview B, B-roll, Exteriors, Music, Animations, Photos, etc.). Why, then, is it recommended that we locate Projects (or timelines) inside individual Events when Projects typically consist of clips from all of the Events? Why would I want to go into Event folders to access my Projects/Timelines? Shouldn’t Projects be renamed Timelines and placed in a Timeline folder inside a Library, separate from the Events? And shouldn’t Libraries have been called Projects, so that within each “Project” (Library) folder, we would have Timelines and Events?

[Ron Hurtibise]

Why would knowing which events are associated with which project have to be automagical? In 10.0.9, you click on the project in the project library and the properties box lists the events tied to that project. Is this still true in 10.1 when all projects and events are lumped into one big library?

[Ron Hurtibise]

Thanks for the responses. No, I don’t want to lop everything in one big library. And Bret, you’re right when you say there’s no true automated process. What I think would have been nicer would have been a simple option to have FCPX 10.1 create a new library with all connected events for each project in a mounted drive. Some events might be copied into more than one project library, but so what? Using Event Manager X to organize which projects and events are moved into new libraries still requires me to have a prior listing of which events are tied to each project. It doesn’t appear that Event Manager X detects which events are tied to each project, or am I missing something?