Installed JBridge. It resides in my Programs Folder. I watched the video. I tried to install a 64bit VST Nectar2 plugin in both BIAB and RB but I still get the same "won't work" message as before, that is, pre-2015 BB/RB. I'm not sure how to proceed or troubleshoot.

Should the JBridge program folder be in the BB Folder? Should I delete and reinstall - how do I do reinstall? (So many questions!)

Thanks in advance for any help.


Win7Pro / 8GB RAM / 1.3G Hard Drive / BIAB/RB EverythingPK /


[reply by Peter Gannon/PG Music]: Hi Sonny Ray: Please see my detailed reply at the bottom of this thread. In our testing, the 64 bit plugin that you mentioned works fine in Band-in-a-Box 2015 with jbridge. The plugin to use is "iZotope Nectar 2.dll" (this works in Band-in-a-Box 2015, including 64 bit and 32 bit ). The issue likely arose because you chose a different plugin name, that is iZNectar2.dll which is a "VST 3" and not a VST plugin. But please try it with "iZotope Nectar 2.dll" and it should work fine. Peter Gannon

Sonny,

Did you get JBridge from PG Music? If not, what version do you have?

Regards,
Noel

A wont work message likely means that you don't have the current version of jbridge. Try the menu help,show log of yellow messages. That should record the exact message, which usually says more Info,

Hi,

Noel: Yes, I purchased my JBridge from BB: Version 1.7b3

Peter: I don't understand the last part of you message: "Try the menu help,show log of yellow messages. That should record the exact message, which usually says more Info" I've gone to help and I've looked at the activity log but I can't access any message pertaining to my attempts to access a 64bit plugin.

I read the a later posting similar to mine about the same problem and followed the link to jBridge. I've followed their set up instructions but still am getting the same result: RB won't recognize the 64bit version of Nectar2 (it still recognizes the 32bit format) or any other 64bit plug on my computer.

Not sure how to proceed.

Thanks for your help,
SonnyRay

I don't know if this makes any difference to the above: I just clicked on the JBridge icon and noticed at the top of the box this info: "jBridger Tool V1.25 (jBridge V1.7b3)" This seems intentionally confusing about which version is actually operating?

SonnyRay

If you don't mind my asking and purely out of curiosity, since I don't have Nectar 2 I can't check, but in the folder:

"C:\Program Files\VST" (the 64 bit folder) or WHEREVER you told iZotope installer to install 64 bit Nectar 2:

How many, and what are the names of, each .dll that contain the word "Nectar" are there?

Larry

Hi,
There's several plugins that come with Nectar2. This is how they're noted:

iznectar2.dll
iznectar2BreathControl.dll
iznectar2PitchEditor.dll

When I bought the plugin I downloaded both the 32 & 64bit versions.

I can used the 32bit versions with BB/RB, but I'm trying to get JBridge to work with the 64bit versions, and it ain't working.

Does anyone at PG think I should reinstall JBridge?

Thanks for your help,
SonnyRay

JBridge; if you want to use a 64bit plugin: run jbridger, select the source 64bit plugin dll, and install the newly created 32 bit version through jbridger in folder or location where you want BIAB to find it using BIAB's add VST function. Might be handy to create the new 32bit one with *.32.dll extension. If the converted vst plug works partly , thus only if it's GUI shows but it will not run and gives you error messages, you have some options for specific corrections if you click on settings below the plugin it self. -F

That is NOT required anymore - BIAB/RB recognizes JBridge natively, for lack of a better description.

Install BIAB, Install the v1.73 JBridge - then simply load your 64 bit plugin like it was a 32 bit upon - no extra steps.

That's how its working for my 64 bit plug ins like ST 3, Kontact 5, etc.

The reason I asked about the actual .dll names is that because that is all you have to pick them in the VSTi plugin pull down in BIAB/RB and not all .dlls are the actual VST/VSTi . And i know from a few "wrong picks" on my part it will crash JBridge - AND one was nectar elements it has two .dlls and only ONE is the correct actual application

Hello Larry and everyone,

Unfortunately I also have problems using jBridge with BIAB 2015 myself.
I bought jBridge with my BIAB 2015 upgrade.

When I launch BIAB 2015 and try to load a 64 bits VST plugin I get a message that 64 bits plugins can only be used with jBridge and that I should order it! So BIAB obviously doesnt notice the presence of jBridge on my PC. After the first message an appcrash message follows for Auxhost.exe.

When I start jBridger and follow the steps for 32 bits host I get en error message 'No valid files found' as soon as I point to a preferred folder for the jBridge adapter files. I have tried numerous times to uninstall/reinstall jBridge with and without virusscanner activated but it doesnt work.

