Hi.
I am curious to know how you deal with spaces in filenames (for imported footage). Apparently everything works fine, but since several versions ago (I can’t say exactly), the archive process is interrupted if the project have such clips . So I have to check the whole project, rename, reimport and replace it everywhere in flame, which is terribly tedious.
I was thinking of writing a bashscript (with the help of chatgpt) that would check and rename files.
thoughs?
Hi,
in the Logik Portal, you will find the script “sanitize names”. Add this to a custom shortcut and hit it every time you load such files into flame.
I frequently have spaces in names (I try to avoid them, but I don’t try real hard) and I never have an issue archiving. What I try VERY HARD to avoid is /,%,$,#,!,@ and &, which can really screw you up in many ways. I often have to sanitize the spot names clients send for delivery. Otherwise I’ll be screaming /%$#*!@&.
I was unaware of this. It’s great. Thanks.
This morning I have been trying to replicate the issue (2025.0.1) and strangely, everything went fine and flame archived correctly.
The truth is that this is a problem that has been screwing me up me for the last few versions, and I have 100% verified that this is the problem.
I wonder if it is an NFS/SMB thing?
I once had a file name, when I accessed the folder holding said file Flame would instantly crash.
I used to get that with the f symbol apple used to use for folders.
Yes, that is a known problem with filenames containing /,%,$,!,@ or whatever crap like that. It’s not really (for me) a problem, because I never use such characteres, and I rename immediately any file I found with wrong filenames.
I work with direct attach disks (internal raid5), not net shared volumes.
We use FreeCommander in Windows to pre-filter all the stupid names we encounter nowadays. I can’t tell the amount of issues that throws everywhere.
How did my comment become the solution? I haven’t seen that symbol used in nearly 20 years.
Oops, I didn’t even realize. Wrong click.
In the old days I had issues with those characters only on our linux flames. The mac flames seemed to be ok with it.
Hi. I tested this. If I´m not wrong, this hook only works for clip names within flame. It doesn’t rename for filesytem level from media hub as I expected.
If you’re on you could(I think), setup an Automator that will replace spaces and symbols since you can do this with the rename function in Finder.
That is about I was thinking. I prefer bash script, sure. Or better, a python hook.
If the media that comes to you is full of crappy filenames you can consider creating conversion tables and hard links.
This process is quick, non destructive and leaves a paper trail.