A memory allocation request failed. Maybe there is no memory ...

nilstk wrote on 6/7/2010, 4:17 PM
"A memory allocation request failed. Maybe there is no memory available or an internal error has occurred."

I'm using Magix Movie Edit Pro 16 and I have to admit that I'm really VERY dissappointed with the program.

I have a new i7 processor, 64bit, Windows 7 and 6GB RAM and it's not possible for Movie Edit to encode a video longer than 10 minutes. If the movie consists of many video files it's less than 5 minutes. If I look at my RAM, I have to say that there is more than 2GB memory left. No other (memory intensive) program has these errors, so I can exclude a memory error.

Does anybody have an idea, what to do? In my opinion I need a patch by the producer as it has to be a software error. Sometimes, even this memory errors occurs, I just click ok and can go on. On other times it appears immediately again.


Comments

rainer-listing wrote on 6/7/2010, 6:32 PM
Hi nilstk
I tried to answer this earlier, so please forgive any double post, this community keeps losing my answer and asking me to relog in. Which you would be aware of. Yes, it's a software error. I have roughly the same configuration and the same problem. It came up on the user board http://support.magix.net/boards/magix/index.php?showtopic=53072 where Erriez reported "Magix support confirmed this problem with 64-bit Windows computers and more than 4GB of RAM memory. A workaround is to reduce the amount of memory to 4GB or less by removing some memory from your computer. Unfortunately, this is probably not a solution for everyone. For now we should wait for a real MEP16 solution." Fortunately it only seems to occur with HD, I can (so far) render long mpgs without problems. 
GeocaverDan wrote on 6/9/2010, 8:22 PM
rainer-listing's answer is what I've been looking for! However it's still not able to solve my problem that has me so totally frustated that I'm ready to toss everything! I recently bought Adobe Premiers 8 and it also has the exact same problem! So why can't these software companies correct these problems? Until they can my films are at idle, and I have campground guests waiting to see the films promised and I'm stuck. I DESPERATELY NEED THIS PROBLEM SOLVED! If you Magix guys can actually solve this problem soon and make my program run smooth I would be soooo Happy!!!! P.S. my computer is a 8GB RAM designed just for video editing.
nilstk wrote on 6/24/2010, 10:17 AM
Well, removing some memory isn't a solution for me. Throwing the software out of the windows and never buy it again, is a better solution.

It's sad that I have to read that Adobe has the same issue. Looks like I will have to switch to Linux and use some free software ... ??

