Activity › Forums › Apple Final Cut Pro › Blog list FCPX positives and bugs
-
Blog list FCPX positives and bugs
Posted by Craig Seeman on July 2, 2011 at 3:38 pmBlog list FCPX positives and bugs
https://fcpxquirks.tumblr.com/One person’s catalog of good things as well as bugs. Nice posts in detail as he experiences them.
Paul Jenkins replied 14 years, 7 months ago 5 Members · 6 Replies -
6 Replies
-
Alban Egger
July 2, 2011 at 10:38 pmHe/She does a great job identifying certain problems especially with compound
clips in a very fair and constructive way. Good stuff. -
Craig Seeman
July 3, 2011 at 2:56 pmIt’s good to see someone do that kind of workflow analysis.
The quandary over Keywords vs SubClips is one of the most interesting design discussions I’ve seen about FCPX.
He wants the Keyword to be the visible name of the clip as it could be with a subclip.
The problem is,on the other side, if you have lots of clips with the same keyword (Interviews for example), I’d might prefer seeing the unique source clip name, if they are coming from different clips. Although the clip name may not have a meaning full description, at least I could tell them apart.I’m not sure what the best answer is given the context of the GUI. Any solution I can think of has the potential of walking into another area of confusion depending on how used.
You could easily be in a situation where you want some clips to show keyword test and others to show the clip name, possibly another means to ID the clip so as note to impact keyword names or clip names.
I wonder if there should simply be a separate name field and a key command to draw the name from keyword for the given clip so it’s not global.
-
Jerry Hofmann
July 4, 2011 at 8:44 pmThe Event library and it’s contents are one the most interesting changes in this software. There are things taken directly from FCP 7 too. There are searchable columns hidden just as they were in FCP 7 for example.
I suppose you make one little keyword for how you want to organize anything you’re doing. But you need a keyword for every clip. But it’s all in the keywords for sure. Finding clips once done seems fast here.
Jerry
Apple Certified Trainer, Producer, Writer, Director Editor, Gun for Hire and other things. I ski. My Blog: https://blogs.creativecow.net/Jerry-Hofmann
Current DVD:
https://store.creativecow.net/p/81/jerry_hofmanns_final_cut_system_setup8-Core 3.0 Intel Mac Pro, Dual 2 gig G5, AJA Kona SD, AJA Kona 2, Huge Systems Array UL3D, AJA Io HD, 17″ MBP, Matrox MXO2 with MAX – Cinema Displays I have a 22″ that I paid 4k for still working. G4 with Kona SD card, and SCSI card.
-
Eddie Mcfly
July 8, 2011 at 6:37 pmHey Craig,
Great article, it really helps to see pros actually using the app. talk about it’s pros and cons.
In regards to your sub clipping issue where you couldn’t seem to get your keyworded ranges to be named what you wanted in the timeline:
I do a lot of interview stuff as well and figure out this workflow that may work for you:
1) in the event browser clip mark your range – section you want to name “bob talks about his 401K”
2) Make this range a Compound Clip using Control Click > New Compound Clip or opt. G
3) Name the clip range whatever you want
4). Place this compound clip (and all others about bob’s 401K) into a keyword collection
5). Edit the Compound Clip into the TL and it’s got your custom name on itThis has worked great for me to see interview themes at a glance in my TL. Give it a shot 🙂
-
Paul Jenkins
September 11, 2011 at 8:51 pmHi Eddy,
I’ve been testing your technique. Very nice to have the description displayed in the timeline. But, unless I’m missing something, when one creates the compound clip one breaks ability to ‘Reveal in Event Browser/Finder’ and also to check the original source.
Even if one manually finds the compound clip in the Event Library, there still appears to be no way to identify the original source(s) from which it was created.
I can see that this might be problematic down the line in an edit when searching for more material to build a sequence from a particular reel/roll.
Did you refine your method in any way to accommodate these issues?
I guess one possible workaround is to include the source name in the name of the compound clip, but this seems to be laborious…Thanks,
Paul
Reply to this Discussion! Login or Sign Up