Potential 64 bit VST solution found

[nix]

Hi! Hope you are all well
I guess I should write to MyCo or Malc about this too-
but I would like to sound out you audio users about this too.
Recently I have had custom wraps done for 2 of my plugins to bridge to x64.
The wrap is transparent, ie. the user of the plugin has the same experience as a 64 bit plugin.
Here you can check and load these jBridge custom wraps->
https://www.sendspace.com/pro/dl/apzula
The bridging is not perfect, but it could be.
Cubase performs perfect, with some redraw issues in other hosts- Reaper, Reason & FL have been tested by myself.
What if we partnered with jBridge to provide a x64 export option?
I understand that this method reveals the extended RAM.
If DSPR had the financial resources, I'm sure jBridge could wrap us perfect for all DAWS!
What do you think?
Cheers! Nick,PhonicsAudio

[BobF]

Hello Nix,

How have you been, good I hope.

This is excellent! Yes I would contact MyCo and Malc for sure!

Also I would hope many a old Flowstoners/Synthmakers and new Flowstoners would be willing to make a small contribution to this goal.

Great find!

Take care and good luck, BobF.....

[nix]

G'day Bob mate,
Glad you like the idea!-
I'll write RDSP this week

If it takes a kitty hmm- we'd have to see how that goes

I've been pretty good- still enjoying music as much as ever...
some issues, but can't complain

[Walter Sommerfeld]

Hi Nick,

i second that idea too!

Glad to hear you enjoy music - like me

Keep on doing!

Cheers,
Walter

[adamszabo]

Hmm, I would still rather have an in house proper 64 bit export, because the crazy 64 bit people still consider briding "cheating" and thats what they will cry about next.

[Spogg]

Hmm, I would still rather have an in house proper 64 bit export, because the crazy 64 bit people still consider briding "cheating" and thats what they will cry about next.

If the bridging was somehow invisible to the end user it might be ok. The bridging would need to write a new dll with the 32 bit one embedded. I've no idea if this is even possible.

Cheers

Spogg

[tulamide]

Hmm, I would still rather have an in house proper 64 bit export, because the crazy 64 bit people still consider briding "cheating" and thats what they will cry about next.

If the bridging was somehow invisible to the end user it might be ok. The bridging would need to write a new dll with the 32 bit one embedded. I've no idea if this is even possible.

Cheers

Spogg

I'm sorry if I sound rude now, but I really just use the clearest words:
Any try to hide from the customer the fact that it is just bridged and not a real 64-bit version, is committing a fraud!

That's like, when you buy a car, but get a bicycle with the body-work of a car. A true 64-bit version is more than just a bridged 32-bit one. First of all it is 100% compatible. Then it is using double as precise floats, which results in more accurate and reliable values. And lastly, even if there were no differences at all, hiding the fact would still be fraud.

[nix]

a single .dll is not necessary IMO-
we can be transparent, and make it plainly known it is a bridge

As far as hue and cry- if it performs perfect, it allows us to use to use 64-bit DAWS directly,
I think it would be received OK
It would just require extensive crash and bug testing,
if the implementation is rock solid, it would silence protest

I offer this idea on the basis that Flowstone may never be 64-bit,
I think that may be so at this point

[Spogg]

Any try to hide from the customer the fact that it is just bridged and not a real 64-bit version, is committing a fraud!

Yes I agree. My idea was to sell it as "compatible" rather than offering it as true 64 bit but I should definitely have said so. This would be like offering "compatible" ink cartridges. The end user would need to know what they were getting.

Cheers

Spogg

[Spogg]

Any try to hide from the customer the fact that it is just bridged and not a real 64-bit version, is committing a fraud!

Yes I agree. My idea was to sell it as "compatible" rather than offering it as true 64 bit but I should definitely have said so. This would be like offering "compatible" ink cartridges. The end user would need to know what they were getting.

Cheers

Spogg

My other thought was that many users probably don't want to mess around with any bridging procedure; just install the dll and away you go.

Cheers

Spogg