We’re trying to get to the bottom of why stills (so far) imported through the Mediahub sometimes have the case of bits of their pathnames change.
/Volumes/lucid1/12345_job/Finish/supers/FLAVOR/logo.png
somehow became
/Volumes/lucid1/12345_job/Finish/supers/Flavor/logo.png
and Flame loads the 2nd logo.png as solid black.
Spicy, eh?
Anyone else seen this?
2026.2.2 on Sequoia running LL Classic.
Linux is strictly case-sensitive. /Storage/ProjectA/ is completely different from /storage/projecta/. macOS and Windows are case-insensitive but case-preserving.
If a Mac artist exports a still or creates a folder on an SMB/NFS share using mixed case, the network protocol or mount point might force it to lowercase. Flame then looks for the mixed-case path and fails.
The Fix: Check your /etc/fstab or automounts. Ensure you aren’t using mount flags like nocase or SMB options that force lowercase.
Or just tell your Mac artists to lay off the shift key.
Right, re: case-sensitivity on various OSes. We’re all on Macs, though, and there’s no SMB/NFS stuff in play here as our Macs are all underpants-adjacent in our artists’ homes. The LucidLink Classic client per their docs is also case-insensitive but case-preserving, so I would think that…shouldn’t be changing anything?
An added wrinkle that I did not mention in my initial post is that we’re anecdotally running into the case getting changed when moving stuff from one machine onto another via archives. Teeny unmanaged archives. Yay for the future!
I need to spend more time chasing this down and will update the thread when I do. I just wanted to see if anyone else had run into anything similar. Will update once I know more!
On a similar note, non-English characters in file names might bork out on Linux. I had üğşçöı in Turkish, now I’m dealing with åøæ.
Can’t educate people so I have a script to sanitize filenames.
Ah. Then who’s got special sauce on their Flame that is fecking it up? Path translation or something unique to each machine?