From the original SynthMaker forum (2004–2014), with its members’ names and dates.
Tom7777 ·
When i load this example i get a load of messages and a crash
http://www.snadsie.f2s.com/oneshotbd.osm
Also every time you load a .osm when you already have sm you will sometimes get a crash and usually no midi or sound output, it would be better if it just stayed as one copy of SM open and the new file loads as the latest schematic i think.
infuzion ·
me 2
GaryG ·
Just to clarify, that's my schematic Toms reporting; it's just one of Jorges examples (waveloop2 i think...) with the code changed so the playback freq. isn't dependant on key pressed, the cnt float is simply incremented by one.
There's also a midi filter that only allowed note 24 through.
SM 0.9.4a
It obviously worked fine last night when I saved and posted it...
.g
malc ·
Yeah we noticed that too. I'll have a look.
Tom7777 ·
Having noticed new bugs appearing in most releases since i joined the community im just wondering how regular things like this will be, not that it puts me off one bit it can just get annoying sometimes and it seems like the bugs are on a mod matrix and new ones appear ever old bug fixed 🙂 Im hoping things will get a lot more stable at some point.
Anyways even if SM had a few hundred bugs is still better the other modular apps i think 🙂
Nu Audio Science ·
I think the speed there found and fixed is a little unfair, If they weren't fixin em so quick we would just find ways around it, The difference being here that Malc and Jorge beat the shit outof em so quick it seems like there are a lot but there aren't really, Well not for a beta anyway, I do a lot of beta testing (I even get paid by one very big GFX company in free versions 🙂 ) and SM is quite good for bugs really especially considering the fact that the package can be taken in somany directions.
malc ·
It's a fair point Tom. Bear in mind though that in the last two months we've had to mess around with some pretty fundamental parts of the software. We hadn't planned to do this especially as we thought we were getting close to recahing v1. But it was all necessary.
We've found it very frustrating taking a step backwards on the stability front and it's set us back a bit in terms of our v1 plan. But I think that we're over the worst of things now and stability is much better than it was a month ago.
Of course that's my opinion, but it's yours that matters. It would be interesting to hear what you and everyone else thinks about how stable we are at the moment. Maybe I'll start another thread on this.
On the issue of bugs appearing in each release, this is something that we hope will become less of an issue as time goes on. These tend to happen more when we change fundamental of the engine or framework - ironcally this is usually when we're trying to fix another bug.
GaryG ·
Apart from todays little drama (now fixed in 0.9.4c, cheers Malc!) I've found SM remarkably stable, I've certainly had a lot more problems in general with almost all the other audio software I own (maybe not including Audiomulch, bulletproof 🙂)
If you perceive this is a problem that could harm SMs 'image' then maybe adopt the 'latest stable beta' model. Make sure people realise when a new version has wide-ranging changes so they have the option of staying with what works for them (or a parallel install, I've had no problems with different versions of SM installed simultaneously)
.g
Tom7777 ·
Well what you guys don't know is that i PM malc quite a lot reporting bugs and i have found quite a few which malc has fixed, i have also made requests for things that some will now take for granted such as key press modules and a load of general things which Malc and Jorge have added, thanks guys 🙂
Also i use SM everyday and many hours, i often make experimental projects which is why i often find bugs.
It's a fair point Tom. Bear in mind though that in the last two months we've had to mess around with some pretty fundamental parts of the software. We hadn't planned to do this especially as we thought we were getting close to recahing v1.
Well IMHO i think you should just add a bunch of these new modules now and then later on they will probably only cause basic errors.
If you perceive this is a problem that could harm SMs 'image' then maybe adopt the 'latest stable beta' model.
I always run the latest beta, i have also already found bugs in it, SM is getting more stable all the time but then comes along new bugs that set it back.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker