Workaround: MuLab 4.3.12 win64 - supports only 64 bit VST Plugins?

[Hermu]

with MuLab 4.3.12 win32 i can use my 32 bit VST plugins, but it's not possible to use it with the win64 version. I think it should be possible to use 32 bit VST plugins within MuLab win64 version?

MuLab win64 VST Plug-In Scan Log:

Ready to start scanning D:/VST/DUNE/DUNE.dll

Scanning D:/VST/DUNE/DUNE.dll
Load library for VST plug-in 'DUNE.dll' failed, msw error=
Added 0 VST plug-ins
New Total = 0 VST plug-ins

[fluffy_little_something]

There is a kind of adapter program that enables you to use 32-bit plugins in the 64-bit version of Mulab, it is called a bridge if I remember correctly, forgot its name, though

[Hermu]

There is a kind of adapter program that enables you to use 32-bit plugins in the 64-bit version of Mulab, it is called a bridge if I remember correctly, forgot its name, though

now i've tried jBridge to create a 64 bit VST plugin but it won't work with MuLab 64-bit, because MuLab does't seem VST hosts provide built-in jBridge support.

MuLab win64 VST Plug-In Scan Log:

Ready to start scanning D:/VST/DUNE/DUNE.64.dll

Scanning D:/VST/DUNE/DUNE.64.dll
Exception while creating aeffect for DUNE.64.dll
Added 0 VST plug-ins
New Total = 0 VST plug-ins

[MuTools]

Indeed you need jBridge to bridge 32 bit plugins into a 64 bit host.
MuLab 64 bit is working fine with jBridge, several users are using it.
If Dune 64 bit crashes in MuLab 64 bit, please contact Synapse as i can't look inside a VST plugin. I'm open to cooperate with Synapse if they need me to sort this out.

[Hermu]

Indeed you need jBridge to bridge 32 bit plugins into a 64 bit host.
MuLab 64 bit is working fine with jBridge, several users are using it.
If Dune 64 bit crashes in MuLab 64 bit, please contact Synapse as i can't look inside a VST plugin. I'm open to cooperate with Synapse if they need me to sort this out.

thanks for your advice. I think it's a problem with jBridge demo version, because always a VST dll file with 3,50 KB filesize will be created and jBridger is finished within 1 second.

[AndreasD]

The small file size for jBridged VSTs are normal.
But you have to select these mini .dll files that jBridge created, not the original .dll! when you install the VSTs in 64bit Mulab.

[Hermu]

The small file size for jBridged VSTs are normal.
But you have to select these mini .dll files that jBridge created, not the original .dll! when you install the VSTs in 64bit Mulab.

Here my jBridge procedure step by step. I don't know what's wrong.

I've used jBridge V1.5 (demo version)

start jBridger:
jBridger tool v1.21 (jBridge v1.5)

Step1: Select your VST host's architecture -> I'll be using x64 (64bit) host.
Step2: Select your options...(unchanged)...and choose a file creation method: ->
Create bridging files inside a directory I'll specify -> HIGHLY recommended! <-
Step3: Select VST plugin(s) to be scanned (a directory or a single file)
D:/VST/DUNE/DUNE.dll
Step4: Select destination directory for briding files
D:/VST/DUNE64

JBridger message window output:
1 file(s) briged for using in your 64bit VST host (0 subdirectories scanned)...

start MuLab 4.3.14 64bit and select new Session.
MULAB -> Manage VST Plug-Ins -> Add VST Plug-In
D:/VST/DUNE64/DUNE.64.dll

MuLab win64 VST Plug-In Scan Log:

Ready to start scanning D:/VST/DUNE64/DUNE.64.dll

Scanning D:/VST/DUNE64/DUNE.64.dll
Exception while creating aeffect for DUNE.64.dll
Added 0 VST plug-ins
New Total = 0 VST plug-ins

I've tried also other 32 bit VST plugins and i get always the same error.

[AndreasD]

Can you try to create DLLs without the ".64" change in the name?
Otherwise your way of setting it up sounds similar to what i have done.
You mention 'effect' can not be created, so the DLL name change might have to do with it.

I have about 20 bridged VSTs running (Waldorf, Korg, Vandal,..., sorry no Dune) without problems.

[edit] i downloaded the Dune demo and with the above it installed OK in Mulab x64. BTW, there seems to be a 64bit version of Dune. So you don't need to bridge it. Use the 64bit version.

[Hermu]

Can you try to create DLLs without the ".64" change in the name?
Otherwise your way of setting it up sounds similar to what i have done.
You mention 'effect' can not be created, so the DLL name change might have to do with it.

I have about 20 bridged VSTs running (Waldorf, Korg, Vandal,..., sorry no Dune) without problems.

[edit] i downloaded the Dune demo and with the above it installed OK in Mulab x64. BTW, there seems to be a 64bit version of Dune. So you don't need to bridge it. Use the 64bit version.

Have you also used the same jBridge V1.5 (demo version)?

I've also created VST DLLs without the ".64", but it's the same effect.
All other FREE VST 32bit plugins which i have tried, generates the same error when i try to load them into MuLab 64bit. If i can't do that, i must say only 64bit VST DLLs works with MuLab 64bit.

Now i have installed DUNE 64bit VST version.

[AndreasD]

I'm out of options. Dune installed fine, never encountered a problem free or commercial VSTs.
I use the same jBridge version (purchased, but i remember that i checked the demo first).
I'm running win7 64bit.

Can you do a last try and drag and drop the jBridge DLL into a rack in an open session?
Can't see that it would make a difference, but that's what i usually do.

[edit]: i just remember, start with an empty (at least not copied over from the 32bit Mulab version) VstPlugins.Xml file in the Mulab/user/settings folder.
I did had problems when the same plugin was already in the VstPlugins.Xml.
Delete any entries in this file of previous (failed) installations. Then install it again.

[Hermu]

I've draged and troped jBridger DUNE.dll into a rack of an open new session with an empty VST plugin list and i got the message window "Invalid VST Plug-In".

How does MuLab know in which directory the original VST dll is located?

jBridge generates 2 files in D:\VST\VST64:
DUNE.dll
DUNE.txt

content of DUNE.txt:
"D:\VST\DUNE\DUNE.dll"
ID: 1398231888
flags: effFlagsHasEditor
flags: effFlagsIsSynth
flags: effFlagsCanReplacing
flags: effFlagsProgramChunks

[MuTools]

I don't think MuLab has to know the original 32 bit DLL location. This is how it works: You plugin the jBridged DLL 64 bit into MuLab 64 bit, so MuLab talks to jBridge, then jBridge talks to the 32 bit plugin.

But did you read Andreas' note:

[edit]: i just remember, start with an empty (at least not copied over from the 32bit Mulab version) VstPlugins.Xml file in the Mulab/user/settings folder. I did had problems when the same plugin was already in the VstPlugins.Xml. Delete any entries in this file of previous (failed) installations. Then install it again.

That's a very good hint indeed. Please only edit VstPlugins.Xml when MuLab is not running.

Hope this helps.

[Hermu]

Yes, i've have read Andreas note and deleted all entries in VstPlugins.Xml if MuLab was not running, but it doesn't help.

[Hermu]

I don't think MuLab has to know the original 32 bit DLL location. This is how it works: You plugin the jBridged DLL 64 bit into MuLab 64 bit, so MuLab talks to jBridge, then jBridge talks to the 32 bit plugin.

It could also be MuLab can't talk with my jBridge demo version?

[MuTools]

Then you would be the first one, afaik. I heard from several users that they were using it without probs.

Hey whats does the scan log screen says when scanning Dune 32 bit?
I would expect some error message in there.