[Mark Smith]

What I tend to do is keep my amount of keywords rather small. So if I am logging interviews the subject name will be a keyword e.g.: Nina. Then if I like something Nina says, I’ll select that range where she says that pertinent bit in the browser, keyword it Nina and then to the right of the keyword in list view there is a field where I can type in a note which will be a text note about what she said.
So what this allows me to do is a search on the text in the note field which is fast or I can select the keyword collection for Nina and see the list of all the things she said that I thought were of use. I like keywords, but I have found that too many of them make for poor project organization and clutter. Better to throw terms you want searchable into notes field and use keywords to filter a more general set of things such as interview subjects, ‘exterior b roll’ ‘scenes’ etc.

[Mark Smith]

Part of answering questions is trying to figure out what people are actually trying to do with an app… So if you are looking for persistent tags, you could tag video clips in the finder and then tick off the “keywords from tags” in the import window so when you bring in your clip it will automatically be keyworded with the tag you have given it . You would need to test if the tag persisted with the file after export from FCPX.

[Mark Smith]

Select an edge of your clip with the trim tool and use the period . and , keys to trim or extend one frame at a time .

[Mark Smith]

Since you don’t mention what your camera original format is , its hard to make some determination as to what the best work flow would be. Some camera formats you can go through your clips in the import window and make selects right there and “import selected” .

Also – in the import window do not check off the optimized media option which turns your camera originals into pro res files, which increases their size.

If you are importing some QT movies then you might need to use VCC to allow you to make selects inside the whole QT movie clip. Without VCC you’re left with importing a whole QT movie clip as your only option.

[Mark Smith]

Is the Apple Solar farm in Az going to suck up all solar energy in a given area and hurt agriculture like it was feared to do in North Carolina?

[Mark Smith]

I don’t use plural eyes, but I have been syncing clips in X. I had about an hour audio record with small shoot I did which had more camera stops and starts than I realized.

I did have common timecode on audio and camera. What I had to do is basically sub- clip the audio record, favorite the audio sub clips and named those clips so that they matched the camera clips. I was having trouble selecting and syncing the audio sub clips to the camera clips in the list view but for whatever reason once I switched to the filmstrip view every clip sync’ed just fine.

[Mark Smith]

I ran into a similar situation recently with some audio clips that were much longer than the video clips. I narrowed the audio clips down to a similar range as the the video clips and compared camera scratch audio with recorded audio to make sure I was in the right ball park and then synced slips from there and that worked for me. This doesn’t answer your waveform question but sort of addresses your other situation.

[Mark Smith]

If I were a betting man, and I am sometimes, I would say that given the timeframe between the NDA’ed exhibit on at NAB and this next badass update to FCPX that hasn’t emerged yet, that yes an up grade to Sierra might be a requirement for the next version of FCPX. I’m maybe wrong on this but my gut feeling is that I’m not.

[Mark Smith]

Arctic whiteness- Library manager app. Among other things this app will tell you where the hell everything associated with a library actually is.

[Mark Smith]

The only clue I have so far is that when importing XF-AVC files from C300 mk2 , the clips come in without a problem but the associated files with each clip, the thumbnail, the xml, and a .cpf file are not recognised by X and are not imported… If the XML were recognised maybe the correct fields in the inspector with reel and take info would be populated? This problem might be a X – Canon XF AVC issue which may be addressed in the FCPX update code named “Godot”.