Bit bridging

[dakkra]

Some other thought about bit-bridging: It's all about a temporary problem because day by day those 32 bit VST plugs that are not updated by their devs towards a 64 bit version gets more and more outdated. Question: Are those abandonned VSTs so unreplacable for you guys? (or am i missing something?)

The biggest issue is DEVs aren't willing to switch to 64bit. There are DEVs who are trying but are failing. Also there are some VST that are really nice but are only 32bit. G200k Kerovee for example. It's a nice free pitch corrector. No 64bit version but I don't want to pay 200$ to get a new 64bit pitch corrector that I'll have to re-learn.

[MuTools]

I guess I wasn't clear while talking about the layer, I talk about the fact that you have to run jbridge, make bridged dlls, scan your folders. I have 2000+ vst 32/64 mixed in same folders. And my SSD is already full so I stick to daw with integrated bridges only but I guess I'm a special case.

I'll evaluate adding direct support for jBridge in MuLab. That way there won't be a need to create auxiliary files anymore, if i understand well.

[MuTools]

Basically I get an error while it bridges files. An R6034. And when I try to load the bridged files into mulab they aren't added because Mulab sees them weird (I don't exactly know what the problem is as I am not a programmer)

Good news: As you already probably know this only is a permission issue. It's explained on the jBridge website, iirc. So issue solved.

And adding direct support for jBridge in MuLab will make it easier to use jBridge. I think that will be a good compromise.

[dakkra]

Yeah I forgot to run Mulab as admin (silly me)

Agreed on direct support for JBridge.

[liquidsound]

MuBridge.... sounds much better

[jonljacobi]

Wow. I have about ten FX and three or four synths. I can't even imagine the time involved in keeping track of 2000 VSTs, let alone using them.