I would request Magix to fix this issue with highest priority !!! How can you sell such a buggy software? Today every computer has more than 4GB usually ... !?!?!?!?
lpjunior wrote on 6/29/2010, 12:19 PM
I just wanted to add that I'm getting the same error with Magix Music Maker 11 on a laptop with 2 GB of memory. This is a problem they've had for years and apparently have not bothered fixing. I'd recommend trying another program, as I plan on doing soon.
GeocaverDan wrote on 7/2/2010, 11:19 AM
Looking at all these unhappy p[eople I wonder what's on Magix mind! If you guys are out there I just downloaded the patch so my programs can now work with 64 bit computers and instead it corrupts my files and will crash when I try to burn! I'm still holding out but not for much longer!!!!!! here's my report.....06/23/2010 08:36:28 PM.927:   DLLAV32.DLL loaded, all entry points available
06/23/2010 08:36:28 PM.928:   AVSDK MsgCbFunc registered
06/23/2010 08:36:28 PM.929:   AVSDK: StatCbFunc registered
06/23/2010 08:36:39 PM.311:   AVSDK Version 9.0.193
06/23/2010 08:36:39 PM.311:   ------------ Reading Device Info ----------------
06/23/2010 08:36:39 PM.311:   AVSDK: 1 device(s) found
06/23/2010 08:36:39 PM.311:   Adapter=0  ID=1  LUN=16   E:hp DVD-RAM GH40L Revision:RB0E
06/23/2010 08:36:39 PM.312:   AVSDK: 1 record device(s) available
06/23/2010 08:36:39 PM.312:   ------------ done ----------------
06/23/2010 08:36:39 PM.599:   setting no speed limit
06/23/2010 08:36:39 PM.599:   !!! DBK error in CBurnDevSupport::InvalidateDiscInfo(): 16 - burn support - invalid device !!!
06/23/2010 08:36:55 PM.462:   setting no speed limit
06/23/2010 08:37:53 PM.146:   setting no speed limit
06/23/2010 08:38:34 PM.696:   Open Project: WABHD_Chapter_1_Shellburg -- dvd project 2010-06-23
06/23/2010 08:38:34 PM.700:   VideoMode: NTSC   Temp Dir: C:\Users\Public\Documents\MAGIX_Movie_Edit_Pro_16\Disc Images\
06/23/2010 08:38:34 PM.704:   dll version 4.4.4.6
06/23/2010 08:38:34 PM.709:   PrepareDVDVideoFiles() - Abschätzen des Splitpunktes
06/23/2010 08:38:34 PM.713:   EstimateLayerSplitPoint()...
06/23/2010 08:38:34 PM.857:   Splitpunkt 4271833088 auf Disk mit Größe 542998528
06/23/2010 08:38:34 PM.861:   Title an Stelle 0, Länge 542998528, Typ 1
06/23/2010 08:38:34 PM.865:   ... Split möglich nach aktuellem Title, -> Abbruch
06/23/2010 08:39:08 PM.291:   Step 1 of 3, Encoding movie 1 ... -------------------------- 06/23/2010 09:12:27 PM -------------------------- 06/23/2010 09:12:27 PM.133:   DLLAV32.DLL loaded, all entry points available
06/23/2010 09:12:27 PM.141:   AVSDK MsgCbFunc registered
06/23/2010 09:12:27 PM.146:   AVSDK: StatCbFunc registered
06/23/2010 09:12:27 PM.294:   AVSDK Version 9.0.193
06/23/2010 09:12:27 PM.307:   ------------ Reading Device Info ----------------
06/23/2010 09:12:27 PM.320:   AVSDK: 1 device(s) found
06/23/2010 09:12:27 PM.327:   Adapter=0  ID=1  LUN=16   E:hp DVD-RAM GH40L Revision:RB0E
06/23/2010 09:12:27 PM.334:   AVSDK: 1 record device(s) available
06/23/2010 09:12:27 PM.341:   ------------ done ----------------
06/23/2010 09:12:27 PM.613:   setting no speed limit
06/23/2010 09:12:27 PM.617:   !!! DBK error in CBurnDevSupport::InvalidateDiscInfo(): 16 - burn support - invalid device !!!
06/23/2010 09:12:40 PM.175:   Open Project: WABHD_Chapter_1_Shellburg -- dvd project 2010-06-23
06/23/2010 09:12:40 PM.178:   VideoMode: NTSC   Temp Dir: C:\Users\Public\Documents\MAGIX_Movie_Edit_Pro_16\Disc Images\
06/23/2010 09:12:40 PM.182:   dll version 4.4.4.6
06/23/2010 09:12:40 PM.188:   PrepareDVDVideoFiles() - Abschätzen des Splitpunktes
06/23/2010 09:12:40 PM.191:   EstimateLayerSplitPoint()...
06/23/2010 09:12:40 PM.337:   Splitpunkt 4271833088 auf Disk mit Größe 559382528
06/23/2010 09:12:40 PM.341:   Title an Stelle 0, Länge 559382528, Typ 1
06/23/2010 09:12:40 PM.345:   ... Split möglich nach aktuellem Title, -> Abbruch
06/23/2010 09:12:49 PM.819:   Step 1 of 3, Encoding movie 1 ...


At this point I removed Magix 16 and reloaded then downloaded the patch and as you can see it went back to its ways!!!!



----------------------- 07/02/2010 08:59:17 AM -------------------------- 07/02/2010 08:59:17 AM.396:   DLLAV32.DLL loaded, all entry points available
07/02/2010 08:59:17 AM.427:   AVSDK MsgCbFunc registered
07/02/2010 08:59:17 AM.427:   AVSDK: StatCbFunc registered
07/02/2010 08:59:17 AM.583:   AVSDK Version 9.0.193
07/02/2010 08:59:17 AM.583:   ------------ Reading Device Info ----------------
07/02/2010 08:59:17 AM.583:   AVSDK: 1 device(s) found
07/02/2010 08:59:17 AM.583:   Adapter=0  ID=1  LUN=16   E:hp DVD-RAM GH40L Revision:RB0E
07/02/2010 08:59:17 AM.583:   AVSDK: 1 record device(s) available
07/02/2010 08:59:17 AM.583:   ------------ done ----------------
07/02/2010 08:59:17 AM.879:   setting no speed limit
07/02/2010 08:59:17 AM.879:   !!! DBK error in CBurnDevSupport::InvalidateDiscInfo(): 16 - burn support - invalid device !!!
07/02/2010 08:59:30 AM.656:   Open Project: SOF_Title -- dvd project 2010-07-02
07/02/2010 08:59:30 AM.656:   VideoMode: NTSC   Temp Dir: C:\Users\The Best's\Documents\MAGIX_Movie_Edit_Pro_16\Disc Images\
07/02/2010 08:59:30 AM.671:   dll version 4.4.4.6
07/02/2010 08:59:30 AM.671:   PrepareDVDVideoFiles() - Abschätzen des Splitpunktes
07/02/2010 08:59:30 AM.671:   EstimateLayerSplitPoint()...
07/02/2010 08:59:30 AM.671:   Splitpunkt 4271833088 auf Disk mit Größe 48758784
07/02/2010 08:59:30 AM.687:   Title an Stelle 0, Länge 48758784, Typ 1
07/02/2010 08:59:30 AM.687:   ... Split möglich nach aktuellem Title, -> Abbruch
07/02/2010 08:59:30 AM.718:   Step 1 of 3, Encoding movie 1 ...
07/02/2010 09:00:18 AM.314:   Step 1 done
07/02/2010 09:00:18 AM.329:   ERROR: PrepareDVDVideoFiles() failed with errNo 5 - encoding failed
07/02/2010 09:00:18 AM.345:   !!! DBK error in BurnProject: 10 - movie encoding failed !!!
   Note I posted this here and at the Magix support site someone should have an answer somewhere.
worshipgal wrote on 1/11/2012, 5:10 PM

I have the same problem. I am using Magix 10 on a Pentium 4 with XP SP3 2gb Ram.

shauldag wrote on 3/16/2012, 1:08 AM

I had the same problem. I was in the middle of producing a documentary movie, and all of a sudden, I got that error message. It froze the whole program. The movie was in suspended animation. But what I did, was end the process, and then when I started it up again, I did not load any projects. All I did was find the project that was frozen in time, and that couldn't be loaded with out the error message, and I right clicked on it. I clicked on Show project elements, and it produced all of the elements in the file window. I started dragging them into the time line, and lo and behold, all of the effects were there too. I am talking about fades, and special effects, (The Whole Shabang). It took me about an hour to put half of it back together, and to proof it before rendering, but I rendered at 20 minutes of produced material at a time, rather than cramming the whole project into the time line, and it worked.

I then dragged the rendered video into the time line, after restarting the program, and continued to drag and drop the rest of the elements from the original project where they belonged, and viola, it is DONE!! I have 8 Gig Ram, and the two gig restriction is a little bit nuts, but when it is done a little bit at a time, it should work well. Another thing I did, was run my disk cleanup utility. It works like a charm, and I will be releasing my film this Spring. Speaking of which, I have to get going, so I can meet my deadline.

Shalom.