[CONFIRMED] Outputs Mono/Stereo

BFD3 Archive
1

Hi,

Iam using the latest Version of BFD3 within Cubase. I normally use all the outputs and want to do so. However, it is not working.

For example: Kick in to Mono1, Kick out to Mono2. I set it up and then it works… and then after a while it stopped working. No sound is going to Cubase anymore. And when I close everything and start again, all settings are lost.

This is a big thing for me… please help. Thanks, Olli

edit: The problem is (I think), that BFD automatically sends Kick in and Kick out to Kick. And doesnt let it at Mono1 and Mono2 for example.

3

Hi @Ollimarc

Thank you for reporting this issue, I have passed it onto the dev team to look into further.

All the best, Rayne

4

Thank you.

I can put everything but kick in, kick out, snare bottom and snare top to the mono/stereo outputs.

5

Same issue here. I can’t able to route properly the snare bottom and top to different mono outputs (Cubase 12.0.20).

6

Same issue in Cubase 11.0.41.

I set route Kick(In, Out, Sub) to Mono1-3, Snare(Top, Bottom, Rim) to Mono4-6.
But they has been reset latest version.
I set again but reset every time rebooting Cubase…

I want to use BFD previous version untill fixed, is there a method for reverting?

7

Same issue here. (Cubase 12, BFD 3.4.4.29)

8

Same issue here. (macOS 10.13.6 High Sierra and Pro Tools 2021.6)

Even after routing the kick and snare manually to the correct outputs, saving the session and re-opening the kick and snare channels revert to Master 1. This is a huge issue for me. Gonna have to revert to the last BFD3 build until this is fixed.

9

Oooo… okay, we’ve repro’d this in house. That’s a bit messed. We’ll get it fixed, and hopefully be able to put out a .30 build. Will raise with devs.

3 Likes
10

(By the way, it happened before)
Thank you, but… I have to finish many productions for my clients. I tried to revert to the previous version without success (License Manager tells me everything is OK and authorized, but the VSTi keeps telling me I need to authorize it).
So, please, I can’t wait anymore: can you explain the correct way to have the previous version working?
Thank you.

1 Like
11

@lordadb The previous BFD3 build installs the wrong LM (3.0.5.2). You need LM 3.0.5.3. If you don’t have it saved, I may be able to upload it here. Let me know.

Edit: Here you go.
BFD License Manager_3053_OSX.dmg.zip (1.7 MB)

2 Likes
12

Thank you! Unfortunately I’m on Win 10.
My LM installed version is 3.0.6.22. So, Do I need to unistall and install again the old version of LM to have the BFD 3.4.3.7 authorized?

13

We believe we have a fix. Needs QA to check it.

14

Yeah, sorry 'bout that man. I realized afterwards that heck, there is a Windows version too, duh. Which I don’t back up, but since they’re pretty lightweight, I’m gonna start saving the Windows installers for users if they need to revert and don’t have them.

Ideally, we as customers should have access to previous build/LM installers in our accounts, or here on the forum.

So back to your question… there is no need to uninstall when reverting or upgrading BFD3, or the LM. If you have the installer for 3.4.3.7, just run it and it will overwrite your current LM version with the previous one.

But maybe hang on a few days, as Drew says they can probably bang out a hot fix for this issue.

1 Like
15

I thought this yesterday but forgot again.

Yes, 100%

16

He already has it! Sent it over to him yesterday.

If anyone else wants it, ping me.

17

@BFD_Drew Wait, the hot fix, or previous version?

18

The hotfix. And it seems to work very well.

2 Likes
19

Yeah, he sent it to me. I’ll try it out in a bit.

20

Hotfix seems to be working for me. No issues with custom saved output routing now. Thanks for the prompt fix.

1 Like
21

Hi, where can I get the hotfix?