File naming on import

[Jeremy Garchow]

Surely.

Select all the clips you want to rename (this only works for the clip name inside FCPX, and does not rename them in the Finder).

Open the inspector, click the info tab, on the bottom of the inspector there’s a drop down called “Apply Custom Name”, choose the first in the list, Clip Date/Time.

You can even edit those specs and create your own string if you’d like.

Jeremy

[David Mathis]

I wish there was a way to create keywords in Resolve, use the folders in the media pool as events and have that carry over to FCP X when editing. I bring this up as I mainly shoot raw, render out in ProRes with same resolution as the raw files and send it to X for editing.

camera operator | editor

[Brett Sherman]

It’s really for file management and easier relinking, so it needs to be at the Finder level. Sounds like the answer is “No”.

[Jeremy Garchow]

FCPX can now import native AVCHD files, so that means you’d have to break the card structure of the AVCHD files.

You can use something like A Better Finder Rename and import the renamed files to FCPX: https://www.publicspace.net/ABetterFinderRename/

I’d be careful with that as you won’t have a proper AVCHD structure anymore, but maybe that’s not important to you?

Jeremy

[Darren Roark]

Yeah, it is unfortunate that they don’t offer a way to have it either way. When I adjust time and date created there is an option to also change the files as well.

I use A Better Finder Rename, it’s pretty great as you can quickly add sequential suffixes or prefixes, remove things from multiple files, pretty much anything you can think of.

It would make roundtripping much easier if we could just change the file names in FCPX though.

[Richard Herd]

[Brett Sherman] “the Finder level”

And now I propose the über David Lawrence media management technique. Recall previously he stated he plans to use FCP for the key words, then Xto7, then XML to Premiere. For finder level support, try using Prelude first!

Dump the camera archive somewhere. Ingest it into Prelude (transcoding as necessary), batch rename in Bridge. Import into X

A brave new world.

[Paul Neumann]

I prefer ingest with Prelude with custom batch renaming (no transcoding) send to PPro.

[Darren Roark]

[Paul Neumann] “I prefer ingest with Prelude with custom batch renaming (no transcoding) send to PPro.”

I agree, Prelude is really useful.

I’m just trying to see if I can live without the subscription with Adobe alternatives. If my workflow does suffer for it, I will sign up, it’s been pretty smooth since 10.1 came out.

[Dennis Radeke]

Well, I like Paul’s suggestion best (‘cuz it uses Premiere Pro!) but Richard is right on…

You can ingest (transcode or not depending on your preference) and do a batch rename that is custom and saved as a preset directly in Prelude. It’s pretty easy to set up. The only nagging thing for me personally is that it doesn’t allow spaces in the names, so I am in the habit of using an ‘_’ in place of a space.

Bridge is superfluous in this case but a great tool for batch renaming.

HTH – Dennis

[Gary Huff]

I have to say that I prefer the approach Darren outlined, mostly because I use a lot of ClipWrap, and I do that for two reasons.

1) Makes skimming through clips in an AVCHD on the Finder level far more manageable. The QuickTime interface for AVCHD folder structures is very poor. It’s fine as it is, but the simple fact that you have to start from the beginning to go through clips every single time is really bad from a time-management perspective. So it’s nice having a straight up listing of QuickTime files that one can easily parse through.

2) As far as I know, FCPX still cannot correctly interpret 30p footage from a Canon C100 (it’s 60i with 2:2 pulldown applied but the flag for the pulldown is wrong or something). I do a lot of 30p work, so this makes sure I don’t get any interlacing.

So ClipWrap the AVCHD archive, then use the Better Finder Renamer. I totally sympathize with the annoyance of 0001, 0002, and so on naming convention of this format.