FCPX UI instability- is it just me?

[Peter Ochs]

Yeah- just apply the “Straight Outta Compton” Filter and and it edits the music for you.

(I heard the “Eazy-E” Filter might be a little buggy, though…)

Peter Ochs | Editor
MacBook Pro 2.7 GHz Intel Core i7 16 GB RAM
FCP X 10.1.1
OSX 10.9.2

[Charlie Austin]

[Peter Ochs] “In general music editing is cumbersome in X. It’s a shame with the advantage of subframe editing, but some of the current limitation of the magnetic timeline are problematic. Compounding the music edits is one work around. But then you have to “step in” to that every time you wanna edit the track. Seems clunky.”

I actually feel like cutting mx is easier in X. Chop away as connected clips A/B style, then just select the bits and put ’em in secondary A/B story lines to make them “stay put”. No need to step into a CC to tweak the cuts. And you can still cut the secondaries if you need to pull up or extend a section. Agree that being able to use I/O KB shortcuts on a selected clip/storyline would be nice.

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Chris Harlan]

[Oliver Peters] “With Apple buying Beats, maybe we’ll get the new and improved Dr. Dre mixing panel and music editing module in FCP X. ;-)”

With lots and lots and lots of bass added to anything you might be working on.

[Alban Egger]

There is a bug in the EQ right now. It indeed often defaults when you reopen it.

Waveforms: do you have enough RAM ? 16 GBmin! And when you import clips FCPX takes a while “rendering” the waveforms, although the import is basically done. When you cancel X while this process is still working, then you might have your issue.

Beachballs: when I use a fast RAID I never see it. When I use FW800 drives they occur often.

[Gary Huff]

[Lance Bachelder] “CHEF, which opens this weekend was shot ALEXA in Pro Res for cost and time constraints. I’m sure it looks great on the big screen.”

Yep, been dealing with Alexa 2K ProRes 4444 footage this week and it’s gorgeous.

[Jason Porthouse]

[alban egger] “Waveforms: do you have enough RAM ? 16 GBmin! And when you import clips FCPX takes a while “rendering” the waveforms, although the import is basically done. When you cancel X while this process is still working, then you might have your issue.

Beachballs: when I use a fast RAID I never see it. When I use FW800 drives they occur often.”

Hi Alban, yes to the RAM – 20 gigs at the moment. It’s not the rendering – its that skimming the clip plays audio that doesn’t match the waveform under the skimmer at that moment. So I use skimming for fine audio edits – it’s great tp be able to rock back and forth over audio slowly to get sub-frame accuracy. But there’s a disconnect between what your seeing on screen (using the waveforms for a visual guide) and what’s heard. It makes for a confusing experience until you learn what to trust (the waveforms NOT the audio)

Beachball wise – it’s a Thunderbolt G-Raid so no issues there. It starts to get worse after 3 or 4 hours – move a clip in the timeline – beach ball. Raise volume – beach ball Basically any action will cause it – then it may be OK for 5 or 6 actions, then back again. Quit and restart seems to cure it for a while. I think it’s doing something to the database and that’s locking up X in the meantime. But that’s just a guess.

_________________________________

Before you criticise a man, walk a mile in his shoes.
Then when you do criticise him, you’ll be a mile away. And have his shoes.