-
A list of FCP X frustrations…
-
That is show audio components, not expand. My shortcut for expand all is shift+E. Then shift+cmd+e to collapse all. Usually I’m working on a couple clips so I just expand all so I don’t have to select them or learn 2 different shortcuts. Expand all and collapse all. Occasionally I’ll expand 1 by double clicking on the lower audio half of the clip.
Ctrl opt s is audio components. A step deeper where you can see and adjust the channels separately. In there you can use the range tool to disable just parts of a clip, or turn off particular channels, etc.
-
Quintus,
A lot of us here have long held the opinion that the longer a person has been editing in another NLE, the more difficult a time they’ll have adapting to X.
It’s not ALWAYS true, but it’s very often so.
It’s clearly and unmistakably different from any other NLE. And so approaching it as if it’s going to react like another NLE will always be frustrating at best.
Many years ago, I was told that it takes most people about 3 months of immersion in a new environment to feel that it’s their “normal” one.
I suspect that’s pretty accurate. If you can manage to use it for 3 months (more or less to the exclusion of any other NLE) then I suspect that like most of us here – you’ll open your old NLE and literally be AGHAST at how slow, constraining and old-fashioned it feels.
But you’ve GOT to decide to take the leap forward and jettison your past reflexes – or just resign yourself to moving to Premier or another NLE that works within the older fixed timeline model.
You’ll be more comfortable, for sure. The question is what happens if X continues to catch on with those who value it’s speed, flexibility and internal database driven approach – will you eventually be at a competitive disadvantage because you couldn’t find the patience to adapt earlier?
Nobody knows that answer for sure. All I know is that it’s REALLY hard to locate folks who’ve truly become proficient at X who say they’d be happy going back to their prior editing software. There ARE some, of course, but very, very few from what I’ve read around the net.
YMMV.
Know someone who teaches video editing in elementary school, high school or college? Tell them to check out http://www.StartEditingNow.com – video editing curriculum complete with licensed practice content.
-
I agree with Bill’s observations and that reflects my precise experience. I know this forum is about technique so I will be brief. I had Initial extreme resistance to fcp x as I had become wedded to fcp 7. Several perfunctory attempts at learning fcp x did not help the situation. However, then I decided on deep immersion and there did come an a moment of epiphany when I internalised the new logic of the programme. It takes at least a month of really working at it hard. In particular, I had to develop new editing strategies to deal with the magnetic timeline before I could move forward. All I can say is that it was worth the trouble.
-
[Bill Davis] “you’ll open your old NLE and literally be AGHAST at how slow, constraining and old-fashioned it feels.”
I tried to edit something in Premiere CC a while back and I could hardly stand it. It felt like work!
Jason Jenkins
Flowmotion Media
Video production… with style!Check out my Mormon.org profile.
-
Thanks to you all for the suggestions, tips and encouragement. Moving into the FCP X world is truly daunting as it involves changing your mindset completely but I am determined to stick with it and learn!
As has been said here, it takes about 3 months to become familiar with working in a new environment and when you’re trying to earn a living on short deadlines the temptation to fall back to familiar territory is immense (in my case Legacy). But with the enthusiasm shown here I’m determined not to fall back to my old ways.
There is another issue that I’m finding on X which is killing me right now. When I hit the spacebar in the timeline, there is a brief pause before it starts playing and then again shortly after playing, audio continues happily along, but video will freeze and then pick up again. As you can understand, this makes editing quite frustrating (especially when you’re already climbing that learning curve!) when you’re not receiving immediate responsiveness from your GUI. I did a mavericks install over mountain lion and am wondering if that’s the problem. Anyone else had this issue?
Thanks again!
-
[Bill Davis] “A lot of us here have long held the opinion that the longer a person has been editing in another NLE, the more difficult a time they’ll have adapting to X.”
I know what you mean… I’ve spent 8 years in FCP 7 and am finding this change quite difficult indeed.
[Bill Davis] “But you’ve GOT to decide to take the leap forward and jettison your past reflexes”
Have made that decision thanks to all the great suggestions and encouragement I’ve received on the forum. Knowing that there are other professional FCP X users so willing to help makes a major difference. Thanks again!
-
My system Mac Pro 4.1, 16 GB Ram, Ati Radeon 5770.
-
I have exactly the same system, Mac Pro 4,1 (2009) and the Ati Radeon 5770 graphics card at work and experience the same sluggishness. However, I come home to my mid-2012 MacBook Pro (Thunderbolt) and don’t. I have the Full Monty new Mac Pro on order and CANNOT WAIT to have more fluidity under my fingertips!
NewsVideo.com
-
Just don’t my friend. Please look at some of the issues I posted. Create a large project with over 50 tracks and see for yourself.
-
Hi Quintus,
Everyone here already gave you most of your advice you wanted and I echo everything that is being said about FCPX and taking the time to learn it. After a while you will THINK in terms of: will I put this in the primary or Connected? And even more, after a while you will make better judgements more quickly (like with any program you get used to). Believe, I also came from 7.
About your sluggishness: I’m not going to pretend I know what the problem is, just tell you that we upgraded 3 retina MBP’s at work to Mavericks and FCPX and were getting awful performance (beach balls and the same pauses you mentioned). A clean install fixed it all…
I have heard similar reports from some other forum members.
Reply to this Discussion! Login or Sign Up