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

[Hermu]

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.

Error message posted already with my first post.

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

[pljones]

Dumb question - you're using the jBridge in the "right direction", yes? There's a 32->64 and a 64->32, I believe (I don't use it, so I could very well be wrong). I don't know which you'd need to be running but if you're running the wrong one, it'd be like going 32->32 or 64->64 and not really help much .

[Hermu]

Dumb question - you're using the jBridge in the "right direction", yes? There's a 32->64 and a 64->32, I believe (I don't use it, so I could very well be wrong). I don't know which you'd need to be running but if you're running the wrong one, it'd be like going 32->32 or 64->64 and not really help much .

please read my jBridge step by step procedure above.

[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?

I looked at jBridge installation directory and found this Readme.txt:

• Important:
  
  *If you're using a VST host without jBridge support, run the jBridger tool ( Start Menu->Programs->jBridge->jBridger )
  and follow the on-screen instructions. Your host will need to scan the bridging files created by the jBridger tool instead
  of the original plugins.
  
  *If your VST host has built-in jBridge support, please refer to its documentation.
  
  *Currently, the following VST hosts provide built-in jBridge support:
  - Cakewalk Sonar 8.5.x or above
  - Cantabile 2.x
  - VSTHost
  
  For more help and documentation, please visit:
  
  http://jstuff.wordpress.com/jbridge/jbr ... eshooting/

If i understand it right, the user have not to run jBridger tool if VST host (MuLab) has a build-in jBridge support.

[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.

I looked at jBridge installation directory and found this Readme.txt:

• Important:
  
  *If you're using a VST host without jBridge support, run the jBridger tool ( Start Menu->Programs->jBridge->jBridger )
  and follow the on-screen instructions. Your host will need to scan the bridging files created by the jBridger tool instead
  of the original plugins.
  
  *If your VST host has built-in jBridge support, please refer to its documentation.
  
  *Currently, the following VST hosts provide built-in jBridge support:
  - Cakewalk Sonar 8.5.x or above
  - Cantabile 2.x
  - VSTHost
  
  For more help and documentation, please visit:
  
  http://jstuff.wordpress.com/jbridge/jbr ... eshooting/

If i understand it right, the user have not to run jBridger tool if VST host (MuLab) has a build-in jBridge support.

[MuTools]

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

Based on what i read in your other posts, you tried to load the original Dune.dll here i.e. the 32 bit one. That would indeed lead to a "Load library for VST plug-in 'DUNE.dll' failed".

Make sure you load the bridged DLL file i.e. the one with the small filesize.

[MuTools]

If i understand it right, the user have not to run jBridger tool if VST host (MuLab) has a build-in jBridge support.

Indeed MuLab has not yet built-in jBridge support but that should be no problem. You can still use jBridge.

[Hermu]

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

Based on what i read in your other posts, you tried to load the original Dune.dll here i.e. the 32 bit one. That would indeed lead to a "Load library for VST plug-in 'DUNE.dll' failed".

Make sure you load the bridged DLL file i.e. the one with the small filesize.

Now we are turning around.

How you can read in my second post i always loaded the jBridger builded dll.

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]

Because you also reported this one:

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

I see 2 differences:

1) I don't see the VST64 folder in there that you seemed to use before.
2) The error message is different.

[Hermu]

Because you also reported this one:

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

I see 2 differences:

1) I don't see the VST64 folder in there that you seemed to use before.
2) The error message is different.

correct, these are the scan logs from my first and my second post.

[Hermu]

If i understand it right, the user have not to run jBridger tool if VST host (MuLab) has a build-in jBridge support.

Indeed MuLab has not yet built-in jBridge support but that should be no problem. You can still use jBridge.

MuLab has not build in jBridge support and so MuLab has to know:
1. this is a briged DLL
2. on which directory the original DLL is located

if this is the precondition, loading jBridged DLL should work!

[MuTools]

MuLab has not build in jBridge support and so MuLab has to know:
1. this is a briged DLL
2. on which directory the original DLL is located

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.

if this is the precondition, loading jBridged DLL should work!

Did you check: http://jstuff.wordpress.com/jbridge/jbr ... eshooting/ ?

[Hermu]

If i understand it right, the user have not to run jBridger tool if VST host (MuLab) has a build-in jBridge support.

Indeed MuLab has not yet built-in jBridge support but that should be no problem. You can still use jBridge.

MuLab has not build in jBridge support and so MuLab has to know:
1. this is a briged DLL
2. on which directory the original DLL is located

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?

is this not a conflict? No MuLab build in jBridge support, but talking with jBridge during loading VST plugin?
Is it possible, to extend the scan log, to get more details about loading VST plugin error, because "Exception while creating aeffect for DUNE.64.dll" is not realy helpfull? Or have MuLab error logging implemented?

Did you check: http://jstuff.wordpress.com/jbridge/jbr ... eshooting/ ?

yes, i have checked and my 32bit VST DLLs works very well.

[MuTools]

is this not a conflict? No MuLab build in jBridge support, but talking with jBridge during loading VST plugin?

No, not a conflict.
Built-in jBridge support means you would not have to bridge the plugins manually, afaik.

Is it possible, to extend the scan log, to get more details about loading VST plugin error, because "Exception while creating aeffect for DUNE.64.dll" is not realy helpfull?

I can't get more details about that error. Only Synapse can know what's going on when an exception occurs inside Dune.

[Hermu]

is this not a conflict? No MuLab build in jBridge support, but talking with jBridge during loading VST plugin?

No, not a conflict.
Built-in jBridge support means you would not have to bridge the plugins manually, afaik.

Is it possible, to extend the scan log, to get more details about loading VST plugin error, because "Exception while creating aeffect for DUNE.64.dll" is not realy helpfull?

I can't get more details about that error. Only Synapse can know what's going on when an exception occurs inside Dune.

As i wrote in a post before, it's a generaly 32bit VST DLL problem. As I know it's not easy to keep overview over all posts.

However, i have tried MuLab on 3 different PCs with Vista 64bit and Win7 64bit, but of none from them is it possible to use 32bit VST DLLs within MuLab 64bit, this was also my post subject.

Thank's for your support!