Hi, first tried to update, but with de- and reinstall the same.
Standalone is not starting, VST is crashing the DAW (Live reaper, Tracktion Waveform).
Can't report anything else, nothing is to be seen.
Any thoughts?
thank you, horst
SynthMaster 3.1.1 is crashing
-
- KVRAF
- 19803 posts since 16 Sep, 2001 from Las Vegas,USA
Sadly I'm experiencing the same thing here with FL Studio. Constant crashes just by changing presets. I've tried every combination of "Fix Sized Buffer" options in FL and haven't come across one that is more stable than the other. FL just shuts down without any warning. None of the other two dozen or so synths in my working line up have any stability issues. (Win 11).
To be honest I don't have much time for beta testing plugins at the moment so I've had to put SM3 on the shelf for the time being.
It breaks my heart because I want SM3 to be one of my most used and favorite synths but with it being so unstable I just can't trust it at this point.
Every time I call it up I run in to one issue or the other. Some issues I have reported in various threads but some have gone unacknowledged so I don't know what the status of those reports are at this point.
I would advise KV331 to feature lock SM3 for the time being. Concentrate on working out the bugs and issues. If they keep adding more features then they'll potentially keep adding bugs and issues so it will be a never ending cycle of chasing their tails.
Maybe a sticky thread in this sub-forum just for reporting bugs and issues would help.
To be honest I don't have much time for beta testing plugins at the moment so I've had to put SM3 on the shelf for the time being.
It breaks my heart because I want SM3 to be one of my most used and favorite synths but with it being so unstable I just can't trust it at this point.
Every time I call it up I run in to one issue or the other. Some issues I have reported in various threads but some have gone unacknowledged so I don't know what the status of those reports are at this point.
I would advise KV331 to feature lock SM3 for the time being. Concentrate on working out the bugs and issues. If they keep adding more features then they'll potentially keep adding bugs and issues so it will be a never ending cycle of chasing their tails.
Maybe a sticky thread in this sub-forum just for reporting bugs and issues would help.
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe
-
- KVRAF
- 3154 posts since 10 Jan, 2005
This is not a new story to me. With SynthMaster, I've been there. I wanted it to become one of my go-to synths, but every time I started using it seriously, there were bugs, crashes, and so on (mostly bugs, to be fair). In the end, I could never use it consistently, and even though I upgraded to 3, I was hoping this would be different now, but in the meantime, I'm swimming on other beaches.Teksonik wrote: Sat Jan 25, 2025 4:36 pm Sadly I'm experiencing the same thing here with FL Studio. Constant crashes just by changing presets. I've tried every combination of "Fix Sized Buffer" options in FL and haven't come across one that is more stable than the other. FL just shuts down without any warning. None of the other two dozen or so synths in my working line up have any stability issues. (Win 11).
To be honest I don't have much time for beta testing plugins at the moment so I've had to put SM3 on the shelf for the time being.
It breaks my heart because I want SM3 to be one of my most used and favorite synths but with it being so unstable I just can't trust it at this point.
Every time I call it up I run in to one issue or the other. Some issues I have reported in various threads but some have gone unacknowledged so I don't know what the status of those reports are at this point.
I would advise KV331 to feature lock SM3 for the time being. Concentrate on working out the bugs and issues. If they keep adding more features then they'll potentially keep adding bugs and issues so it will be a never ending cycle of chasing their tails.
Maybe a sticky thread in this sub-forum just for reporting bugs and issues would help.
-
- KVRAF
- 19803 posts since 16 Sep, 2001 from Las Vegas,USA
Yes but I've been having issues with Synthmaster going back to version 2 and perhaps even longer. I stopped using SM for a quite awhile until version 3 dropped and some of the issues have gone back to the first version of 3 so rolling back is not a solution.midklang wrote: Sun Jan 26, 2025 4:29 pm HI, but you can easily fall back to 3.1.0 Revision 15897 for the moment.
horst
The point being that I'd like to help with testing of every latest version to make each one as bug and issue free as possible so again rolling back does no good.
I just don't have time to take screenshots and post them along with steps to reproduce an issue if that report is going to go unacknowledged.
That's why I suggested a Bug Report sticky thread in this sub-forum so Bulent doesn't have to try and keep up with multiple threads which contain a lot of other chatter not related to issues.
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe
-
- KVRAF
- 19803 posts since 16 Sep, 2001 from Las Vegas,USA
Yes and it's sad. SM3 has the potential to be one of the most powerful synths on the market but as I posted very early on when version 3 was announced the concentration should be on stability.mabian wrote: Sun Jan 26, 2025 7:54 pm This is not a new story to me. With SynthMaster, I've been there. I wanted it to become one of my go-to synths, but every time I started using it seriously, there were bugs, crashes, and so on (mostly bugs, to be fair). In the end, I could never use it consistently, and even though I upgraded to 3, I was hoping this would be different now, but in the meantime, I'm swimming on other beaches.
Even if a synth has every synthesis feature known to man it's no good if it can't be trusted and can take down a DAW without warning in the middle of a project.
Based solely on size of the user base and not on anyone's personal preferences, FL Studio is one of the most popular DAWs on the market so supporting it makes perfect sense from a business standpoint.
None of the other synths I own have any problems in FL Studio or have solved those problems in time (Hive 2) or have made an option switch for FL Studio (At least some of Rob Papen's synths).
So FL Studio compatibility which I understand is a pain the butt for plugin developers is none the less possible to achieve.
Again I'm willing to help but there must be a robust system in place to report issues and get feedback on them in order to make testing worth the time.
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe
-
- KVRer
- 4 posts since 2 Jul, 2022
Imho, as developer myself, if they they released 3 different Synthmaster apps, and there were never improvements on stability and bugfixing, then it's most likely never gonna change and it's a bit naive to keep having faith in ever having an usable app by just "paying again" and "upgrading again".
I see there's continuously offers for discounted prices; so seems that devs prefer get new user base, even tho they know their software is unstable & not fully usable, tempting with offers rather than committing to become reliable and fix their software in the long term.
This was the same tactic that Vodafone was using when I worked for them: _"promotion to get new users is cheaper, than fixing for the existing users"_. If the poll is big enough, it's a very winning business model, I must admit.
I mean, of course they are humans, it's ok to have regressions, bugs slipped with one release or another; but to never fix bugs that half the community is complaining about (since more than a decade!) and still trying to tempt users in buying a known-faulty product, and still focusing on releasing a new SM3 that has similar defects as the previous version, shows that the focus is on making money rather than on providing software.
Understandable, of course, as a company. But makes also user loose trust in such company in the end.
My assumption is that when they released a new SM, they never really rewrote the full app, or at least the basic engine is always the same; because the bugs are too similar from version to version, and the fact that the crashy behaviour is still there, means that not enough thought was put into figuring it out or that (if they put it) they choose to not resolve it because probably implied re-architecting the core app and that would have costed too much to them (or some other cost/benefit rationale).
But, what do I know... ; that's my interpretation of the facts; and I didn't have facts to support more positive opinions.
I see there's continuously offers for discounted prices; so seems that devs prefer get new user base, even tho they know their software is unstable & not fully usable, tempting with offers rather than committing to become reliable and fix their software in the long term.
This was the same tactic that Vodafone was using when I worked for them: _"promotion to get new users is cheaper, than fixing for the existing users"_. If the poll is big enough, it's a very winning business model, I must admit.
I mean, of course they are humans, it's ok to have regressions, bugs slipped with one release or another; but to never fix bugs that half the community is complaining about (since more than a decade!) and still trying to tempt users in buying a known-faulty product, and still focusing on releasing a new SM3 that has similar defects as the previous version, shows that the focus is on making money rather than on providing software.
Understandable, of course, as a company. But makes also user loose trust in such company in the end.
My assumption is that when they released a new SM, they never really rewrote the full app, or at least the basic engine is always the same; because the bugs are too similar from version to version, and the fact that the crashy behaviour is still there, means that not enough thought was put into figuring it out or that (if they put it) they choose to not resolve it because probably implied re-architecting the core app and that would have costed too much to them (or some other cost/benefit rationale).
But, what do I know... ; that's my interpretation of the facts; and I didn't have facts to support more positive opinions.