I Really Like Synthmaker....But...Convince Me

robrokken · 3 Sept 2009

I share some of these concerns myself, but mostly for me it's the lack of support for impulse response modules - but again, theres workarounds for that. As far as the updates go, I'm concerned here as well, It does not seem like there have been any updates to the software for some time, or problably more correctly, it seems like the updates, new versions have gone stale.

I also have serious concerns that are making me a tad uneasy. But again, I'm a noob and maybe I'm missing a lot of things heheheheheh 😀

~Rob.

Disco_Steve · 3 Sept 2009

for me the code limitatioins have helped! because you cant do db to linear conversions in the code, I dont! I work around it, and the result is faster and better, everything that is missing from the code component in my oppinion has been chosen quite carfully to not actually hinder you to badly (the lack of array import is incredibully anoying though for me but hay 🙂 ). people who do dsp are by definition very clever! so the chalenges that SM offers are quite fun sometimes.

I would greatly recomend buying it, becaue in 2 weeks you'll think to yourself, "I wonder if I an make a sound like..." its trully great value for money, even if only as a prototyping tool, you did ASM some time ago and so you will be able to pick that up.

the only way the software will get beter is if people buy it. that way money can be spent to pay for someone to fix and upgrade.

thats how I work anyhow, nothing can be done without funds 🙁

also the fact you wrot such a long post you know you like SM and want to buy it 🙂

Nu Audio Science · 3 Sept 2009

If you can already code and you can learn C++ don't bother SM is heavily limited in many ways compared to natively coded plugins If you have any thoughts of making money from plugins then put down SM now and move along CPU usage for basic things in SM is huge (Try doing some snazzy dynamicly updating GUI like a lot of EQ plugins and such have and watch the CPU spikes) RAM usage in SM is a problem and can end up being huge especially when you delete a plugin from your project and the RAM doesn't get flushed Load times on SM plugins are way way too long There is a bunch of other stuff too but if you have looked at the issues above and you know about the long term bugs (Unload an SM vst in some hosts crashes the host being a few years old now just as an example) and you are still interested then by all means jump in

The community of users here is extremely helpful and SM can do a fair bit of stuff As for the comment of "SM will only get better if you buy it" well the updates are very very slow from Outsim but we have all got used to that now and i very much am in the camp of "Let em know what they are getting into" that is why i have let you know the reality of SM not the rose tinted sales pitch 😉

NAS

ChunkyBloke · 4 Sept 2009

Thanks Rob, Steve and NAS for your comments.

Rob, I'm with you on the updates - when I came to the site to download the demo I noticed the last update to the program (and site) was nearly a year ago, and that started ringing alarm bells. Having said that, a quick look at the forum seemed to suggest that a new release with lots of bug fixes is fairly imminent. It's what may or may not come after that....

Steve, I get what you're saying about buying it because if people don't buy a product then inevitably it will die a death. But with a piece of software like this I'm looking for some kind of ongoing updates and support - in some ways the cost is irrelevant as it is the investment of my time that concerns me and is simply something I don't want to waste. If I felt comfortable that the product had that longevity and was heading in the right direction I would happily pay 3 or 4 times the price.

NAS, I've had a dual career in IT and the music industry (although not connected directly) so yes I can code, and OO is not entirely alien to me; although I've not done any serious coding for about 10 years as the music has been taking the lead. Having said that, I've downloaded the VST SDK and spent (probably not enough) time trying to digest it. For me, it almost seems like I'm looking for something in between SM and the VST SDK. The ideas I want to realise are not ground breaking, but are based on needs I find I have working day to day in the studio, so I guess they would be useful to others too. Therefore I do have in the back of my mind the idea of selling what I create, but I'm not necessarily looking to make a business out of that.

Thanks folks for your input, it hasn't helped with the decision re SM as such, but it has made me realise maybe I should spend a bit more time with the VST SDK before making my decision (and I still think SM is an amazing program, but it could be so much more 🙂 )

Chunky

ccpurno · 4 Sept 2009

I can tell you that making a succesfull commercial SM plugin is very possible and only limted by your creativity.

The whole point is: with Synthmaker, you can actually spend 90% of the time on creative DSP design. While with coding, this is a lot less. Because a lot of side issues need to be completely built up/fixed from scractch.

Also, because of the user community there are custom made solutions for most common issues to get you going.

Saving time to create new possibilities, soundwise. Not strictly technology wise... 😉

CC

Nu Audio Science · 4 Sept 2009

ccpurno wrote: I can tell you that making a succesfull commercial SM plugin is very possible and only limted by your creativity. CC

I would really like you to point me to one to prove that And when you say succesfull i am going to assume you mean making enough to keep a company afloat and pay taxes If you are talking about a couple of sales then dont bother cause plenty fo crap heap plugins have done that

NAS

Disco_Steve · 4 Sept 2009

your bang on about the time investment. the number of hours spent is really quite scary!! I too should learn the vst SDK, but as said, doing DSP is so easy in SM, creating a product, almost impossible, but DSP and fun with sound 🙂 easy.

it sounds more like you think SM isn't for you 🙁 but good luck on your journey, and don't forget to post your vst's when they are completed 🙂

Nu Audio Science · 4 Sept 2009

I think if you look at SM as a prototyping platform it simply cant be beat You are never going to build a business on SM plugins for lots of reasons but for prototyping them before going to code yes perfect

NAS

ChunkyBloke · 7 Sept 2009

Yep, I think I'm coming to the same conclusion - SM for prototyping and 'playing around' (or development as some people call it 😉 ) and the VST SDK if I want to make it a viable commercial product (low down on my list but not absent) - it can't be too hard to take a working model in SM and convert to a proper coded version, albeit the framework that it hangs on is radically different - anyone have any specific experience of that?

Just need to mull this one over a bit more but I'm leaning towards going both routes at the mo rather than choosing one over the other.

Again, thanks for everyone's input.

Chunky

infuzion · 9 Sept 2009

Another possibility is to use SynthEdit; it has a similar concept to SM with "modules connected by wires", but also has a C++ SDK, so you can hand-code your own modules using C++. There is one commercial project that has all the audio code custom-built in C++, but SynthEdit handles the graphics & VST chatter. SM lacks such a SDK, which has been requested for years.

MAX/MSP4 has a VST export, but sadly MAX5 does not & is 99% likely never will have VST exporting.

A third possibility is to buy Fruit Loops