From the original SynthMaker forum (2004–2014), with its members’ names and dates.
Panoply ·
interesting one.
I have 3gig system ram...
and crash report says there is only 2...
ohhhhh yeah, and it still crashes like a pig when trying to put together really complicated OSMs and copy/pasting - all sorts of good ones, most of much don't generate crash report screens but just dump to desktop, I've even had a BSOD!
stefan ·
Do you get the same results in Vista or XP? Windows 7 is still in beta no?
Panoply ·
hmm well, I'd love to try but my XP install is dead, and I incredibly stupidly threw away the reinstall key on the old case... so I'm left with a partial reinstall asking for a key, lol.
I'd be surprised if it was windows 7 - the kernel is very (very) similar to Vista.
Perhaps a more likely source is perhaps the triple channel nature of the ram on the x58 mobo? Possibly? But, I have no way of checking on an old OS - apart from Server 2003 R2 - but my understanding is that the kernel for this would likely be more different to XP than windows 7 would be to vista.
Open to suggestions.
sunsynth ·
It's the same in XP and was mentioned before...
stefan ·
Oh ok 🙂
Tzarls ·
Yes, I posted about this some time ago.
Wrong Data in errorlog.txt
Panoply ·
so, for the $64,000 dollar question...
is synthmaker making full use of my systems resources, or is it only seeing a fraction of it?
Considering just how much the memory usage goes up when copying complex modules... and how frequently it crashes under circumstances where it runs out of memory - which is inevitable due to copying memory usage - isn't this really quite important to have right?
Put it like this - I open a file and say it uses 250mb, something like that - if I copy an admitedly highly complex module, memory usage will very easily shoot up to well over a gig of usage.
this makes me think three things (well, repeatable ones anyway)
a) This is bizarre - how on earth can copying a subset of an OSM which runs at 250mb generate memory usage 600% in excess of the total OSM?
b) It would be really, really useful if there was some way of clearing what is in copy memory - as once SM starts gobbling memory, it is very reluctant to let it go again... even if I copy a much smaller module or primitive.
c) There is no point in sending error reports, as the information contained within is fallacious.
apologies for not posting on the original thread - I did look, but obviously not hard enough. 🙂
Andrew J ·
IIRC, unless you use the /3GB switch for Windows 32bit you can only be allocated up to 2GB of RAM. So as far as SM is concerned, the available memory it sees is 2GB.
More info here and here.
Panoply ·
hehehe nice links AndrewJ
In Vista (and hopefully 7) you can't get at win.ini, but need to use this at the command prompt. (I hope 😉)
BCDEDIT /set increaseuserva 3072
will report back. I'm also hopeful that this will allay of my out of RAM issues when saving huge projects under Cubase SX 3.
Definitely time to switch to 64bit.
Panoply ·
This does not fix the issue.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker