KVR Audio

Giusmex · Post by **Giusmex** » Mon Aug 08, 2011 11:27 am

Hi

I made your program scan my waves directory which is :

c:1programfiles(86)\waves ( where also one knob loude, pressure, maxxbass are included, and that work well

and then i told you program t put the bridged plugins into:

c:\programfiles (64)\steinberg\vstplugins\bridgedplugins.

Now, this latter directry cntains 2 subdirectories which are:

c:\programfiles (64)\steinberg\vstplugins\bridgedplugins\waveshells and

c:\programfiles (64)\steinberg\vstplugins\bridgedplugins\plugins

now, i did not discriminate between the two because as i said to you i put the output bridged plugins into:

:\programfiles (64)\steinberg\vstplugins\bridgedplugins.

Should i put my transx into only one of those 2 directories?

repeat the other waves plugins work well

umd · Post by **umd** » Mon Aug 08, 2011 11:38 am

Hi.

I would recommend that you only create bridging files for the waveshells ( which would mean scanning all the waveshells inside c:\programfiles(86)\waves one by one ).

As for trans x's bridging files, you can place them in any place you want, as long as the original trans x plugin isn't scanned.

( if that plugin is associated with a waveshell, I recommend that you bridge that waveshell instead )

Giusmex · Post by **Giusmex** » Mon Aug 08, 2011 11:56 am

forgive me, but i dnt understand what you mean

i'd prefer you to explain me step by step what to do, this waveshell is in onothere directry different frm the plugin directory, so it is a mess

if you want to explain what to do step by step with your program , itll be good, other wise ill understand

umd · Post by **umd** » Mon Aug 08, 2011 12:06 pm

Hi.

Sure, no problem. In doubt, I would recommend that you delete all the previously created bridging files and start again.

Please have a look here first, this is the procedure:

http://jstuff.wordpress.com/jbridge/jbr ... ing/782-2/

Do you know which waveshell(s) contain the plugins you mentioned?

Inside the c:\programfiles(86)\waves folder there should be one or more files named WaveShell(...).dll, try bridging those files only.

Hope this helps.

paterpeter · Post by **paterpeter** » Sat Sep 03, 2011 9:09 am

Hi there,

I'm currently demoing jbridge (version 1.3). Can I somehow disable the warning that the host or auxhost is running without admin privileges? I mean, I understood the message the first time I saw it

Thanks!

Regards,
Andre

umd · Post by **umd** » Sat Sep 03, 2011 10:18 am

Hi, Andre.

Unfortunately, it can't be disabled in the demo, but contact me if you decide to go for the full version and I'll customize your build to address that.

Restless · Post by **Restless** » Sat Sep 03, 2011 10:19 am

paterpeter wrote:Hi there,

I'm currently demoing jbridge (version 1.3). Can I somehow disable the warning that the host or auxhost is running without admin privileges? I mean, I understood the message the first time I saw it

Thanks!

Regards,
Andre

If you right click on the executable you can set it to always run as administrator. It's in the compatibility tab, assuming you're on win 7.

umd · Post by **umd** » Sat Sep 03, 2011 10:23 am

Thanks, Restless.

I assume he just wanted to disable the warning, but I forgot to add that I recommend to run it in admin mode (jBridge and your main VST host ) to avoid problems such as plugins appearing unregistered, blank GUI's, sound data access problems, etc.

paterpeter · Post by **paterpeter** » Sat Sep 03, 2011 10:27 am

umd wrote:Hi, Andre.

Unfortunately, it can't be disabled in the demo, but contact me if you decide to go for the full version and I'll customize your build to address that.

Hey, that's cool, thanks a lot

Restless wrote: If you right click on the executable you can set it to always run as administrator. It's in the compatibility tab, assuming you're on win 7.

Thanks for your answer. I know that. But the point is: I don't WANT to run the applications with admin privileges. I have no plugin that requires fully blown admin privileges. While it's of course the easiest solution for plugins that misbehave (by assuming admin privileges) it's an unnecessary security risk.

The issues with those "difficult" plugins normally boils down to either:
- files or registry settings that are not found at the expected places
- attempts to write to protected directories

So far I could tame all those plugins by copying some files/registry settings to the proper places and/or giving them write access to very specific directories.

Have fun,
Andre

nickb100 · Post by **nickb100** » Thu Sep 15, 2011 3:35 am

Hi UMD!

How can I disable the "Prevention of major control the host when the GUI window is closed" for some plug-ins ? I restart my DAW but this option is enabled again

umd · Post by **umd** » Thu Sep 15, 2011 7:37 am

Hello.

Which is the plugin that it happens with?

nickb100 · Post by **nickb100** » Thu Sep 15, 2011 9:59 pm

Waves,PPG Wave3 as an example. Jbridge 1.2 this option worked properly
JB1.3 option "Prevention of major control the host when the GUI window is closed" always enable (after restart DAW),even when I turn it off

umd · Post by **umd** » Fri Sep 16, 2011 12:20 am

Hello.

Hum, I am thinking that this could be some sort of write permission issue ( the settings fail to be saved into the settings file ).

Does it only affect this specific option?

Also, are you running everything as admin as shown here in pictures 1-2?

http://jstuff.wordpress.com/jbridge/jbr ... ing/782-2/

DrApostropheX · Post by **DrApostropheX** » Fri Sep 16, 2011 12:23 am

Just curious: has anyone figured out the jbridge settings that get the d16 SilverLine plugins to work reliably? I know there's got to be a combination of settings which makes them work, but I haven't figured it out.

umd · Post by **umd** » Fri Sep 16, 2011 12:24 am

Hello.

Try enabling the "opcode 19" and the "sluggish GUI hack" options.

Let me know if it's any better.

Need testers for my x86 to x64 vst adapter