Out of Memory

Trevor-Allport wrote on 4/30/2019, 11:38 AM

Ok. I find I'm fighting the software on two fronts. I can tolerate the idiosyncrasies of the audio settings with respect to my setup but now I'm getting out of memory faults and also crashes to desktop without error message. It happens during playback in which the sound just stops, it locks and crashes to desktop. All of this coincided with the latest update although I accept it may not be the cause. My current project is using 20 tracks although I have used 29 tracks with previous projects and no problem.

I have an i7 8700k CPU and 16GB of ddr4 ram so I find it hard to believe the out of memory claim. I've reinstalled MM but still get these lock-ups. It actually started on an earlier iteration of my project with pops and crackles in the sound at certain points. As I say, this was after the latest update.

What should be an enjoyable hobby is becoming a horrible chore. Is there a more reliable software out there that anyone can recommend? Because at the moment. MM is standing in the way of both my learning and enjoyment.

Comments

johnebaker wrote on 4/30/2019, 12:41 PM

@Trevor-Allport

Hi

. . . . out of memory faults and also crashes to desktop without error message. . . .

An Out of memory error occurs when no additional memory can be allocated for use by programs or the operating system, ie when all available memory including the disk swap space has been allocated, and often arises when Windows and the programs are on a SSD drive that are too small and are running low on free space - you should have at least 25% of the drives capacity free.

The first step is to identify what is causing the faulting condition, it may not be Music Maker. There are many guides on the Internet on how to do this.

. . . . 16GB of ddr4 ram so I find it hard to believe the out of memory claim . . . .

Music Maker is currently a 32 bit program, this means irrespective of how much memory you have on your system, it can only use a maximum of 4GB of memory, the claim is feasible, especially if your system drive is low on free space, or you have too many other programs running.

HTH

John EB

 

Lateral thinking can get things done!

VPX, MEP Premium, MEP 2016, and earlier versions, Music Maker Premium, Music Maker 2016, 2015.

Running Windows 10 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 1Tb + 2 x 2Tb internal HDD + 60Gb internal SSD, + 6 x 2Tb ext HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

Trevor-Allport wrote on 5/1/2019, 3:16 AM

Hi John. I freed up a hell of a lot of disk space but that did nothing.

What I have just found is that I can play the entire project back if I drop the MULTITRACK SIZE to 16384 in the MM audio buffer settings. I don't understand exactly WHY that works but I'll take it. Don't know if I'll have any further problems when recording either midi or audio but I hope not. This particular project has taken maybe about 50 hours of my time (just one tune) and I've learnt a lot on the way. A far cry from the dance tune I made in 90 minutes!

Thanks for the reply John. I'll keep you posted.

johnebaker wrote on 5/1/2019, 6:51 AM

@Trevor-Allport

Hi

. . . . I can play the entire project back if I drop the MULTITRACK SIZE to 16384 in the MM audio buffer settings . . . .

That would suggest that, at some point, the default size has been changed - the installed default is 8192 and Preview size (just in case this has also been changed) is 4096.

HTH

John EB

Lateral thinking can get things done!

VPX, MEP Premium, MEP 2016, and earlier versions, Music Maker Premium, Music Maker 2016, 2015.

Running Windows 10 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 1Tb + 2 x 2Tb internal HDD + 60Gb internal SSD, + 6 x 2Tb ext HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

Trevor-Allport wrote on 5/1/2019, 7:56 AM

Thanks for that John. I've adjusted back to default on those parameters. However, regardless of what I use for those settings, I'm getting a lock-up and out of memory error in MM when I try to playback AFTER copying a block (a bassline I handplayed) to extend it. If I delete the added chunk, it will playback ok. It seems that just extending this bassline is creating the memory error. Ironically, this part of the tune isn't very busy. There are only a few tracks playing simultaneously.

Edit: As an experiment, I randomly copied other blocks and tagged them on the end. The project plays back ok but for some reason, it doesn't like that bass I recorded from the DeepMind 12.

I've just found that the yellow line at the top which stretches between start and end of project went all the way to over 1600 bars. I also had some junk further on down which I had just shunted out of the way and kept just in case I needed them. I deleted the junk and brought the bars closer to where I am currently in the project. This seems to stop the crashes.