clipsort.log crashes machine

Does it crash on every jam, no matter how short? The longer sessions can be very RAM intensive - the extra 2GB can make a big difference.

I only did one actual jam. I did connect to an empty server for a minute to test and I WAS able to load THAT clipsort file. The jam was pretty long. It was 431M compressed and expanded to about 2.2G. Might be a file size/memory problem? This machine does just blackscreen on occasion when its loaded up.

A process on XP32 has a maximum address space of 2GB. (You can increase it to 3GB by some jiggery-pokery.) If you try to load 2.2GB of data into it, it's simply going to die horribly. Vista64 doesn't have that limit. Maybe time for a new PC...

So it uses the file size of the files worth of ram during the conversion process? Is there an ap one could use to do the conversion/decompression/combing process that doesn't? I searched around in here and I thought I saw mention of manually combining a few files. Does that require coding knowledge? New machine is on the list but keeps getting pushed back. The laptop IS the new machine for now but I don't like using it for some stuff. I'm used to a desktop.

I've not got a clipsort.log to hand right now but I don't imagine processing by hand would be much fun... There's a command line tool called "sox" which is pretty good for processing batches of files, though, so you might be able to work something out.

I just did a little dabbling with the minidumps generated. It seems all of my crashes (clipsort related and otherwise) are being caused my us122.sys I've always had trouble with those drivers, they like to disappear when I unplug the unit sometimes. They don't actually disappear but they want to rediscover and reinstall the device when it happens. Sometimes I enable the show hidden devices (I finally wrote a bat file to make it easier) and uninstall multiple instances of them there and start over. They have never been quite right on both this machine and the one I use in our practice space (both desktops). I own two of the things. They seem to work pretty good once they are actually working (until I realized my blackouts are being caused by them of course). Well, actually I did have to replace the input op-amps (first learning how to solder small scale surface devices and build a hot air torch and buy some components-online only- and solder paste...) on the second one I bought from ebay. DON'T plug or unplug with the phantom power on I found out. Only I didn't do it. It came that way! Oh well, buyer beware. At least it came with a (cheap) Shure mic. I haven't got around to trying them on the Vista64 laptop but it was on my list. I wonder if they will crash it too.

When loading a Clipsort into REAPER it normally gives an option to convert clips to wav, this should help with memory problems. Also if the pagefile is too low, even if system managed it could cause a problem, you can increase by right clicking My Computer and selecting Properties, then Advanced, then under Performance you have settings. Then in Performance you have Advanced again and in that you have Virtual Memory. It should show total Pagefile for all drives, C: is best over 2gigs, if I get problems ever I set to 3072 around 3 gigs. Some stuff can even flag up that the virtual memory is too low and it should be increased to 2gigs or more. You could set min setting to 2048 and max to 3072 this will give you 2gigs minimum up to 3 gigs. But note this takes 2 gig of hd space, if your current pagefile is say 1.8gigs then it's only going to take a further 200mb and more up to the 3 gigs when it needs to grow.