From the original SynthMaker forum (2004–2014), with its members’ names and dates.
Acrobat ·
Having lots of crashes since 1.1 was installed on my PC.. 😠
Anyway I can't claim it's SM because it's over 1 year that I have serious problems with the fan and overheating on my P4 3.4Ghz, so I'm asking if others have the same problem with 1.1...anyone having crashes since 1.1?
A.
tektoog ·
Yep !!! I confirm i went from version 1.09 to 1.1... and since i have way more crashes... It seems , i have noticed but i might be wrong, it often is related to the gestion of ASIO drivers, for example when i pass from one schematic to another...
Nu Audio Science ·
Yep well i was warning of crashes and such before 1.1 got released but everybody else said they where fine so it got released I'm afraid to say that SM has gone way down hill with the newer releases
We need a tidy up beta i think Problem is that it may be hard for Malc to find the issue if we cant round it down to whats causing it and i have had no luck as of yet pinpointing it
NAS
Acrobat ·
tektoog wrote: Yep !!! I confirm i went from version 1.09 to 1.1... and since i have way more crashes... It seems , i have noticed but i might be wrong, it often is related to the gestion of ASIO drivers, for example when i pass from one schematic to another...
exactly, I use ASIO too, exactly! closing and then reloading .osms causes crashes, so it's SM
(not my stupid P4 which I wish I never bought because it's simply a too fast monocore processor!)
Acrobat ·
ok for now I try to pass to DirectSound and see what happens... hope Malc sees this as ASIO seems very unstable ATM... 🙂
Bleah DirectSound has tremendous latency....
angstrom ·
Hmm, I usually use DirectSound and have no unusual problems. my only issue with a crash recently has been ... when I encapsulated an ASIO in.
I wonder if that's where the possible instability lies.
tektoog ·
i also noticed that all the OSMs i try and that are hooked up to an asio out module crash on my system...Each time i see this ASIO out module I directly switch it to a DS one ... So far to do that has avoided me a lot of crashes !! And bad work loss too especially when you have multiple schematics opened including the one you are working on !!!
infuzion ·
1.0.9 crashed on me 70+ times while it was official, about 20 crashes w/o SM-reporting.
Acrobat ·
Nu Audio Science wrote: Problem is that it may be hard for Malc to find the issue if we cant round it down to whats causing it and i have had no luck as of yet pinpointing it
NAS
I know, actually I'm not sure it's even ASIO since yesterday night I had another dropdown while I was using DS... I'm quite confused at the moment, the only thing for sure is I have 10X times more cradhes with the new versoion 1.1 but I can't swear since I have hardware problems concurently, so that's all... 😕
Tom7777 ·
I'm afraid to say that SM has gone way down hill with the newer releases
Indeed, i always find crashes and bugs but the more recent versions seem full of them. I have actually been using SM alot less because of it and put all project plans on hold for now and esspecially with that space bar and drag synth off screen bug in the current version, cpu usage etc, plus i have trouble building large projects due to slowdown, loading older projects and closing gives errors sometimes, host problems, smaller things don't always get fixed/added unless lots of people want them etc, i know all that sounds negative but im just being honest and for now im focussing on other things more.
malc ·
I have a feeling that alot pof the crashes may be MIDI related. Do you all use external controllers?
There's a beta coming very soon that fixes a bug in the MIDI handling that definitely causes crashes.
MichaelBenjamin ·
yes, sometimes when i switch between schematics, the controller is not recognized anymore.
aliasant ·
I have been suspecting ASIO for a long time but maybe its midi ? My MOTU Traveler soundcard also has the midiports that Im using.
Maybe all of us should post our ASIO and MIDI devices here?
I use, as I said, MOTU Traveler for both midi and ASIO.
malc ·
The MIDI problem certainly isn't hardware specific, it's an error in the code which will affect you whenever you change from one schematic to another and both use the same external device.
Acrobat ·
Now that I repaired my PC, confirmed for 1.1: closing and reloading causes crashes, sometimes with a "Runtime" error. Now I will install the beta 1.1.1 and see what happens..
electrogear ·
I'm getting crashes about every 3 or 4 times I try to open a schematic, and sometimes when pressing a key on my MIDI keyboard I get a crash also, in any schematic, there doesn't seem to be a pattern. Sometimes the sound just cuts out altogether too, again, in any schematic, it doesn't seem to be caused by one particular thing. It's getting quite irritating, really knocking my thought processes and slowing my work...
TomC ·
- no crashes during work - opening a schematic, saving it and leaving SynthMaker works - opening a schematic, doing some work, saving the schematic and leaving SynthMaker crashes on leave in 5 out of 10 cases, number increasing the longer I work on a schematic
Tom
Nu Audio Science ·
The thing is that a lot of people said this release was fine when i pointed this out before the 1.1 release Malc then had no option to release because a lot of people where saying it was all good
It's a shame because it is giving SM a bad reputation 🙁 Maybe the public beta forum should be a bit more restricted ?
NAS
malc ·
Question is, was the 1.0.9 version more stable than 1.1?
We made a huge number of fixes to existing problems that were affecting alot of people. I find it hard to believe that this wouldn't have improved things so if there are more crashes now I think the most likely reason is that we changed something during one of the fixes which in turn (unknown to us) caused some another problem to appear.
I just fixed something that was causing seemingly random crashes either out of the blue while editing or when closing. So I'm hoping that the next 1.1.1 beta will improve things.
@electrogear: can you pin this down to a repeatable case? Maybe find one schematic that will crash within say 5 times of opening and closing it in a row. Same with the audio cut out and MIDI. If I have something I can repeat then I can begin to narrow things down. Many thanks!
Acrobat ·
Nu Audio Science wrote: The thing is that a lot of people said this release was fine when i pointed this out before the 1.1 release Malc then had no option to release because a lot of people where saying it was all good
It's a shame because it is giving SM a bad reputation 🙁 Maybe the public beta forum should be a bit more restricted ?
NAS
I don't agree, NAS, there are NOT not enough people testing, in my opinion.. we need more! Then Malc can have a better picture of the situation. Where I agree with you is that it didn't passed enough time between the beta and the official version, but with such a few testers, why keeping things on hold?
@Malc, I already expressed on versions, 1.0.9 was a lot stabler..
aliasant ·
I think I get much less weird random crashes now. Sure its not rock solid and there are some new weird stuff going on. Seems like the big change Malc and Jorge did about loading times added many small bugs?
Anyways. MORE BETA TESTERS and LESS BETA WINERS.
When you get something funky, try to repeat it a couple of times. If you can repeat the errors there is probably a bug but not for sure. Also try to isolate the problem and write specifications on the steps needed to repeat the crash or what ever. And save the .osm with the right window open so Malc gets straight in to the problematic area with descriptions. If you can help Malc with that I think he can help you and us all.
Dont know how many things I have spammed Malc with that ended up being my own fault, bad code or something else embarrassing. But sometimes I hit the nail straight on and Malc finds a bug he can squash.
I actually enjoy spamming his mail with bug reports. He knows it and its quite likely he hates my mails by now =) But Ill do it anyways to help make the program better.
Nu Audio Science ·
aliasant wrote: Anyways. MORE BETA TESTERS and LESS BETA WINERS.
I'm guessing you meant whiners there yes ? Ifso then lets not start name calling please Everybody around here wants a stable package and because some people spend a vast ammount of time in SM and are having to look elsewhere to do certain things lets not start calling names OK
Some people are passionate about the things they like and all i see in this forum is pretty much a lot of love for SM so lets stop with the silliness right now
NAS
electrogear ·
Ahem... back to the bug solving:
malc wrote: @electrogear: can you pin this down to a repeatable case? Maybe find one schematic that will crash within say 5 times of opening and closing it in a row. Same with the audio cut out and MIDI. If I have something I can repeat then I can begin to narrow things down. Many thanks!
Right, try this:
After SM has crashed, the next time it is started, it should load the recovery file (although sometimes it doesn't you have to go and retrieve it yourself)... Anyway, after the recovery file has loaded, close it straight away. Open up another osm, and then close that one too. Now open up yet another osm and try to play a MIDI note.... it crashes without playing any notes.
That seems to happen for any schematic, I have just done it three times in a row with different schematics. It happens on other occasions too but this seems to be the only one I can replicate - maybe if this is fixed it will fix the other crashing bugs I've been getting.
Tom7777 ·
I'm guessing you meant whiners there yes ? Ifso then lets not start name calling please Everybody around here wants a stable package and because some people spend a vast ammount of time in SM and are having to look elsewhere to do certain things lets not start calling names OK
Some people are passionate about the things they like and all i see in this forum is pretty much a lot of love for SM so lets stop with the silliness right now
NAS
I agree fully Nas, I have been using SM now for ages quite regularly and have found tons of bugs and crashes, it's not perfect but it's getting better slowly, ignoring the bugs won't make them vanish and they can be very frustrating at times so imo theres nothing wrong at all with pointing out when theres problems.
malc ·
@electogear: Do I need to get the application to crash first then? If so, how do you go about doing this? Do the schematics have to have MIDI In enabled for some external device or does all this happen with just the PC Keyboard?
Thanks
electrogear ·
malc wrote: @electogear: Do I need to get the application to crash first then? If so, how do you go about doing this? Do the schematics have to have MIDI In enabled for some external device or does all this happen with just the PC Keyboard?
Thanks
That's the problem, you need to get it to crash first, but I'm not sure how I made it crash to begin with! I think it would work with any recovery file though if you could do something that you know will make it crash, it's the operations I mentioned after closing a recovery file that makes it crash. I'm trying to repeat it now but I'm having trouble making it crash (haha, when u want it to crash it won't!) as you need a recovery file to start the whole crashing process.... then if it crashes you can keep testing it with the generated recovery files...
The schematics that I tried it with before were all MIDI enabled yes (an M-Audio Axiom-49 if that makes any difference).
Tom7777 ·
Does anyone else notice SM is still in the processes on the Task Manager sometimes after closing or getting a crash, not sure why but i have noticed this a few times now.
Eska ·
This might be a Windows or mididriver issue. I have to wait around 10 to 20 seconds when closing my host (XT) too. (OT) I had a filter that stopped working after saving as VST. I searched 4 hours, then opened the folder again: from the two versions inside the one I used was set purgable!
Neptune ·
Tom7777 wrote: Does anyone else notice SM is still in the processes on the Task Manager sometimes after closing or getting a crash, not sure why but i have noticed this a few times now.
Never saw this after successfully closing the application (but ok i haven´t checked the TM in such a case). But after a crash it hangs sometimes in the taskmanager and can´t be removed/killed. Especially those crashes where no crash-report is created. Sometimes the process gets killed automatically after a while (10-15min) but sometimes not. I normally restart my pc if the hanging SM blocks e.g. 300MB of RAM 🙂
But this is not related to the actual SM release. It happens also with older versions.
Btw. is there really a recovery file somewhere? I never saw a recovery file after a crash. Where can i find them?
aliasant ·
The recovery file is in a folder in the Outsim/SynthMaker folder.
But there is something wrong with the whole recovery process. It works only sometimes. Havnt been able to narrow it down but it works in mysterious ways.
Andrew J ·
I think the recovery only works if the new instance of SM has a different process ID. And this doesn't always happen unless you do a restart in between.
TomC ·
Andrew J wrote: I think the recovery only works if the new instance of SM has a different process ID. And this doesn't always happen unless you do a restart in between.
Yep, that's right. If by chance your process happens to have the same ID the recovery file is ignored. Not the most elegant solution, but a workable solution. BTW, when you've ever lost a recovery file by accidentally clicking on 'Canncel' after load you'll find out that it's a good idea to run a small script at Windows startup which copies the contents of the Recovery folder to a different folder 🙂
Tom
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker