10.6.2 and Custom Sounds

In previous versions of FCP I was able to add folders or an alias to /Library/Apple..../Final Cut Pro Sound Effects ..
This would allow me to access my own custom sounds in the Sound Effects browser. Now after upgrading to 10.6.2 I am no longer able to do this.


UPDATE: The problem is that only .CAF files are displaying in the browser. None of my .WAV files display anymore.

What I've always done is have a dedicated Library with sound effects (and a few other commonly used things) that I call "Elements". I have my sound effects in an Event and it's all categorized by folders (keyword collections) and it's easily searchable as well. If I need a sound, I find it and just drag it into the Project I'm working on. I've never tried adding sound effects to Apple's folder.

I've always added my sound effects to Apple's folder..

So it turns out that in the previous versions(s) you could add your own custom sounds in .WAV format.. Now, only .CAF files are recognized - so all I needed to do was rename all of my .WAV to .CAF - no conversion even needed..

Struggling_Editor wrote:

Does anyone have a work-around/way to get my own custom sounds into the Sound Effects Browser?

This still works as always. I'll bet you need to delete your preferences when launching FCP. Hold down Option and Command when starting FCP and choose to delete preferences when asked. This is always a good idea (and likely mandatory) whenever launching a new release of FCP for the first time to correct odd issues that sometimes appear.

The correct path just for information to add your own music to the FCP audio browser is : Macintosh HD/Library/Audio/Apple Loops/Apple/Final Cut Pro Sound Effects. It accepts the most common audio file types of .wav, .mp3, .aif, .aiff, and more.

I use my own sound folders in FC but they always appear completely out of alphabetical order.

I've always added my sound effects to Apple's folder..

So it turns out that in the previous versions(s) you could add your own custom sounds in .WAV format.. Now, only .CAF files are recognized - so all I needed to do was rename all of my .WAV to .CAF - no conversion even needed.

I use my sounds with different applications. I presume that if I rename my files with .caf then I can't use them with other software?

It would be better to just fix this so we can use .wav

Because of my alphabetical order problem I just use my sound library and drag the files into FC.
BTW, this problem I have is most probably local. Tried fixing it but nothing has worked up to now.

Albo wrote:


It would be better to just fix this so we can use .wav 

What are you referring to?  FCP works with WAV and most audio formats.  

After the 10.6.2 update, my FCP no longer recognized my custom .WAV files in the Audio Browser.
After updating to 10.6.2 does your recognize .WAV files in the FCP audio/sound effects browser?

FCP can still use .WAV files, but they are no longer recognized in the audio/effects browser -thats what this entire thread is about.

I am referring to custom folders.
I can drag .WAV in FC. I can't use custom folders.
If I need to change from .WAV to .CAF
It is not very usefull...for me at least.

I haven't received my MaC Studio as it is stuck at the canadian border!
I can't test it. I'm working with Catalina but the folder issue remains.
Sorry for any confusion.

If you mean the FCP Sound Library when you say audio/effects browser - yes, the latest version of FCP shows all my custom folders and sound effects within those folders....wav, aif, m4a, mp3, etc. See my post above in this thread and see if clearing the prefs as mentioned helps. If you are not talking about the FCP sound library, then I guess I do not understand.

Clearing prefs doesn't work. I rarely have issues but this one is just there and not going away.
Fo now I simply open my sound folder which is fine and alphabetical and drag from there.
I am not losing sleep over this. I prersume that once I install the latest version on Mac Studio everything will be back to normal.
Thanks.

My FCP sound library will no longer recognize/show/display anything but .CAF files. Clearing prefs doesn't work/fix/change anything.

Its not a big deal as changing all of my custom audio files from .WAV to .CAF only took a few seconds, but it was a PITA to figure out

Wow, not sure why that's happening. Working fine on FCP 10.6.2 and Monterey 12.3.1 on our Intel iMac pro.

Struggling_Editor wrote:

In previous versions of FCP I was able to add folders or an alias to /Library/Apple..../Final Cut Pro Sound Effects ..
This would allow me to access my own custom sounds in the Sound Effects browser. Now after upgrading to 10.6.2 I am no longer able to do this.
Does anyone have a work-around/way to get my own custom sounds into the Sound Effects Browser?

I just want to confirm we're having the same problem at our school on all our computers and laptops (so, it's not a machine specific thing).  We always linked all our sound libraries by putting those links in this folder:

Library - Audio - Apple - Final Cut Pro Sound Effects

This worked great for years, but now those links aren't showing up or if they are, it's only showing a partial list of the sound files inside them.

I wish there was a better way to manage large sound libraries inside FCP that worked as intended.

Chris
p.s. Not to be negative, I love all the other changes in 10.6.2, just frustrated by this new bug.

Library - Audio - Apple - Final Cut Pro Sound Effects

This doesn’t sound like the correct file path.

dgwvideo wrote:

Wow, not sure why that's happening. Working fine on FCP 10.6.2 and Monterey 12.3.1 on our Intel iMac pro.

Interesting. So those folders show up inside FC, in the browser? I'm having the same issue - have several aliases that simply don't show up now. Just tried a test where I copied a folder into that location (no alias) and it doesn't show up either... nothing but the defaults show up here, in spite of the other folders that live in there via Finder.
 macHD / Library / Audio / Apple Loops / Apple / Final Cut Pro Sound Effects

FWIW, just chiming in with my experience: I am running FCP 10.6.2 under MacOS 12.3.1 on a 2017 iMac Pro. I created an alias to a folder with 17.3 GB of sound files residing on an external SSD (Samsung X5). I placed the alias in the appropriate Final Cut Sound Effects folder on my system drive. All the files show up in the FCP browser. The files are in a variety of formats .wav. aif .mp3 .caf, etc. So, normal behavior as expected.

It's not... the correct one is Macintosh HD/Library/Audio/Apple Loops/Apple/Final Cut Pro Sound Effects.

Unless i missed something, it seems like those with Intel machines are not reporting any problem.
I have an M1, and can no longer see/access anything other than .CAF in the Sound Effects Browser inside FCP..

Tom Wolsky wrote:

Library - Audio - Apple - Final Cut Pro Sound Effects

This doesn’t sound like the correct file path.

Sorry, yes, I forgot to type the "Apple Loops" folder in there.

Also, as others have mentioned, I am on an M1 Mac Laptop.  But our classroom iMacs are Intel models.  All of them are experiencing issues accessing sound effects, through the Sound window in FCP with the new update.  Hopefully, enough people report this to Apple and hopefully, this is an easy fix.

OK, so now I am seeing the problem, but not exactly as some. We have about 200 GB of sound files in our library and mostly WAV or AIFF and a few mp3 and CAF. All of the CAF, MP3 and some of the WAV and AIFF files are showing up in the FCP sound browser. All of our custom folders show up (although not alphabetical which has been the case forever), but they are there. If the folders contain a mix of wav and mp3, then sometimes they show individual tracks (even some wav files) but not always. This is definitely a BUG and Kudos to Struggling Editor for first pointing it out. I've tried with the complete 200 GB production music folder in the path (same one it's been in for years) and also tried placing the production folder elsewhere on the system drive with an alias placed in the Final Cut Pro Sound Effects folder. Same result, but it was hard to tell at first without going through a large amount of subfolders to find the offending files.