Mouse Over Help/Info popup dont wor...

DigitalWhiteByte · 31 Jan 2010

On my Machine W7 i7 x64 work

aliasant · 31 Jan 2010

DigitalWhiteByte wrote: On my Machine W7 i7 x64 work

After sleep and a fresh restart it works here too. I did have a bunch of weird SM crashes yesterday. Maybe that had something to do with it. At one point I had 2 SynthMaker apps running in TM. Nr2 got stuck some how.

Il test more today from time to time. Maybe test afte a crash to.

DigitalWhiteByte · 1 Feb 2010

I noticed that sometimes using multiple runs of ShellExecute, if any of this does not end properly, and I'm going to crash, the application closes, but the execution of synthmaker remains in memory without words, in some cases impossible to end if not restart the system.

infuzion · 3 Feb 2010

DigitalWhiteByte wrote: I noticed that sometimes using multiple runs of ShellExecute, if any of this does not end properly, and I'm going to crash, the application closes, but the execution of synthmaker remains in memory without words, in some cases impossible to end if not restart the system.

Sounds like SM is not releasing something. Good find.

sunsynth · 3 Feb 2010

When my SM crashes here it's 99% that way 🙁

AngularMomentum · 3 Feb 2010

It is not releasing images for sure...say I altered a background.png, it locks the file, even if I load a bakground1.png, the background.png is still locked. Very annoying when doing graphics and trying to write over the old file with photoshop, because you end up with a lot of files, or you have to close and open synthmaker everytime to release the image file. 🙁

aliasant · 3 Feb 2010

Having that image problem now.

All I have in this schematic are 5 images at about 1 to 10 Mb each + 5, 100 pix wide previews of the bigger ones and SM memory usage is up at 600+mb

Auto Saves takes a very long time and completely freezes SM

The OSM itself is only 34 Mb and that feels ok since the images are saved in arrays.

Hm. lol This might not be the thread for this. Sorry...

malc · 4 Feb 2010

Whoa, has this become the catchall thread ? 🙂

1. Popup Help

Sounds like this is something that came and went. I have noticed this happens occasionally too but haven't been able to work out what causes it. I have my eye on it anyway.

2. SynthMaker not fully closing

This can happen if there's a crash and the software is left waiting on a thread to return that never does. Not sure there's much that can be done about this. What we can do is look at stopping the crash in the first place so if you can find a way of replicating the crash then please do let me know and I'll look into it.

3. Locking of image files

I thought this was fixed some time ago. I dragged in an Image module and loaded up a png. I then tried editing and saving the png file and it worked fine. This was all done using 1.1.6. I'm assuming this doesn't work for you? Or are you both doing some different?

4. Slow Handling of Some Images

Are you using very high res images? SM is no Photoshop so it's not designed to cope with ultra hi res. It should be fine with images around 1600x1200. In vast majority of cases I think that they would be way smaller than that.

aliasant · 4 Feb 2010

Ll. Catch em all thread... well.

When I had the "SM used a shitoad of ram for a couple of images" problem, yes. Some of them were a little highres. I guess when a normal compressed image loads up in SM its no longer compressed. But I also saw the ram grow and grow but after some tinkering that dissapeared. At its worst SM was using above 1 gb or just about there. It also crashed a couple of times and acted very very sluggish. I have optimizsed some in my schematic now and it seems to work better. I had a some preview bitmap modules spread out in the schematic without bit reduction so that ate memory and also View Loops and I know you said something about the Navigator feedback into view loops. Maybe that is what caused the raising ram?