XoechZ ·
When can we expect a bugfix update for SM 2.0?
Just curious, because I want to know if it´s worth to go back to 1.17 or wait.
XoechZ
From the original SynthMaker forum (2004–2014), with its members’ names and dates.
XoechZ ·
When can we expect a bugfix update for SM 2.0?
Just curious, because I want to know if it´s worth to go back to 1.17 or wait.
XoechZ
Jay ·
You and the rest of us are in the same boat Xoechz! We all want to know this and I would suggest mailing Outsim and ask that very question!
If you do not get a reply, I would suggest a smattering of angry posts here http://www.dsprobotics.com/support/
and here http://www.kvraudio.com/ and here http://www.soundonsound.com/forum 😈
That should get things moving 😉
Best Regards
Jay
MichaelBenjamin ·
the only way to get an useful answer and to bypass that marketing crust would probably be to email malc directly.
trogluddite ·
And remember; asking how long a bug will take to fix is like asking 'how long is a piece of string' - it takes as long as it takes, epecially for such a small programming "team". If the reply is "as long as it takes", don't be offended - it is just the nature of the beast.
MegaHurtz ·
Come on.. 😝 They lost interest, putting all the effort into DSP robotics.
XoechZ ·
MegaHurtz wrote: Come on.. 😝 They lost interest, putting all the effort into DSP robotics.
I really really hope that this is not true.
Synthmaker is a great software and I think that with the big home recording market the user interest for SM should be much bigger than for Flowstone. Or am I wrong with this?
Look at all the VST FX and instruments out there. It seems that today everyone is trying to create own plugins. SM is still unique with it´s possibilities, opening a big door for all kinds of plugin developers. Flowstone really has nothing for me, because I don´t want to control roboters and that stuff. I want to create VST plugins. But that´s just me 🙂
Are there really so much more people interested in Flowstone than in Synthmaker? I can´t believe it.
In my opiniom Outsim should put almost all of their interest into Synthmaker or many customers will losse their interest in SM.
Any if they release an update that costs money, for users who pay that money and that have payed money before, it´s just their duty to provide bugfixes if there are some. And there are many. That´s not a matter if they are interested in doing this. They simply have to in my opinion.
So could any developer who reads this tell us anything about a bugfix update?
I will also send this post per e-mail to the support team. I will tell you if I get any answer.
Acrobat ·
MegaHurtz wrote: Come on.. 😝 They lost interest, putting all the effort into DSP robotics.
By the time I came here in 2006, there was already a defectionary, Jorge. Now it's just the other guy leaving, it is natural. By now a positive person should take all what's done and thank them and go search for some other goodies from other people and decide if it's the right time to pay a debt for what was done there, collaborate or not. I mean I just say be positive, we say don't "scratch at the bottom of the barrel"! 😀
XoechZ ·
That´s the answer I got from the support:
Thanks for your email.
An update to V2 is almost ready to go. This fixes issues that come from the change we made to the code Stage() order for V2 which can cause clicks or no sound in schematics that were created in earlier versions of SM. It doesn't affect everyone but it will affect some.
This is the only clear, repeatable bug that we've pinpointed so far. You mention bug fixes, is there something in particular that you have discovered which was introduced in V2 that doesn't occur in 1.1.7? If so please do email the details through and we'll definitely take a look.
Don't believe everything you read on forums btw. There's no loss of interest in SM here!
All the best,
Malc SynthMaker
So, reading this, I think it´s better to mail all the bugs to [email removed] than posting them in the forums.
Greetings,
XoechZ
synchrony ·
201 is released
Wrote something here? To have a post removed or your name hidden, write to [email protected].