I don't have this problem. I ran the installation of BIAB, and a day later -- because "J" took about a day to send my file -- I did install Jbridge without any changes to the install routine.

It works for me. Caveat: so far I only used SampleTank 3.

[Sonny Ray] >> There's several plugins that come with Nectar2. This is how they're noted:
iznectar2.dll


Hi Sonny Ray,

We tested Band-in-a-Box 2015 with Izotope's Nectar 2, and it's working fine for us with Band-in-a-Box 2015 with jbridge. That's both the 64 bit version and the 32 bit version.

Note that the name of the DLL to use for the 64 bit version is iZotope Nectar 2.dll (not iznectar2.dll as you noted above).
The Nectar Plugins come in various plugin types, including
"VST" : iZotope Nectar 2.dll (this works in Band-in-a-Box 2015, including 64 bit and 32 bit )
and "VST 3" : iznectar2.dll (this is a 'VST 3' format plugin, so not supported at all in Band-in-a-Box


Band-in-a-Box supports VST plugins, but not "VST 3" plugins. Most companies making VST 3' also make a VST version (as Nectar does). You can read about other software users (like Reaper) discussions about VST 3 here: http://forum.cockos.com/showthread.php?t=118616

[valentino] >> When I launch BIAB 2015 and try to load a 64 bits VST plugin I get a message that 64 bits plugins

This is likely the same issue that Sonny Ray reported. You are likely choosing the 'VST 3' version of your plugin instead of the 'VST' version. Band-in-a-Box has never supported 'VST 3' plugin format, and but we do support the more common VST standard plugins.

The message we issue is currently that it isn't a valid VST plugin, which we will elaborate on in future patches of Band-in_A_Box to tell the user if its a 'VST 3' plugin or not.

Please note that this issue isn't related to 64 bit or 32 bit, and if BiaB was a native 64 bit app, it still wouldn't support 'VST 3' plugins.

Hey Peter,

Any plans to support VST 3 or higher (3.0 came out in 2008 and 3.5 in 2011)? Any way for us to know which one we should load in BIAB? I see you identified the one for Nectar and I assume other Izotope products are similar but what about other VSTs? Any quick way for us to know in advance whether they will work in BIAB?

Thanks.

With future versions of Band-in-a-Box, there will be an error message with the version number explained. Keep in mind that VST 3 isn't just a version change, it's a different plugin system.



>>> Any plans to support VST 3 or higher (3.0 came out in 2008 and 3.5 in 2011)?

No. Here's an KVR forum poll and article on the issue, and we seem to be with the majority in sticking with VST2. As the dicussion states, most hosts (Ableton etc.) don't support VST 3, and everyone supports VST 2.

http://www.kvraudio.com/forum/viewtopic.php?p=5937353

Wow. This stuff just gets better and better doesn't it?

I've said for years now that in order to understand and use digital audio software we have to become true computer nerds and this is yet another example of it. You have to read the doc's carefully and if you don't understand something you can't make assumptions about it. You then need to Google it, read the links and before you know it another whole afternoon is out the window and you're wondering what was I trying to do again??

This is like Zero in his other thread talking about an 11gig pagefile suddenly showing up on an external drive. If that happened to me I'd be going whatinhellhappened?? too.

I mean seriously who has the time to study all this crap?

But if we're going to make serious music with this software we need to know this stuff or it's just gonna be one frustration after another.

Bob

Maybe there is something I don't understand (no surprise there) but over on the SONAR User Forum, there was quite a lot of angst for a couple of years about SONAR not supporting VST3. Now that it can, I don't hear much about it.

Yes, Matt, my understanding is that SONAR does now support VST 3.

Matt, if I recall correctly, you have a Motif Rack XS. It's editor can run as an VST3 in Sonar X3. Run the scan and it should be picked up. Sonar will put it into a separate VST section for VST3's in the VST pulldown menu along with your VST2's, also in a separate section of that pulldown.

Jeff

My understanding is that Reaper long ago concluded it would not adapt the new VST3 format. Something like, "...we don't need no stinkin new formats"

And yet.... Reaper version 5.0 Pre 1 - VST 3 now supported!


Kevin

You are correct.... Took me a while... but I confirmed this was announced on 12/21!! Holy Cow! Now why doesn't BIAB add this?

Thanks Peter for the VSTx clarification. I was able to load the 64 bit version of Nectar2 and Eventide's 64bit version of their UltraChannel. The Nectar2 resided in Programs/Steinberg/VST folders and the UltraChannel resided in Programs/CommonFiles/Steinberg/VST2 file.

So I guess I'm good to go. Thanks to everyone who sent advice/and direction. Extending to you all a Best Wishes for the Holidays and for music making in 2015.

P.S.:
And I must agree with Bob/Jazzmammal - I (we?) seem to spend a lot of time trying to figure out how to make all this software work together, time we might be spending on writing and playing songs...

When I started out "making music" I just opened my mouth and the sounds came out in song. Later when I was a teenager I was persuaded to strap on a bass guitar and play rock songs in a garage with four other guys, and eventually play the songs for kids in high school gyms, college fraternity and sorority houses and bars with those four other guys. It was easier then; but it was the Dark Ages, decades before BB/RB set us free to, among other things, re-create those songs practiced in that dusty, old garage. Now I'm using a keyboard, a mouse, and, if I want to, plug-in my bass or guitar and my microphone and sing my songs. Progress...

Thanks for the help,
SonnyRay

Hello Peter,

Thanks for your reply.

I checked my PC and found a folder named C:\Programfiles(X86)\Common Files\VST3\SSL\ containing VST3 files with extention .VST3 and I wonder if files of type .VST3 can also occur with extention .dll?

In the meantime I got a little test-app from jbridge which supplies information of a VST when loaded. For test I checked a VST from my Sonar VS DAW called Sonar VX64 Vocalstrip.dll, which is a 64 bit VST. It loads succesfully in my DAW and offers an interface.
When I run the 64 bit testapp it tells me this is a VST 2.x plugin type, so now we are sure its not a VST3, right? When I load the plugin in BIAB 2015 with jBridge installed nothing happens, no interface appears. Shoudnt this VST work in BIAB?

greetings

+1 - Now you are singing my song.

And at the risk of stirring the pot, I wish we would stop trying to use BIAB as a DAW, and I wish BIAB would stop trying to be a DAW.

nuff said, now lets have fun make some music.

Hello all,

The Sonar VX64 Vocalstrip.dll 64 bits plugin works fine now with jBridge!

By mistake I had set the focus was on a Melody Midi track instead of Audio. Though I noticed that even when pointing to the Audio track the focus was automatically set back to the Melody track in the Plugin selection dialog several times so I had to manually set it back.

Then when trying to unload the pluging from the 1st slot and set it to [None] I got a jBridge error ‘Dispatcher opcode 15 failed (VX64 VocalStrip/1129805427)’ The solution was a jBridge setting under the jBridge settings button below the Plugins interface when loaded. It is the setting: "prevent main host control when the GUI window is closed" Note that this setting is on a ‘per plugin’ basis. When I checked this setting the plugin unloaded normally and now it works fine.

Thanks for all suggestions! I hope this information is also beneficial for others.

greetings

Hey guys, I just bought jbridge for my 2015 audiofile edition of BIAB and it's not working. I'm trying to use my Waves Diamond 64 bit plugins.
When I try and add the VST Waveshell VST 9.3 x64.dll I get the same message I was getting before I installed jbridge. Any ideas???????

derryl,

It might be better to start a new thread because this one has "resolved" in its title. As a consequence, not too many people will look at it.

Regards,
Noel

• latest song: Just A Little After Midnight

Yes, the setting fixed the same problem with EmuX3 and error opcode 14. Thanks for sharing the fix!

That's not a JBridge issue its a Waves SHELL issue or a PG - Waves shell issue. I've never been able to get Waves "Waveshell" (64 or 32 bit ) to work in BIAB either.

So I just breakout all the DLL's like all other "normal" VST mfg's (i.e., "like normal folk) , see how to here

https://www.kvraudio.com/forum/viewtopic.php?t=158714

Then just call up the dll's you want like any other.

Basically download shell2vst unzip, copy the two executable's into the "c:\programs files (x86)\waves" folder (and if concerned make a copy of that folder - call it "waves-copy")

1. If you don'tt want 32-bit Waves VST's then just go to next step (2) to get just teh 64-bit ones. Now drag the "WaveShell2-VST 9.91.dll" onto the "shell2vst.exe" and it will breakout all the 32 bit dll's then copy those .dlls' to wherever you keep your 32-bit VST's (do that before next step becasue next step overwrites the 32-bit with teh 64 bit ones). if you don;t want 32 bit VST's then just go to next step

2. Now drag "WaveShell2-VST 9.91_x64.dll" onto "shell2vst64.exe" and it will breakout all the 64 bit dll's

all these broke-out .dll's, will be created in a folder called "waves" where you are at, which would be a new "waves" folder under "c:\programs files (x86)\waves"]

Larry


EDIT

FORGOT in Win 10 - you'll need to set both "shell2vst.exe" and "shell2vst64.exe" to run as Administrator, in win 7 it works without having to set those (right click on the .exe and select Properties, then select Compatibility tab then at bottom select the "Run This Program as Administrator"