I support 64Bit development

[Father]

It seems HE doesn't have the time to do all the stuff himself, and doesn't want to hire or involve anyone else. So its gonna take a long long time to release a stable version, and start to work on 64 bit project. Beside there is that robotic side unfortunately (for us).

[tulamide]

An extreme, but probably working alternative:
Say, DSPr would be willing to branch, making a "Flowstone Audio". FA would be stripped down to only create VST/VSTi. No .exe export, no robotics, just everything needed to create VST instruments/effects. This version's code would then be shared with a few trusted people, explicitly Myco and Exo. Those would then be able to care for a VST3 port, including 64bit-support.
The stripped down version would be sold for less, say 30€, and no subscription, but in-app-purchases. This way, bugfixes would be free, while exclusive content (e.g. a reverb module, special wavetables, file-format-readers, realtime fft, etc.) would be bought if needed. Sharing the income with Myco and Exo would further motivate them to keep that branch alive, offering new content, etc.

[djbrynte]

Must be much more easier to make a bridge tool inside flowstone. So when export as 64 bit VST. its like a jbridge but much better. something behind thats not seen.

[StereoSpace]

An extreme, but probably working alternative:
Say, DSPr would be willing to branch, making a "Flowstone Audio". FA would be stripped down to only create VST/VSTi. No .exe export, no robotics, just everything needed to create VST instruments/effects. This version's code would then be shared with a few trusted people, explicitly Myco and Exo. Those would then be able to care for a VST3 port, including 64bit-support.
The stripped down version would be sold for less, say 30€, and no subscription, but in-app-purchases. This way, bugfixes would be free, while exclusive content (e.g. a reverb module, special wavetables, file-format-readers, realtime fft, etc.) would be bought if needed. Sharing the income with Myco and Exo would further motivate them to keep that branch alive, offering new content, etc.

Best idea!

[CoreStylerz]

The idea is cool but looks like: "we had synthmaker, we merged the two products (FS-SM) and then 3-4 years later we remake synthmaker"

[JHud]

I wish i would have done more research before buying. No 64bit is sad. I hope we get a free upgrade if it does come out. I did not pay for next upgrade.

[tor]

Yes I want 64bit, yesterday

[Urnsoft]

Abandonware detected

[SampleScience]

I would pay for 64 bit plugin export for Flowstone. For exe too, but it wouldn't be a priority for me.

A decent 64 bit wrapper would be the best option, and it can actually be done by a third party developer. For that kind of work, I estimate that it would cost around 10 000$ to 15 000$ to hire a programmer for this task.

Funding the money would be fairly easy, especially if someone launch a Kickstater fundraiser campaign.

Now, I would do it but lack the time to organize such an event. Did anyone already tried this and failed? I think I once saw a someone who planned to do this, but did it ever get done?

[S1User]

Not to unnecessarily pile on or anything (I'm sure there's been enough of that already)... but that's the reason I only bought the limited license, the license that's already stopped for me and doesn't include any upgrades, and why I'll likely not ever upgrade, because it can't create x64 plugins.

It has nothing to do with RAM for instruments or any of the other stuff for me really. It's only a matter of using a plugin in an x64 host without bridging, nothing else really. Some of the major hosts have built in bit bridges but some don't... and in some of them bridging can be problematic at times in some cases... though it does seem to work for the most part.

I can't imagine the potential complexity of making FS export x64 VST plugins so I'm certainly not griping that people who are way, way, way smarter than me may have some difficulty getting that done... but as to paying to help make that happen via KickStarter or something, I wouldn't personally do that.

I'm firmly in the "build it first and then I'll pay" camp.