FlowStone 3.0.9 Beta1

[Nubeat7]

sounds really good, some long requested features are here now, because i have no support licence for this version, i will wait to see 3.1, as nice as all the new features are, i'm thinking that all this should be on lower priority behind 64bit support.

I really hope that the dsp and assembler improvements are forerunners to this long overdue step.

sorry to bring it up again, but for me this looks like that there is more interest to make it more fancy then to bring a 64 bit version.

beside that, i really like the idea with public betaversions, sadly there is no way for me to get it without buying a new license.
what about the idea to make the beta version working just for one month (like the trial), so that everybody could test it?
or at least for customers with old outdated licenses to get only testers which are familiar with the program...

anyway congratulations for this update right before christmas, hopefully there are not much bugs inside to keep further development running.

[adamszabo]

Why is everyone crying about 64 bit version? All the exported plugins work perfectly fine in a 64 bit host

[tulamide]

Why is everyone crying about 64 bit version? All the exported plugins work perfectly fine in a 64 bit host

That's the issue: they don't. To run 32-bit plugins in a 64-bit host you need to bridge them. Those bridges are additional software that map 32-bit addresses to 64-bit adresses, among other things. Some DAWs already come equipped with such bridges (for example this one is very popular https://jstuff.wordpress.com/jbridge/). But not all DAWs offer these bridges and then you have to buy one for yourself, plus setting it up for use, etc. There is no free working bridge for VST plugins.

The second issue is memory. With 32-bit you are restricted to a maximum of approx. 3 GB. With 64-bit memory you can have huge sample libraries like a 10 GB Steinway, or whatever.
The current trend goes to 16 GB RAM, so expect it to be 32 GB in a year. People with that many RAM also expect their sample instruments to make use of it.

[RJHollins]

Also ... bridging can cause issues such as 'loss of focus'.

[adamszabo]

The second issue is memory.

Is memory really an issue in FlowStone plugins? If you are anyway running a 64 bit host you can load as many 32 bit plugins as your memory will allow. Plus I dont think FlowStone is really designed to make synths that use 3+ gig ram.

Regarding jbridge, I always though hosts automatically come with built in bridging? In FL Studio, and Ableton you dont need jbridge, you just simply load the 32 bit plugin and works seamlessly.

[tulamide]

The second issue is memory.

Is memory really an issue in FlowStone plugins? If you are anyway running a 64 bit host you can load as many 32 bit plugins as your memory will allow. Plus I dont think FlowStone is really designed to make synths that use 3+ gig ram.

Regarding jbridge, I always though hosts automatically come with built in bridging? In FL Studio, and Ableton you dont need jbridge, you just simply load the 32 bit plugin and works seamlessly.

Yes, memory is an issue. If you want to make a sampler that uses big libraries (compare it to Kontakt libraries and you know what I mean), you can't use Flowstone. So indeed, the 32-bit Flowstone is not designed to support todays standard of 64-bit memory addresses (needed to allow more RAM usage).

jbridge, well, that's what I said. Some DAWs come equipped with a bridge (some just integrate jbridge, other, like Reaper, have their own solution). But not all DAWs. Since you don't know what DAW your customer uses, you can't assume the plugin will run. Furthermore, this bridging needs additional processing, so all 32-bit plugins that run in a 64-bit DAW run slower. The bridge is the bottleneck for both ways of the communication. Remember, every single instruction has to be converted from 32 to 64-bit and vice-versa.

For me personally it is ok, I can live with that when making music. But most customers see it slightly different. They have a 64-bit system, a 64-bit DAW and they expect their plugins to be 64-bit as well. Just because.

[kortezzzz]

There is also the prestige and the reputation issue. Most of my potential customers were grumbling about "No mac?",
"No 64bit?". When you loose points at the prestige category, you loose the client. Its really hard to come over the "herd effect". You must keep some minimal standards today to be taken into account as a solid developer and 64bit is one of them

[TheAudiophileDutchman]

YES, I want to emphasize that many long requested features are in this beta! Thanks Devs incl. MyCo
This makes me hopeful for the next big thing, which indeed should be 64-bit

[support]

Thanks for the great reception you've all given to this new beta!

Just wanted to mention something that we hope you will all be as pleased about as we are.

I think some people may already have guessed this but huge credit for the release has to go to MyCo who has been working very closely with us recently. Almost all of the beta is down to him and we can't thank him enough for his efforts.

We're really looking forward to working with him more as the software evolves.

[Nubeat7]

Thanks for the great reception you've all given to this new beta!

Just wanted to mention something that we hope you will all be as pleased about as we are.

I think some people may already have guessed this but huge credit for the release has to go to MyCo who has been working very closely with us recently. Almost all of the beta is down to him and we can't thank him enough for his efforts.

We're really looking forward to working with him more as the software evolves.

+1