JBridge as VST3 - anyone know?

[RikkShow]

Does anyone know if the host JBridge will be updated to a VST3?
I never got a response from support but thought maybe someone knows.

With Cubase dropping VST2 in about a year, JBridge will not be useful unless it can run as a VST3. I have some old VST2 that I want to host and they need sandboxing to prevent crashes.

[whyterabbyt]

If it isnt, you could try subhosting the JBridge'd VST2 plugins via VST3 versions of SigMod, MetaPlugin or Bidule etc. MetaPlugin can also do the bridging part if you have 32-bit plugins and want a single mechanism.

(Another possible option would be hosting in something that still handles VST2 and wiring audio between them with BlueCat Connector or similar)

[RSL369]

If it isnt, you could try subhosting the JBridge'd VST2 plugins via VST3 versions of SigMod, MetaPlugin or Bidule etc. MetaPlugin can also do the bridging part if you have 32-bit plugins and want a single mechanism.

(Another possible option would be hosting in something that still handles VST2 and wiring audio between them with BlueCat Connector or similar)

BlueCat's Patchwork VST3 will also load both VST2 (bridged and normal) and VST3 plugins, so that's one more way to get around this problem.

Feels like jBridge will not be updated to support VST3, but we'll see.
I also sent him emails about that, he never responded.

[Sahul]

Does anyone know if the host JBridge will be updated to a VST3?
I never got a response from support but thought maybe someone knows.

With Cubase dropping VST2 in about a year, JBridge will not be useful unless it can run as a VST3. I have some old VST2 that I want to host and they need sandboxing to prevent crashes.

Joao, the developer of JBridge, told me that it was not very likely that the application would directly support VST3 in the future. That was quite some time ago. It's a pity, because for example with JUCE I think it could be implemented to support not only VST3, but also other formats like CLAP.

The solution I particularly use, and works very well, is Kushview Element, which also since version 1.0 (currently in beta) has native support for JBridge, so that it is possible to directly open 32-bit VST2 plugins through it.

[concealed identity]

Does anyone know if the host JBridge will be updated to a VST3?
I never got a response from support but thought maybe someone knows.

With Cubase dropping VST2 in about a year, JBridge will not be useful unless it can run as a VST3. I have some old VST2 that I want to host and they need sandboxing to prevent crashes.

Unless they announced something recently, I don't think Cubase is dropping VST2 in a year? They "ended support" of VST2 plugins in Cubase 14, but they are still useable. I think they just won't be providing customer support or spending resources on compatibility moving forward, but I could be wrong.

[jancivil]

I haven't used it in a project, but VE Pro Server comes in a Rosetta flavor. It will connect to Cubase in silicon native, it's in a separate process.

[umd]

I think that VST2 is like MIDI 1.0. It won't go away so soon. It works, it is consolidated.

[RikkShow]

Does anyone know if the host JBridge will be updated to a VST3?
I never got a response from support but thought maybe someone knows.

With Cubase dropping VST2 in about a year, JBridge will not be useful unless it can run as a VST3. I have some old VST2 that I want to host and they need sandboxing to prevent crashes.

Unless they announced something recently, I don't think Cubase is dropping VST2 in a year? They "ended support" of VST2 plugins in Cubase 14, but they are still useable. I think they just won't be providing customer support or spending resources on compatibility moving forward, but I could be wrong.

They actually did the announcement back in 2022 that they will completely drop VST2 like the way DirectX was dropped. Cubase 14 can actually still load them, thus it seems the date has been stretched a little, but no announcement has been made that they have changed their minds.

See this: https://helpcenter.steinberg.de/hc/en-u ... hatgpt.com

[RikkShow]

Does anyone know if the host JBridge will be updated to a VST3?
I never got a response from support but thought maybe someone knows.

With Cubase dropping VST2 in about a year, JBridge will not be useful unless it can run as a VST3. I have some old VST2 that I want to host and they need sandboxing to prevent crashes.

