• Apple Final Cut Pro

  Keyword oddity – bug?

  Posted by Thomas O’carroll on November 20, 2012 at 4:45 pm

  I’m seeing a strange thing when using keywords and I’m wondering if I am alone in struggling with this.

  In a certain situation I cannot make a selection or make IO points on a keyword clip.

  set up:
  select a clip and assign a key word to the the whole thing (keyword e.g.: “interview”
  Now make three selections in the clip and give each one the same keyword e.g. : “answer”

  Make sure you have clips in the “list view” – not “filmstrip view”.

  I now have two keywords in my event list: interview and answer.
  When I click on “interview” I see the entire clip
  when I click on “answer” I see three clips – now looking at those three clips…
  If I select the third clip in the “answer” keyword group, and decide I want just a few seconds from it I will want to make an I/O selection. As soon as I lift my mouse from selecting – or after I have pressed “I” the selection in the clip list swaps to the first clip in the list. This clip now has its associated keywords revealed (interview and answer) with the keyword “interview” selected. The intended selection has disappeared because I am now looking at the first clip preview strip.

  If I remove that all encompassing keyword “interview” then all works fine.
  If I make I/O selections in the filmstrip view then all is fine too.

  Am I missing something here?

  (I must admit that I have posted this question in the Apple forums… please let me off this once 😉

  Thomas O’carroll replied 13 years, 9 months ago 2 Members · 2 Replies
• 2 Replies

• 

  Tom Wolsky

  November 20, 2012 at 9:44 pm

  It’s a bug.

  All the best,

  Tom

  “Final Cut Pro X for iMovie and Final Cut Express Users” from Focal Press
  “Complete Training for FCPX” from Class on Demand
  Class on Demand DVDs “Complete Training for FCP7,” “Basic Training for FCS” and “Final Cut Express Made Easy”
• 

  Thomas O’carroll

  November 21, 2012 at 10:14 am

  I take it you mean its a known bug that Apple will need to fix – rather than some some freaky conflict that I should be able to fix.

  Thanks for the reply Tom.

  cheers
  Tom (also)

Reply to this Discussion! Login or Sign Up