We create a feature list for the next update fee?

[Tzarls]

The included multisample with velocity layers looks nice. Now, velocity layers were totlly doable before this update (I even had some kind of round-robbing thing going on) but this new feature + SFZ support looks very interesting...

Funny to see that the R&D components are still R&D....

[kirkagur]

It's progress, and it is not expensive - therefore I will not be ________

if its an open to a new way, a way of constant updates and improvements then its more then great and I will stop ______

[MichaelBenjamin]

i got the update and its definately not 2.0, more like 1.1.85 - 1.1.9 but somewhat ok for the asked price. (in goodwill i named the install folder synthmaker1.25). the sfz thing of what i thought would be some compressed soundfont embedding (i could have looked it up before) left me a bit unimpressed, since its only a text file loader primitive that passes its data to a multisampler build which could aswell be realized with 1.1.7. the pow sqrt abs and sign are good. some other high level modules are also there but i am not much interested into these.

btw the 2.0 install screws up the hom modules lookup in your program files/synthmaker1.1.7/modules/user, probably by overwriting the registry for both versions so that the old version doesnt look them up anymore, and i had to go to that stupid users/me/(hidden)AppData/roaming/whatevermicrosoftuselesssubfolder/synthmaker/modules/... and copy them there, increasing overall clutter.

[attic]

How is the MIDI to Multi Voice working with samples?

[MichaelBenjamin]

the midi multi voice is the same like in the "hidden" hex version, with one or two added (renamed) inputs. seems useful, but i did not really check them out yet, as i recently ignored voice stealing issues with setting a high enough poly.

[Andrew J]

It's progress, and it is not expensive - therefore I will not be whinging

if its an open to a new way, a way of constant updates and improvements then its more then great and I will stop whinging

Argh, you quoted me just before I edited to get rid of "whinging". Didn't want people to feel like I'm criticising them for being passionate about SM!

The big deal for me is that things are happening again, and that is good.

[djbrynte]

Did some one mention for mac?

Also why not add an real unison mode to it?

[aliasant]

The big deal for me is that things are happening again, and that is good.

Yes indeed.
If some of the last remaining bugs has been fixed as stated this might be a great restart for SM.
Hopefully we wont have to wait years to get new primitives now that there are 2 guys programming.
They have lately done much more then Malc has alone for many many years. That is promising for sure!

[tor]

The big deal for me is that things are happening again, and that is good.

Yes indeed.
If some of the last remaining bugs has been fixed as stated this might be a great restart for SM.
Hopefully we wont have to wait years to get new primitives now that there are 2 guys programming.
They have lately done much more then Malc has alone for many many years. That is promising for sure!

Thumbs up for this

[adamszabo]

ah I upgraded, and I really wished for .fxp as an option for saving presets

[Tom7777]

+Sub folders in the toolbox

I agree with what rl said. It looks like V2 has some good updates but it did not have a lot that interested me and currently i probably won't upgrade because the main reason is i find the toolbox is too un-organized still. It has been a while since there was any big updates so i also want to see if developments continue.

I can't see Sub folders listed so i am guessing it was not added, kind of sad really because i have been doing less audio stuff recently and this was my main request which i first asked for around 2006 or maybe before that and have bumped the request quite a lot also.

[trogluddite]

i find the toolbox is too un-organized still

If that is the main update you're after, best to stick to SM1.1.7 - the SM2 copies it's toolbox from FlowStone, which IMO makes it worse - for example, FX/Envelopes/Oscillators and more all end up in one big folder called 'DSP'. I'm still trying to tidy up the mess that this has made of my toolbox (custom modules have kept the old folder names)
There are also issues with higher GUI CPU usage, and flaky MIDI response for synths.

[Tzarls]

So in the end, what does SM2 have that makes it superior to 1.1.7? I mean, yes, you have improved compatiblity with certain hosts... but you can´t make a VSTi because it drops some MIDI notes. And the CPU usage is higher. And there are some stage[2] issues. And still not accurate green timing. This feels like a step backwards, to a date even before 1.1.2, don´t you think?

[Shifrin]

So in the end, what does SM2 have that makes it superior to 1.1.7? I mean, yes, you have improved compatiblity with certain hosts... but you can´t make a VSTi because it drops some MIDI notes. And the CPU usage is higher. And there are some stage[2] issues. And still not accurate green timing. This feels like a step backwards, to a date even before 1.1.2, don´t you think?

That's exactly why I haven't even bothered upgrading to 2.0... I'll keep 1.1.7 for prototyping algorithms.

Shif.

[Tom7777]

If that is the main update you're after, best to stick to SM1.1.7 - the SM2 copies it's toolbox from FlowStone, which IMO makes it worse - for example, FX/Envelopes/Oscillators and more all end up in one big folder called 'DSP'. I'm still trying to tidy up the mess that this has made of my toolbox (custom modules have kept the old folder names)
There are also issues with higher GUI CPU usage, and flaky MIDI response for synths.

Thanks for the info, it sounds like V2 would create even more problems for me then. I mostly just code and do non audio based projects these days although this update had me interested but me upgrading was mainly depending on if the GUI got improved.

I would have to agree with what others have said though as it seems like there is a load of new bugs and the GUI sounds like a step backwards. I didn't like having no sub folders before so if it's just large folders of modules now that seems like a huge problem.