Joao, the developer of JBridge, told me that it was not very likely that the application would directly support VST3 in the future. That was quite some time ago. It's a pity, because for example with JUCE I think it could be implemented to support not only VST3, but also other formats like CLAP.

The solution I particularly use, and works very well, is Kushview Element, which also since version 1.0 (currently in beta) has native support for JBridge, so that it is possible to directly open 32-bit VST2 plugins through it.

Well, it is unfortunate if we end up with hosting a host that hosts a plugin. But maybe that's where it ends up.

Just for clarity, I was not asking if JBridge will be able to host a VST3, makes little sense to do. I was asking if JBridge will run as a VST3. Can you clarify, if you know, which one of the two cases Joao was responding to? Thx!

[concealed identity]

Does anyone know if the host JBridge will be updated to a VST3?
I never got a response from support but thought maybe someone knows.

With Cubase dropping VST2 in about a year, JBridge will not be useful unless it can run as a VST3. I have some old VST2 that I want to host and they need sandboxing to prevent crashes.

Unless they announced something recently, I don't think Cubase is dropping VST2 in a year? They "ended support" of VST2 plugins in Cubase 14, but they are still useable. I think they just won't be providing customer support or spending resources on compatibility moving forward, but I could be wrong.

They actually did the announcement back in 2022 that they will completely drop VST2 like the way DirectX was dropped. Cubase 14 can actually still load them, thus it seems the date has been stretched a little, but no announcement has been made that they have changed their minds.

See this: https://helpcenter.steinberg.de/hc/en-u ... hatgpt.com

Thanks for following up, I didn't know they were that explicit about it. But it does say they would do that by January 2024, but Cubase 14 released way after that, so I wonder if they've reconsidered that decision or just decided to delay it.

[Sahul]

Thanks for following up, I didn't know they were that explicit about it. But it does say they would do that by January 2024, but Cubase 14 released way after that, so I wonder if they've reconsidered that decision or just decided to delay it.

Apparently they have allowed a little more time. Cubase 14 still supports VST2, but it is disabled by default. The user has to activate it.

[Sahul]

Does anyone know if the host JBridge will be updated to a VST3?
I never got a response from support but thought maybe someone knows.

With Cubase dropping VST2 in about a year, JBridge will not be useful unless it can run as a VST3. I have some old VST2 that I want to host and they need sandboxing to prevent crashes.

Joao, the developer of JBridge, told me that it was not very likely that the application would directly support VST3 in the future. That was quite some time ago. It's a pity, because for example with JUCE I think it could be implemented to support not only VST3, but also other formats like CLAP.

The solution I particularly use, and works very well, is Kushview Element, which also since version 1.0 (currently in beta) has native support for JBridge, so that it is possible to directly open 32-bit VST2 plugins through it.

Well, it is unfortunate if we end up with hosting a host that hosts a plugin. But maybe that's where it ends up.

Just for clarity, I was not asking if JBridge will be able to host a VST3, makes little sense to do. I was asking if JBridge will run as a VST3. Can you clarify, if you know, which one of the two cases Joao was responding to? Thx!

I asked specifically about Jbridge itself running as VST3. As you say, supporting VST3 32-bit plugins won't have much sense at this point.

[Sahul]

BTW, Kushview Element v1.0 is finally out of alpha these days, with beta 1 made just public, and including basic CLAP support:

https://github.com/kushview/element/rel ... ag/1.0.0b1

[MFXxx]

Im just looking into this and recall using https://www.hermannseib.com/english/savihost.htm
Will see if it works - unless someone beats me to it

[whyterabbyt]

Im just looking into this and recall using https://www.hermannseib.com/english/savihost.htm
Will see if it works - unless someone beats me to it

Savihost is a standalone host for one plugin at a time. As far as Im aware, it doesnt run in any way that would allow a plugin it hosts to be usable by another host, ie as a plugin, or a bridge or wrapper. So not capable of doing what the OP asked for.