- Posts: 122
- Thank you received: 2
3 Post Moderation Rule for New Boarders (25 Jan 2021)
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
File name/rename
I know this can vary from different kinds of footage, AVCHD, H264, but I’m trying to find some “rules” or guidelines for a client, who needs to locate media-files on finder level, regardless of event or projects, and therefor needs to know the behavior and renaming.
So when I make a Event, import media, and load from a flashcard (this one was a Canon EOS) chose a clip and click import, it will name the clip FCPX as date/time when the clip was recorded, even if I can see the clip inside the import menu as MVI_0001?
If I drag the clip from the card and in to FCPX, it will be named MVI_0001!
When and why will FCPX do like that? (Renaming the file)
Its only happening from some raw footage, a BRAV for example, but not on mov files!
Is there any way to make FCPX keep the filename all the way, or can anyone help me out to get an overview on the matter?
Thanks
Please Log in to join the conversation.
- DudeMeister
-
- Offline
- Senior Member
-
- Posts: 47
- Thank you received: 2
Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
Please Log in to join the conversation.
- DudeMeister
-
- Offline
- Senior Member
-
- Posts: 47
- Thank you received: 2
Simply change the default naming preset of set up your own and apply it after import. Of course a simple "reveal in Finder" will always tell you what is what on the Finder level if needed. Which is why I'm not sure I understand the "problem".
Please Log in to join the conversation.
there is a list, and if I drag Original name from Camera on top, that must be preset?
but even then it dose the same, naming the file with date
and if I change the filename inside FCPX, it will still be the same in the finder, the name-change don't effect on finder level ;(
Please Log in to join the conversation.
- DudeMeister
-
- Offline
- Senior Member
-
- Posts: 47
- Thank you received: 2
I would imagine it's a precautionary measure, since any number of cameras could have identical naming conventions and you wouldn't be able to import some files due to duplicate name conflicts. So either way SOMETHING would have to give.
But again, I don't see why that's even a problem once they're in FCP, where you can name them anything you want. You don't want to be fiddling with footage on the Finder level either way, since that could REALLY mess things up!
Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.
- DudeMeister
-
- Offline
- Senior Member
-
- Posts: 47
- Thank you received: 2
And I actually just confirmed my suspicion btw. Apple obviously didn't do it the way they did just for shits'n'giggles, but because, unlike previous versions, all the media lives in the same folder no matter what, remember? With 7 media could live wherever. Guess what that means...? Exactly, any potential name conflicts are avoided (that weren't possible/an issue on the Finder level with 7) with the renaming. E.g. if you import from two identical DSLRs with the same settings. So feel free to fill the feedback page on the matter as much as you want. Never mind that NLEs such as Avid and Media100 do it only vaguely different. Again: guess why.
And guess what, if you in fact had two clips with the same name, what yould you have to go by to figure out which is which? Hmmm... maybe date and time?
And how exactly is one cryptic, nondescript number better or more useful than another cryptic, nondescript number in the end anyway? :huh: Not sure I follow that logic.
One might try not to apply FCP 7 habits to the matter, where its comparatively crappy organisation and TAPE based workflow obviously depended on a decent nomenclature that much more. But then that's exactly what X's renaming automation is for, if that's so important. In which case there's always the "Original Camera Name" option for that exact reason, since obviously that information is saved to the clips metadata. Which boils down to one whole click. Gee, bummers. Okay fine... maybe Apple should pamper us and remove that one click? (which still wouldn't change the need for the renaming in the Finder, but never mind)
So again... what exactly is the problem? And I don't even mean that question in an incendiary way, I just honestly don't get it. Because it's not wrong nor necessary or "crap", it's simply different for a good and logical reason, as with so many other aspects of X.
Please Log in to join the conversation.
First of, I LOVE FCPX, and have not used anything else for the past 2 years, and I fully understand the workflow and all the benefits of the metadata.
But I also understand the difficulties in having 8-12 VJs with different cameras, to load, edit and output small films 24/7 on the same fiber network (not SAN) needs an easy and not complicated workflow
The client got many workstations, and wants to organize media in a simple folder system, and wants to be able to put ORGINAL MEDIA in theses folders, and at the same time be able to put media in the folders form different Event on the fly, but give non FCPX users access to the media files on finder level as well
We need collaborative workflow, need to share Events, Projects and media files, why we go for the sparse-bundle workflow, every new Event and projects will be in its own sparse-bundle, but the media will be somewhere else and will reference aliases in the current Events original media folder, and not media files.
And if someone else needs to find files on finder level, and the VJ has renamed the file inside FCPX to original clipname (MVI_0001) witch is quite a lot easier to overview if you got 50++ files
MVI_0001
MVI_0002
MVI_0003
MVI_0004
rather than
2012-11-07 11:30:14
2012-11-07 11:30:42
2012-11-07 11:31:16
2012-11-07 11:31:48
In my mind it is at lot easier to see
Then someone needs MVI_0002, and try to find it in the finder that will never happen, because the filename on the original file is 2012-11-07 11:30:42
I know that basically we needs some CMS, but I don’t see any solutions that provides functions yet, someone thinks that something will happen in next update, but today its not (as far as I know) not possible
Another issue is resources, this is not a broadcaster, and they don’t got the money to do it “right”, buy an expensive system who needs dedicated manpower, they want an “open” platform for anyone to use with ease, and im looking in to FCPX to see if it can solve the task, they need some kind of system with ingest and fileshare, and here it would be nice to have control over the media files 100%, even if I recon the use of metadata I think is very very unfixable, just like the lack of an “force relink” feature very strange and stupid.
Hope you understand the situation, English is my second language and this shit is complicated to write
Please Log in to join the conversation.
BenB wrote: That (setting a name preset during import), you can't do. I've filled out the feedback page about this. I find it very necessary. That date/time crap they're forcing on us drives me and many others insane.
^ Yes! I can't agree with this comment enough. I liked being able to change the names in the FCP7 Log and Transfer window and having them stick. I also liked being able to rename the file in the finder directly from FCP7. I really want these features returned in FCPX. I remember Ronny arguing a while back that it's so much better the way it currently is.
Please Log in to join the conversation.
- DudeMeister
-
- Offline
- Senior Member
-
- Posts: 47
- Thank you received: 2
One more time: then copy the clips in the Finder first and put the media anywhere you want just as you describe. Then import it into FCP without copying. Big deal. Again, I don't know what the problem is, other than you wanting to work counter to the way it works and creating one for yourself, sorry. Every app has its Best Practices. X is no exception.
Especially since you have to copy first no matter what if you want to do what you describe, and the scenario wouldn't be the least bit different in any other NLE either. So saying that this is somehow a "problem" makes no sense. Because if you import directly from SD or the camera, then
a) it will HAVE to copy to your event, no matter what
b) will be renamed for the reason's described above
So taking that route would clearly be completely contrary to what you need, so why would you do it?
I would have thought that it was pretty clear that that was your only option. Copy in the Finder first. Because the system isn't going to change anytime soon, for obvious reasons. Media management at the Finder level is changing with the next version anyway, so you can even forget about the whole sparse thing, too. Or set up a Cantemo server. But even that won't change anything noticeably as far as your ingest workflow is concerned.
And if you actually think you can draw ANY parallel's to the way things worked in 7 and a TAPE based workflow, then you clearly aren't getting it, Redifier. You want a specific nomenclature in the Finder? Get "A Better Finder Rename" and do the work before you import. Done. Even less work than you ever had in "superior" 7 and still 2x or more faster.
Please Log in to join the conversation.
What I mistook for upset, is that your tone is a bit condescending, and that offends me a little, but it's probably just me who is a sissy :blush:
But I did forget to mention, that the one of the features in FCPX they use a lot, is edit NOW, mount the SD card, import, wait max 30 sec and your editing, while the files moving/transcoding, and that need to be in the current Event, then the media files will be placed in the sparse bundle and not on the mediadrive
the copy time counts, and there is no one to “clean up” and move/copy files later, or every Friday or what have we.
I’m just trying to find a workflow that fits the needs of this place, because I’m sincere interested that they continue to use FCPX, rather than switch to PP or Avid (where they will have the same or bigger problems and pay times 10), but all the negative wipes still goes with FCPX, and they blame the “new” I would love to prove them wrong
And just for the record, you haven’t seen me praise and miss FCP7, I get tired and in a bad mood every time I launch it, but my thoughts’ about workflow don’t need to be wrong because its not the same as yours, if I miss a feature in FCPX, I miss it, and that don’t necessarily mean that I have totally missed the point of everything :blink:
Please Log in to join the conversation.
- DudeMeister
-
- Offline
- Senior Member
-
- Posts: 47
- Thank you received: 2
Copy (archive!) your footage first via the Finder... problem solved.
Please Log in to join the conversation.


