VST design (last) question

Julien Bayle's icon

Hi there,

I'm looking for urgently the right framework to design VSTi & fx.

I'd need to create VST for win & osx

Juce C++ is amazing & powerful. Now I'm sure about that :)
BUT the big problem is: I have to reinvent the wheel at each corner of my journey inside VST design :p

I can deal with that but it is very time killing :-/

Synthedit or synthmaker are still in a corner of my head. . .!
but no VST osx compilation for synthmaker (not sure for SE)

I need to implement quickly some prototypes of my ideas about circular or spiraloid sequencer, drone machines etc ...

m4L is ok for me but, for different purpose, I want to open the box to users outside of Live too.

Pluggo is discontinued I know that.
But, would you have any experience, ideas for me ?

best,

Julien Bayle's icon

Hi DEvo, and thans for your feedback :)

Juce C++ is very attractive because it is very multi-platform.
Indeed, I'm a windows man and this could be a nice alternative (juce I mean) to create vst for windows + mac.

The one you quoted cannot be used on windows but indeed, I could create 2 differents source one on each platform for each final platform.

Not sure it could be the better way.
I'll dig it :)

Julien Bayle's icon

You know what, I even thought about creating max5 exe using soundflower & yoke & rewire as "external" module to use with your DAW... it would suck compared to real VST...

Julien Bayle's icon

Because it is discontinued, I'd need a safer way :)
I tested Synthedit and am retesting it now.
It works fine.
There is a nice SDK.

But it kills the osx users branch and I don't like it for many reasons.

Julien Bayle's icon

I'd dream to have an answer by mate inside Cycling74 about that :p

Still thinking about my best solution (the one that fits with my needs I mean)

prototyping with max is easy/powerful and I'm relatively comfortable with it :)

I guess the prototyping step is required before pure coding.

that annoying step named "pure Juce c++ porting from Max5 prototype" is the part that, before to have begun anything, kill my motivation.

Not because it is impossible to me, but because I really consider it as a waste of time.
I mean: in my case, with my need. porting patch to pure c++ isn't never a waste of time but my added value is more on pure sequencer concept than on implementing raw pointers etc.

Maybe I'm making a mistake here.

I'd like to discuss in that thread about that :)

oli larkin's icon

In the long term it's worth learning c++

you could combine it with a dsp library, then you don't have to reinvent the wheel. I think the BSD licensed icst-dsp library is really nice. I hope to release my own c++ library one day

----
Endless Series v3 out now - A unique synthesis and effect plugin based on the Shepard Tone auditory illusion.

Julien Bayle's icon

hi oli larkin,
if I choose a framework, I'll probably go with Juce C++

You're right about C++
I'm okay to code stuff with a Doxygen extracted docs as Jules (Juce's creator) did. I guess it would be the same with wdl-ce

But quickly prototyping with a graphical programming framework is easier.

btw, I guess I'll prototype stuff and after that, I'll port to C++
So the choice I have to do seems to be now: SynthMaker vs Max to prototype stuff before the C++

I know Max, I don't know SynthMaker ; but SynthMaker can export VST for win (which could help me to alpha test pre-release with my circle of friends)

I guess the final word for me here could be: Pluggo w/ Max5 would just be nice :)