No audio output from BFD after updating to 3.5

BFD3 General Discussion
1

I’d had BFD3 ver 3.4.5.28 running fine on my 2021 MacBook Pro with M1 Max chip running Ventura 13.7.4. Now that I have updated to 3.5 I am getting no audio output from it. I am awaiting a reply from inMusic which I don’t expect until tomorrow, or maybe next week… who knows. Meanwhile does anyone know how to solve this? Thanks.

2

Using the top left menu button, open Tools, then Audio and Midi settings. Are the settings there correct?

Paul

3

Thanks for replying, Paul. That was the first thing I checked and they are correct.

But, checking that again just now got me to notice that in that same Tools menu is “Set up content locations…”, and I found that BFD somehow lost the location of my content. I don’t know this could’ve happened, but after re-pointing it to the parent folder of my libraries, kits are loading and I’m getting audio!

Thanks again.

4

Unfortunately the same her - installed BFD yesterday, no update, first install.
I changed the sound options - MacBook Speakers to Boss Gigcaster – no change.
I see the flashing drumkit, but I don’t hear any sound. I also tried the hint from bucketofish but that had no effect either.
I use a MacBook Pro, M3 with 15.3.2
Does anybody here have some suggestions?

All the best

Klaus

5

Klaus, towards the top left of the BFD3 window is an icon for Show/Hide Browser Panel (phrase displays when you hover over it). Toggle that icon such that the menus will show: Presets, Kits, Drums, Grooves, etc. A kit must be loaded in order to hear sound. Double-click on any kit, then you will notice loading status bars for each drum in the mixer that will disappear a moment later after the kit’s samples fully load from your library. After that when you click a drum on your screen you should hear its assigned sound from the kit. Go to the Grooves menu, and Palettes will appear. Hover over any groove and a play icon will appear; click it to hear the groove play with the kit that you selected earlier. As the groove plays, you can go back to the Kits menu and double-click on other kits for comparison. I hope that helps.

6

Thanks for your answer, bucketofish!
The problem in my case was that I trusted the default installation values.
The installer installed the core library in the wrong location. After solving that, everything just works fine. In case somebody encounters the same problem, follow the installation process described here:

7

Glad you worked it out, kkoop!