G-Sonique and their 64 bit bridge

[SampleScience]

The newest G-Sonique plugin "FM Wave XR-7" and their Renegade synths have an internal bridge system. You can see it running in the background when running them in a 64 bit DAW. However, I find their F.A.Q. is confusing:

The plugins having x64 available logo in shop section have also 64bit version. The plugins marked with x64 compatible logo are 32bit, but they are working
great in any 64bit DAW using their internal bridge as Cubase, FL Studio, Reaper, Sonar etc... In DAW which don't have internal bridge for ex. Ableton or Studio
One, external bridge such a JBridge is needed to run them properly.

So, if I understand well "FM Wave XR-7" is 64-bit because they have a x64 version available for download. It's not 64 bit compatible like Renegade. But we all know that Flowstone doesn't output 64 bit plugins, so they have to use some kind of internal bridging.

Is there anyone who investigated their bridging system? I'm really curious to know how they've done it.

Note: I won't answer to any "angry" or "insulting" comments. Thank you.

[tulamide]

Just a short note, I'm not on here all too long.

If you see this logo on their page


it means that it is a 32-bit plugin able to be run bridged in a DAW. Without that logo only 32-bit DAWs are guaranteed to work. Hope this helps.

Btw. if you are interested in the FM Wave XR-7, have a look at Quilcom and Angular Momentum. Their wave draw solutions are also done with Flowstone, have even better quality - and are free

[adamszabo]

That whole G-Sonique is very confusing. They use flowstone to make plugin, which we know is 32 bit only. They also say that internal bridging can be used in hosts to load the plugin, and if the host does not support it, jbridge can be used. However, they do have their own bridging system somehow, because when I tried renegade, in the task manager there was some custom bridging thing going on, and my host loaded their plugin as 64 bit and not 32. So I dont understand how they did that, it would be great to find out.

[SampleScience]

I've found out how they did it, see my post here with screenshots:

https://www.kvraudio.com/forum/viewtopic.php?f=1&t=474333&start=15

[tulamide]

Not to sound arrogant, but what would be the advantage in binding jbridge to your plugin that will be bridged from the DAW as well? That's at least just double trouble (if there's an error report you never be sure if it is the plugin, jbridge, or the bridge of the DAW).

Some people do everything to betray their customers by telling them they would buy a 64-bit plugin while it is a 32-bit plug. I hope you all don't want to follow this ugly behavior?

[SampleScience]

Not to sound arrogant, but what would be the advantage in binding jbridge to your plugin that will be bridged from the DAW as well? That's at least just double trouble (if there's an error report you never be sure if it is the plugin, jbridge, or the bridge of the DAW).

Some people do everything to betray their customers by telling them they would buy a 64-bit plugin while it is a 32-bit plug. I hope you all don't want to follow this ugly behavior?

Well, the problem is that it's not clear what you buy. If they would make it clear, there wouldn't be any problem. My first rompler plugin was made with public domain sourced samples and I made it clear from where it came from in the product description. If I would have hid it it would be another story.

Nothing prevent a Flowstone plugin developer from doing this as long as he clearly states it in his product page description. If the jBridge is licensed and the people interested in knowing how the plugins are "64 bit compatible", then I don't see any problems.

[tulamide]

I understand your point and agree. I just wanted to point out that any hiding of mechanisms is a betrayal to the customer. For example, my DAW, just as the vast majority of all DAWs, has a built-in bridge. I would be p*ss*d off if I had to buy a plugin with an embedded bridge, disallowing me to work with what I trust.

If it is offered as a service, right on the frontpage of the VST, something in the line of:
"You are buying a licence for a 32-bit-plugin. If your DAW has no built-in bridge, we offer a special version of our plugin, that comes with an embedded bridge. It can then be used in a 64-bit DAW that has no built-in bridge. The plugin itself stays 32-bit. Please choose the special version on the checkout in that case"

That would be transparent and I'm sure customers would appreciate it. But I'm afraid some people active on these forums don't care for customers, but for having the opportunity to sell fake 64-bit plugs. (Yes, I'm pessimistic)