infuzion ·
I just d/l a new _r, & each time I try to open a new .OSM or just open SM, I get an instant crash warning. Let me know if you need the crash report. XPsp2, Athlon64, 256MB ram, Presario 3000z laptop cheers
From the original SynthMaker forum (2004–2014), with its members’ names and dates.
infuzion ·
I just d/l a new _r, & each time I try to open a new .OSM or just open SM, I get an instant crash warning. Let me know if you need the crash report. XPsp2, Athlon64, 256MB ram, Presario 3000z laptop cheers
Shifrin ·
I tried to load the example jorge posted a few weeks ago about the 'loop' function in the code component - the one that creates an additive sawtooth wave. It crashes SM as soon as I try to load it, latest version 0.9.3r. Never had this before AFAIK.
Shif.
jorge ·
infuzion wrote: I just d/l a new _r, & each time I try to open a new .OSM or just open SM, I get an instant crash warning. Let me know if you need the crash report. XPsp2, Athlon64, 256MB ram, Presario 3000z laptop cheers
What would be useful is if you do a clean install to see if the problem is related to some modules that you might have in your toolbox or to a recovery schematic.
jorge ·
Thanks for reporting it Shifrin
Shifrin wrote: I tried to load the example jorge posted a few weeks ago about the 'loop' function in the code component - the one that creates an additive sawtooth wave. It crashes SM as soon as I try to load it, latest version 0.9.3r. Never had this before AFAIK.
Shif.
When I double click on the loop.osm file, SM crashes but if I open it from File/Open, it works fine. Apart from Nildon and the loop.osm, I'm not getting any more crashes at the moment, so if anyone is getting crashes please send us the schematic, it's so much easier to fix bugs when you have a schematic to test with.
I'm sorry the last few versions got a bit unreliable due to bugs introduced when implementing arrays in the code component. We're now working on reliability as it is top priority, it should be getting a lot better.
infuzion ·
jorge wrote: What would be useful is if you do a clean install to see if the problem is related to some modules that you might have in your toolbox or to a recovery schematic.
OK... Uninstall & deleted folder: still crashes. Uninstall & deleted folder & installed _q, still crashes. Rebooted, still crashes. Uninstall & deleted folder, installed _e, opened example.osm in Windows Explorer, opened fine. Deleted folder, back to _r 6:xx pm, everything is find.
Last file opened must be kept in the registry, which isn't removed when you uninstall. I prefer that programs 100% uninstall when you use windows to uninstall (rollbacks are such pain in XP) cheers
jorge ·
infuzion wrote: OK... Uninstall & deleted folder: still crashes. Uninstall & deleted folder & installed _q, still crashes. Rebooted, still crashes. Uninstall & deleted folder, installed _e, opened example.osm in Windows Explorer, opened fine. Deleted folder, back to _r 6:xx pm, everything is find.
Last file opened must be kept in the registry, which isn't removed when you uninstall. I prefer that programs 100% uninstall when you use windows to uninstall (rollbacks are such pain in XP) cheers
Did you try renaming the last opened file to make sure it doesnt load on startup ? It would really help to know what happens in that situation. I have a feeling your crash is related to some schematic or module that SM tries to load on startup, if that's the case and you can identify which schematic/module causes the crash it would help a lot if you could send it to us.
infuzion ·
jorge wrote: Did you try renaming the last opened file to make sure it doesnt load on startup ?
I wasn't sure what file I was trying to open, but one of the later crash ERRORLOG.TXT that I saved was malc's range sliders.osm.
jorge ·
infuzion wrote: jorge wrote: Did you try renaming the last opened file to make sure it doesnt load on startup ?
I wasn't sure what file I was trying to open, but one of the later crash ERRORLOG.TXT that I saved was malc's range sliders.osm.
thanks, I'll try to recreate the crash here.
rl ·
sometimes it helps to remove the files in the recovery folder
DigitalShift ·
guys,
I have a similar issue right now. I try to open the program and it just crashes and gives me the crash page to submit it.
I was trying to view this:
"Filterscape" style knobs ;-)
and it said I did not have the latest version of synthmaker to open the file, but when I re-installed synthmaker, it no longer opens at all, just crashes.
any thoughts?
I also tried, uninstalls, delete folders, restarts, etc...no success.
thanks,
ds
BTW, I sent you guys the dump zip for review..
jorge ·
DigitalShift wrote: and it said I did not have the latest version of synthmaker to open the file, but when I re-installed synthmaker, it no longer opens at all, just crashes.
any thoughts?
I also tried, uninstalls, delete folders, restarts, etc...no success.
Yeah, if SM worked once and it stopped working after a crash it must be because it's trying to load a file that the first time it wasnt. That could be the recovery file which should be inside the recovery folder. Backup your toolbox modules ( if you have any ) and delete the whole install folder then do a clean install and let me know if it works. If you find that the problem is with the recovery file you can then go to the settings and set it up to disable the recovery feature. Let me know if you have any success with that and we can take it further then.
BTW latest version is 0.9.3t
DigitalShift ·
jorge wrote: DigitalShift wrote: and it said I did not have the latest version of synthmaker to open the file, but when I re-installed synthmaker, it no longer opens at all, just crashes.
any thoughts?
I also tried, uninstalls, delete folders, restarts, etc...no success.
Yeah, if SM worked once and it stopped working after a crash it must be because it's trying to load a file that the first time it wasnt. That could be the recovery file which should be inside the recovery folder. Backup your toolbox modules ( if you have any ) and delete the whole install folder then do a clean install and let me know if it works. If you find that the problem is with the recovery file you can then go to the settings and set it up to disable the recovery feature. Let me know if you have any success with that and we can take it further then.
BTW latest version is 0.9.3t
jorge,
thanks for such a speedy reply. I tried as suggested and was unsuccessful. I did not have any recovery files in the folder. I also removed the entire install folder, restarted, re-installed, picked up the latest version _t and also tried the same and no success.
everything was working well, i don't know what happened.
thanks for the help!
ds
jorge ·
DigitalShift, I really hope we can find out the reason why that happens. The next thing you could try is to delete the example.osm file from the install folder just in case that's causing the problem. I'm going to sleep now so we'll have to continue tomorrow.
DigitalShift ·
jorge,
I think I managed to figure out something. It seems like the application is trying to open multiple files that do not exist. What I did was that I took ALL files and deleted them, after un-installs and all.
Then I searched for any .osm files, synthmaker and outsim so I could delete those and start from scratch. I made sure all files were deleted from the trash bin as well. then I restarted.
then I re-installed version _t, did the search again for each item (.osm, synthmaker, outsim) and all was cool...then, for the .osm file, I selected to open the "example.osm" and while I was still in the search screen noticed that all the files I had opened before suddenly appeared in the search as "recent".
So I assume that the app is looking to open all these files and because it cant, it just crashes...thing is that I have no idea how I can even get around this...even if i try to open synthmaker without selecting the example file.
hope you can help.
here are some screenshots to what I refer to:
this is the initial search.
and this is the search refreshing with recent files, all being opened at the same time but that do not exist.
Note - I am not Resubmitting the search, the files appear automatically.
thanks,
ds
BTW, I also tried grabbing all those files from the various posts here and placing all of them in the directory to see if it simply needed all those files and boy, nothing.
infuzion ·
DigitalShift wrote: It seems like the application is trying to open multiple files that do not exist. What I did was that I took ALL files and deleted them, after un-installs and all.
That's exactly what it seems to me. I have sucessfully tested this:
User Workaround:
• Uninstall SM, & delete the entire install folder that uninstall doesn't catch • StartMenu/Run.../regedit • Find "osm",delete all regs found • Find "synthmaker", delete all • close regedit, Log Off Windows, log in • reinstall latest • ensure menu/Options/Application/StartupOptions = Empty Schematic, turn on Auto Recover (I use 99 seconds) Devs please:
• + a DOS switch that would atleast let me open SM without any files opening with it, even if I have SM configured to "open with most recient". • have uninstall remove everything, including registry and full install folder • have SM open empty if SM crashed last time cheers
stefan ·
I'd like to have this option in the options: "prompt about opening last opened file"
Just a "open last opened file? yes/no".
Tom7777 ·
I would like to have this option in the options - "prompt yes/no for delete folder"
I deleted another folder today by mistake, i know Jorge and Malc don't want SM to have popup messages but the option for this would be cool, i have deleted about 3 in total becuase the buttons are so close to the File part on the menu and my mouse freezes up every now and then. Its not to hard for me to get my folder back becuase i know how but for a lot of newbies to SM the fact that folder will be deleted right away may seem like a very bad thing.
DigitalShift ·
infuzion wrote: DigitalShift wrote: It seems like the application is trying to open multiple files that do not exist. What I did was that I took ALL files and deleted them, after un-installs and all.
That's exactly what it seems to me. I have sucessfully tested this:
User Workaround:
• Uninstall SM, & delete the entire install folder that uninstall doesn't catch • StartMenu/Run.../regedit • Find "osm",delete all regs found • Find "synthmaker", delete all • close regedit, Log Off Windows, log in • reinstall latest • ensure menu/Options/Application/StartupOptions = Empty Schematic, turn on Auto Recover (I use 99 seconds) Devs please:
• + a DOS switch that would atleast let me open SM without any files opening with it, even if I have SM configured to "open with most recient". • have uninstall remove everything, including registry and full install folder • have SM open empty if SM crashed last time cheers
Thanks infuzion,
using the described work-around works perfectly.
Thanks,
ds
malc ·
Hi DigitalShift,
I'm looking at this now. Will get back to you a.s.a.p.
malc ·
Ok, I must have been posting as you replied. I was trying to work out what the cause might have been so if it happens again I'll continue my investigations.
That's great that it works now - thanks infuzion for helping out here.
malc ·
Is everything ok for everyone else as well now? Let me know and I'll get on the case.
Thanks
infuzion ·
Your welcome DS & malc 🙂 malc wrote: I was trying to work out what the cause might have been so if it happens again I'll continue my investigations.
I suspect there's an registry entry .OSM with 6 or so binary entries (01 00 03 06...) that is the problem, or whatever the "Begin using SM with: most recient..." is.
Wrote something here? To have a post removed or your name hidden, write to [email protected].