Extensions on Files Changed from lower case to upper case

Question

Level 1

8 points

Extensions on Files Changed from lower case to upper case

I have a project that I have not gone back into for several months. I recently went back to it to pull a few sequences from it. When I went back in, the footage had to be relinked since I had moved it from an external thunderbolt raid to a QNAP Server. The video files relinked perfectly, however the audio files did not. Upon further investigation, the wav file extensions changed from lower case to upper case (.wav to .WAV). FCPx did not recognize them until I went through and replaced the extensions back to a lower case.

Two questions:

1) What could have caused the extensions to change like that?

2) Why does FCPx not recognize the extnesion when the only difference is lower case versus upper case?

(System notes)

MacBook Pro Retina, 15 inch, Late 2013

Mac OS 10.12.6

System Drive formatted Logical Volume, Mac OS Extended (Journaled, Encrypted)

FCPx 10.3.4

External Server

QNAP TVS-871T

MacBook Pro (Retina, 15-inch, Late 2013), macOS Sierra (10.12.6), null

Posted on Oct 25, 2017 11:27 AM

Reply

Answer 1

Oct 26, 2017 9:22 AM in response to Jahret

1) It could be related to the formatting. The usual HFS+ is case-insensitive, but other file systems are case-sensitive.

How is the QNAP formatted?

2) I expect this may be related to 1). I am able to relink files with wav or WAV extension indifferently in an HFS+ volume. Maybe it isn't so in a case-sensitive volume.

Reply

Answer 2

Jahret Author

Level 1

8 points

Oct 26, 2017 9:28 AM in response to Luis Sequeira1

I just confirmed they use a Linux based filesystem EXT4, which is as you guessed, case sensitive. But I am still unclear as to why it would convert it to all caps, when this only happened to the .wav files not mov or .mp4 or any other file for that matter. Thanks for the suggestions!

Reply

Answer 3

Oct 26, 2017 9:41 AM in response to Jahret

You're right, it is strange that it converted to all caps. HFS+, even though it is case insensitive, is "case-aware" (not sure if that is the right term), in the sense that if you name a file in lowercase (or any combination of upper and lowercase) it will honor your naming, so if you save your file as myFILE.wav, for example, it will show exactly like that in Finder, Terminal or whatever.

Reply