I support 64Bit development

[MichaelBenjamin]

.

[SampleScience]

So I've contacted a programmer to create a 64-bit wrapper for Flowstone made plugins. I was ready to pay but he said that it was way too complicated and prone to be unstable.

I'm going to see if I can find other programmer to see what are their thoughts about it.

[SampleScience]

Looks like G-Sonique made it: http://www.g-sonique.com/renegade.html

[Spogg]

Looks like G-Sonique made it: http://www.g-sonique.com/renegade.html

Is their stuff made with Flowstone then?

[adamszabo]

From the preset selector it definitely looks like FlowStone to me. I wonder how he got 64bit

[RJHollins]

From the website ...

* Our products works in most 32 / 64 BIT DAW (most of DAWs have 64 bit internal bridge or you can run plug-ins via jBridge)

[tulamide]

What RJ said, plus from the faq: "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."

To make this very clear, once and forever (please link to this post, when future questions arise):
- The current versions of Flowstone produce 32-bit code. Period.
- If you read about a plugin made with Flowstone that would have a 64-bit version - that's a lie. Period.
- Any plugin created with Flowstone can be wrapped to work in a 64-bit environment. How good it will work is solely dependent on the bridge's capabilities. Period.

(Really, this topic is so old, everyone should already know this)

[SampleScience]

Looks like G-Sonique made it: http://www.g-sonique.com/renegade.html

Is their stuff made with Flowstone then?

My guess is they use some kind of homegrown 64 bit wrapper or they licensed jBridge for distribution. I can't see how they'd make it otherwise.

- The current versions of Flowstone produce 32-bit code. Period.

Of course...

From the website ...

That's been there for a while. Maybe you're right and they are simply playing with words. I guess I'll have to buy the plugin to see what it is.

[tulamide]

My guess is they use some kind of homegrown 64 bit wrapper or they licensed jBridge for distribution. I can't see how they'd make it otherwise.

Um, no. Let me quote myself, it is taken from their faq:

What RJ said, plus from the faq: "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."

How much more clear can it be said, don't you even believe their own words?

[SampleScience]

My guess is they use some kind of homegrown 64 bit wrapper or they licensed jBridge for distribution. I can't see how they'd make it otherwise.

Um, no. Let me quote myself, it is taken from their faq:

What RJ said, plus from the faq: "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."

How much more clear can it be said, don't you even believe their own words?

Got it! Well then, they really are playing with words. Bummer...