Is FlowStone Dead?

[tryphon4]

If you are patient and use Live, then I think Max + RNBO may turn out to be the easiest way to generate something pretty/modern over the longer term and you can create Live instruments/effects now. This assumes that Cycling 74 will develop the ability to generate actual plugin U/Is in reasonably short order.

AFAIK, there is unfortunately no way to create a VST from Reaktor, the Grid or Mux.
I bought Mulab & Mux and love them but it could be really useful to be able to insert some code inside, in some cases.

[ghettosynth]

If you are patient and use Live, then I think Max + RNBO may turn out to be the easiest way to generate something pretty/modern over the longer term and you can create Live instruments/effects now. This assumes that Cycling 74 will develop the ability to generate actual plugin U/Is in reasonably short order.

AFAIK, there is unfortunately no way to create a VST from Reaktor, the Grid or Mux.
I bought Mulab & Mux and love them but it could be really useful to be able to insert some code inside, in some cases.

No, of course not, not directly at least, but you can create instruments and effects and practice all the aspects of that process that are not explicitly coding. You can also distribute your protected ensembles, for a hefty price, if you are particularly good at it. You can distribute it for free and get feedback on your ideas as well. Whether any of this has use to you has to be up to you.

I included it in the list because I think that this part of the process is often overlooked. I still like to prototype ideas in Reaktor because it is faster, largely because there are so many building blocks either built in, or available from the user library.

Whether Reaktor is useful to you as a prototyping tool, really I mean more useful than Synthedit or Flowstone on the way to an eventual product, is a function of your own goals.

[Lind0n]

Is Hise betta

Hise is not Beta, its at version 3.0 - and gets constant updates....

[Lind0n]

Is flowstone a no go for creating 64 bit plugins? Hise looks interesting, is it only for sampler type instruments?

What's best synth maker for creating in 64 bit these days for code newbies

HISE is probably the easiest way to bridge the gap to all formats, for some definition of easy.

.

Ok so this is definitely true...So, more detail: the definition of "easy" here is HISE has its own internal Reaktor-like environment and its own powerful scripting environment too, and works exactly the same way across all platforms. BUT.....apart from the pretty std learning curve with this sort of thing the not-easy thing most new users struggle with is compiling HISE to start with. So you will need a compiler(VS2xxx, XCode etc.) for each platform you want to deliver product on - and you will need to compile HISE from the open-source code provided on each platform. Why does the developer do this to you when he could just provide a compiled version on each platform for you to use? Well.... HISE uses the native compilers to build your native VST/AU/AAX products so you are going to have to learn how to set up and use a compiler in any and all cases, so you may as well learn at the outset. There's a very active support forum (see you there) where you (and many others before and after you) can get help on this (actually quite simple) process and with other development issues.

But caveat: if compiling from source code isnt something you want to do then HISE isnt probably for you - but then again neither is building native plugins...

[ghettosynth]

Is flowstone a no go for creating 64 bit plugins? Hise looks interesting, is it only for sampler type instruments?

What's best synth maker for creating in 64 bit these days for code newbies

HISE is probably the easiest way to bridge the gap to all formats, for some definition of easy.

.

Ok so this is definitely true...So, more detail: the definition of "easy" here is HISE has its own internal Reaktor-like environment and its own powerful scripting environment too, and works exactly the same way across all platforms. BUT.....apart from the pretty std learning curve with this sort of thing the not-easy thing most new users struggle with is compiling HISE to start with. So you will need a compiler(VS2xxx, XCode etc.) for each platform you want to deliver product on - and you will need to compile HISE from the open-source code provided on each platform. Why does the developer do this to you when he could just provide a compiled version on each platform for you to use? Well.... HISE uses the native compilers to build your native VST/AU/AAX products so you are going to have to learn how to set up and use a compiler in any and all cases, so you may as well learn at the outset. There's a very active support forum (see you there) where you (and many others before and after you) can get help on this (actually quite simple) process and with other development issues.

You've captured a big chunk of the detail of my comment nicely. I will add that someone new to development should not underestimate the challenge, learning curve, and expense here. It will be endless hours trying to understand the quirks of each environment (platform+target) and decrypting convoluted error messages from different parts of the build process.