Page 1 of 1

jBridge - ML Shared Memory error

Posted: Thu Jul 05, 2012 1:00 am
by 82DMC12
Hey all,

Just downloaded the demo of jBridge 1.5, made a new folder for bridged VST's, then when I try to scan that folder in Live it says

MLSharedMemory This Buffer Already Exists (long number) - please report this.

I hit OK and the error pops up 9 more times in a row, then stops - no VST's in my plugin window.

Never done this before so I'm not sure what to do? Any help?

Running Win7 64 bit

Andy

Re: jBridge - ML Shared Memory error

Posted: Thu Jul 05, 2012 2:29 pm
by 82DMC12
Just an update to how I came to this problem -

I have one folder called Plugins where I put all my DLL's. I ran jbridge and told it to scan my Plugins folder to find files to convert to 64 bit. I told jbridge to put all the new plugins in the new folder within Plugins called Plugins 64. That seemed to work fine, but when starting Live and going to preferences and setting the new Plugins 64 folder as the default plugins folder, I get all the ML Shared Memory errors.

Does anyone know what to do? Or tell me how they did it? Seems like jbridge works but I must not be doing it right.

I only have the demo of jbridge for now until I know it works.

Thanks,
Andy

Re: jBridge - ML Shared Memory error

Posted: Thu Jul 05, 2012 2:44 pm
by TabSel
Delete the folder "plugins 64".
Create a new one OUTSIDE your plugins folder.
Let jBridger create dlls in this new "plugins 64" folder.

Or use my Plugin Manager ;)

Re: jBridge - ML Shared Memory error

Posted: Thu Jul 05, 2012 3:02 pm
by 82DMC12
OK as I was typing my 2nd post I thought of that but since I'm at work right now I couldn't try it! Thanks I will do that tonight and hopefully it will work!

Andy

Re: jBridge - ML Shared Memory error

Posted: Thu Jul 05, 2012 3:20 pm
by VoiceOfNature
working with the regular version 1.5

NO error at all!

jBridge Works fine so far.

Guess crashes are going to happen, quite normal, but the interface and features is customisable.
Sure there is a way.

Write to the programmer if anything....

Re: jBridge - ML Shared Memory error

Posted: Thu Jul 05, 2012 6:08 pm
by TabSel
82DMC12 wrote:OK as I was typing my 2nd post I thought of that but since I'm at work right now I couldn't try it! Thanks I will do that tonight and hopefully it will work!

Andy
If you let the jbridger create dlls within the path it searches for dlls to bridge, it of course finds the bridge dlls it created, too, and bridges them again, overwriting your former bridge dlls, which will then try to load the former bridged dll, instead of the actual dll...

You have created dlls which try to load itself again and again when loaded by a host... Which leads to the error you mentioned...

Re: jBridge - ML Shared Memory error

Posted: Thu Jul 05, 2012 10:24 pm
by 82DMC12
Unfortunately creating a totally new folder outside of the original directory did not work. I still get the ML Shared Memory errors!

Andy

Re: jBridge - ML Shared Memory error

Posted: Thu Jul 05, 2012 10:41 pm
by TabSel
Running the jbridger tool as Administrator?
UAC off?

Re: jBridge - ML Shared Memory error

Posted: Thu Jul 05, 2012 11:01 pm
by 82DMC12
Well I turned UAC to OFF, then it asked me to reboot. I rebooted and then rescanned the folder in Live 8.4 and it found my plugins!

I did reboot at least once while trying to get this to work, so maybe it had something to do with UAC? I'm not smart with that kind of stuff.

Seems to work now though so time to get to work!

Thanks for the advice!


Andy

Re: jBridge - ML Shared Memory error

Posted: Fri Jul 06, 2012 2:30 am
by VoiceOfNature
Friends,

it truly does work:

UAC off, as Joao (the programmer) explains,
use different dir for the new bridged VSTs,
follow the instruction of the readme,
ask him...

No problem at all

Re: jBridge - ML Shared Memory error

Posted: Wed Jul 11, 2012 8:58 pm
by Bernd
Hi all,

seems like the problem is solved. We are preparing some general information about jBridge which hopefully explains it to everybody. As always I will lock this thread now to make it easier for us to keep track of the open issues.

Regards, Bernd.