Notifications
Clear all

Using 32 bit plugins in Unify with JBridge 1.75

8 Posts
3 Users
1 Likes
134 Views
kpsiegel
(@kpsiegel)
Active Member
Joined: 3 months ago
Posts: 9
Topic starter  

I have several 32 bit VST2 instrument plugins that I want to use inside of Unify on Windows 10. I have a JBridge license and the latest V 1.75 software. I know that Unify supposedly supports JBridge so what is the procedure I should follow to be able to use these plugins as instrument layers in my Unify patches? I haven't seen any documentation anywhere on this. Thanks in advance for any help.


   
Quote
Topic Tags
hallenberg
(@hallenberg)
Irritant
Joined: 3 years ago
Posts: 142
 

In general I believe it just works, or it does for me. No need to create bridging files deliberately. I have my 32-bit VSTs installed in the same location as my 64-bit VSTs. When Unify scans the VST folder, the 32-bit VSTs are identified as '[jBridge] PluginName' and can be loaded like any other 64-bit VST.


   
ReplyQuote
getdunne
(@getdunne)
Illustrious Member Admin
Joined: 3 years ago
Posts: 3813
 

@kpsiegel

@hallenberg is correct. Provided you have jBridge installed on your PC, you should be able to scan/register 32-bit VSTs just like your 64-bit VSTs. They will appear in the Known Plug-Ins list with "[jBridge]" in front of the manufacturer name (e.g. "[jBridge]Daichi") and will sort at the beginning of any pop-up plug-in lists.

As @hallenberg said, it is NOT necessary to first use the jBridge app to scan your 32-bit plug-ins and make aliases of them.


   
ReplyQuote
kpsiegel
(@kpsiegel)
Active Member
Joined: 3 months ago
Posts: 9
Topic starter  

Thanks for the info guys. I did get it to work. I ended up having to uninstall JBridge and reinstall it. No big deal. I guess I will always have to use Unify inside of Ableton Live 11.1 since I can't use the wrapped VSTs anymore. That is such a trivial thing that I am not at all worried about it. Happy to be seeing these plugins again.


   
getdunne reacted
ReplyQuote
hallenberg
(@hallenberg)
Irritant
Joined: 3 years ago
Posts: 142
 
Posted by: @kpsiegel

I guess I will always have to use Unify inside of Ableton Live 11.1 since I can't use the wrapped VSTs anymore.

I believe you can but you may need to go the traditional way of creating bridge files using the jBridge app. I do this and have no problem loading wrapped VSTs in Ableton 11.1.


   
ReplyQuote
getdunne
(@getdunne)
Illustrious Member Admin
Joined: 3 years ago
Posts: 3813
 
Posted by: @hallenberg
Posted by: @kpsiegel

I guess I will always have to use Unify inside of Ableton Live 11.1 since I can't use the wrapped VSTs anymore.

I believe you can but you may need to go the traditional way of creating bridge files using the jBridge app. I do this and have no problem loading wrapped VSTs in Ableton 11.1.

If you do create bridge files, I suggest you put them all into their own special folder, and include that folder in the list that Ableton Live scans, but not in Unify's list. That way, you won't end up with two copies (the original and the bridge) of those VSTs in Unify.


   
ReplyQuote
kpsiegel
(@kpsiegel)
Active Member
Joined: 3 months ago
Posts: 9
Topic starter  

@getdunne That is what I knew I would have to do but I am not going to bother with it since it runs inside of Unify and using it as a wrapper is just fine with me.


   
ReplyQuote
kpsiegel
(@kpsiegel)
Active Member
Joined: 3 months ago
Posts: 9
Topic starter  

@zzz00m You used to be able to put a directory link in the VST2 plugin directory to your bridged VSTs but they managed to break that in the latest release (11.1.6 I believe.) I put a ticket into Ableton and never heard back. With Unify as my wrapper this is no longer an issue which is why I was so happy to see embedded support in Unify for this.


   
You reacted
ReplyQuote
Share: