I’d love for this to work because I really want of VST3 version but so far no luck. Everything seems to install ok, and the InMusic Software Center says everything is activated, but when BFD starts up (either standalone or as a VST on Windows 10) it hangs trying to reauthorize everything. I did get it to play for a while but it kept making horrible noises every so often presumably because of the activation problem
A couple of other weird things I noticed that have been noted elsewhere. The installer appears to delete the old VST2 version which I find scary in case the new version doesn’t work (which it didn’t) or loses the setting for each song the old version was in. I also noticed while it first came as a VST3 version, after playing with it a bit the Cubase plugin manager says it was now a VST2. Some explantion here of what it’s doing would be really nice. Is it supposed to replace the VST2 version? Why doesn’t it always show up as a VST3?
I use OCLP for my daily driver running Monterey, but not on my main music rig. I have a couple issues… I have a Focusrite Saffire FW interface and I use its mixer/monitoring software. It’s only supported through Catalina. It will probably run ok with Big Sur, but not Monterey. The other bigger issue is my Pro Tools version, again with the same OS constraints. Updating my perpetual license will cost $200. I’m fine for now, so long as BFD 3.4.5 continues to function. It’s been fairly stable. I haven’t even fired up the old LM recently because I’m working on a session and haven’t printed my drums yet (too risky). Eventually I’ll have to spend a couple grand to upgrade my whole setup.
ahh…I get you. I still have my saffire as well but replaced it with a Clarett a couple years ago. I actually tried the saffire with Sequoia just for fun and I did get it working, but didn’t really fully test it. I did have some issues with it on Big Sur and that’s why I got the Clarett.
I’ve been milking my Mac Pro as long as I can with OCLP, and now that 3.5 seems to be OK on Sequoia I’ll keep it going but I’m just a hobbiest and mostly just use the whole setup as my daily drum set for practice (edrums) along with “bedroom” recording my own stuff with Logic. If I were doing anything serious I’d probably be on an M chip by now.
I’m sure my Saffire would function fine on the audio side with something like Monterey. It’s just the software that it uses that I’ve gotten used to. Mine is the DSP model and it has some pretty decent virtual room software that I’ve used for years, but you need the app to use it. I like it because it’s not hogging up as much of my Mac CPU. I could Try something like Waves NX. Their stuff is usually pretty lightweight. I tried Acustica Sienna and it was too much.
I too have a Mac Pro 5,1. If I ever did go the way of patching Monterey, or above, I’d probably choose the Martin Lo OC pkg. That would give me H/W acceleration for my Nvidia card at least. For the near future, I’m going to at least consider moving to Catalina. I just picked up a sick deal on IK T-Rack6 Max for $30, but it won’t run on Mojave. I’ve got a few other things that want to run on Catalina as well.
I’m no expert on the Martin Lo version but I think it may have stopped on Monterey? If you want to go farther it would be the OCLP. I use a Nvidia GTX680. I think OCLP has fixed the issues with Kepler based GPU’s. Take I say with a grain of salt though because this is just info I passed by when trying to figure out how to update. lol.
Yes, I think so. I have a flashed GTX680. I don’t think OCLP will give you H/W accel for video editing. That is only with Martin Lo OC. I’ve done some more research today and I think I may try to install OC/Catalina soon’ish. That shouldn’t break anything on my system now and I will be able to use a few more apps that I’ve had on the shelf. I also forgot about my Waves plugins. I still have some v11 that I use and going above Catalina would require buying their WUP. The only downside to Catalina is the loss of 32bit support. I think ML OC can give back support for 32bit, non-GUI apps.
When you launch, don’t click on the authorize everything button. It hangs when it has either a bunch to authorize, or some it can’t, or something like that.
Instead, launch, and when you get to that page, do the option where you don’t authorize. Then go into installed content locations, and scan each of your locations one by one.
The authorize everything button on launch is kind of broken in that respect, and you shouldn’t ever press it unless everything is perfect. However, it’s also safe to ignore if you’ve previously authorized everything that does work, using the method I just described.
Thanks katka, but I think the problem lies elsewhere. The BFD 3.5 windows installer doesn’t put the new standalone version in the start menu (at least it didn’t on my Windows 10 computer) nor it seems does it remove the old standalone version. So after running the installer last time I inadvertently ran the 3.4 standalone version which apparently wasn’t happy. I tried reinstalling BFD 3.5 again yesterday and got the 3.5 standalone version to work with everything apparently authorized, but now the VST version crashes Cubase. I’ve submitted a bug report and got one fairly prompt reply but no solution yet.
Well that and compatibility for VST3 and native Apple silicon for AAX. And they ditched the old LM. We weren’t expecting much more than that for a point release anyways. It’s a free update for existing owners, so I’m not sure how that’s disgraceful. Obviously, BFD4 is still a ways out, so they decided to refresh this UI one last time.
Status update. With some help from BFD support I got BFD3.5 working on the third try. Almost all the BFD expansions seem to work ok, but none of new installers for the Sonic Reality or Platinum Sample expansions I have installed correctly, Luckily BFD is still working at the moment with the old BFD 3.4 versions.
Re for a free update I’d be thrilled if it didn’t add anything but VST3 support as VST2 is end of life.
Interesting. I’m on Windows here. (Used to have Macs, but switched to PCs a number of years ago so I could assemble my own hardware ;>) The third-party downloads seemed an appropriate size, but something’s wrong with the Windows installers. The installer for a couple of the packages threw up a Windows Security error message and failed to run at all. Funny thing is all the InMusic installers worked. Who knows. I sent the details to InMusic. Also, still don’t know why I needed the new installers at all as BFD 3.5 is running fine on all the old audio files and now my disk is full of 2 couples of all the expansion packs.
Can’t seem to download the Software Center on my Mac Studio. I was able to install it on my MacBookPro over the weekend but on the MacStudio Running OS15.2 I get an error when trying to download the Mac version. It does let me download the Windows version!! So did something change over the weekend with the Mac installer. I tried different Web browsers as well. All with the same error message: SignatureDoesNotMatch tx000004a734d7d05fcb018-0067d846ca-9d003d33-default9d003d33-default-default
