View Full Version : Not enough memory error during mpeg 2 encode
mob47
28th March 2002, 17:59
I am trying to encode feature length DV avi to mpeg 2 with TmpgEnc. Short clips work fine, it just doesnt like large files (the one I am working on now is 12.2 gig, which is small compared to others I will be doing once I get this one to work). I have used version 2.53 and 2.02, both give the same error. I have the VFP plugin. Ideally I want to use vabiable bit rate 2 pass, but I have tried CBR and lower bit rates and still get the error, so it is a problem with the size of the file, not the settings for the encode (I have tried alot of different settings but seeing as it takes 6 hours just to see if it works or not I havent tried everything). My Win XP system has 512 meg of RAM and plenty of free HD space (around 30 gig), plus I have two hard drives and I have tried running it on both and still get the same error. I have run HD and RAM diagnostic programs and everything checks out. A friend with a PC comparable to mine (same RAM, same OS, same version of Tmpg)encoded the exact same clip I am trying to do and it worked fine. I noticed the latest encode stopped at 5:59:59, I am not sure if the time it froze on my previous attempts was the same, I do know from watching the clips that it froze at a different point in the video, but that could be due to slightly different settings, maybe it has froze at 5:59:59 every time, if that means anything to anyone. I finally did a fresh install of XP and, guess what, it didn't fix it. I know I could cut up the avi before I encode, but that is a backwords way of doing it, and I use my computer to make my living so dont want to tie things up exporting avi clips in addition to the time it's tied up encoding every night. Anyone have any solutions besides throwing my computer out the window? Thanks!
chainsaw135
29th March 2002, 00:46
Wat is your swap file setting? I've seen tmpgenc give low memory when the swap file was 2 low, also try updating windows xp before doing the next test.
mob47
29th March 2002, 01:18
Swap is set at the XP default (768-1536meg) which is the same as my friend's who tested the clip. XP is updated cuz I just reinstalled it last night. This whole thing is kinda weird.
chainsaw135
29th March 2002, 01:20
Yes i agree it's strange, hey could u swap out u're memory from your friends computer? see if that works or not.
mob47
30th March 2002, 07:07
Tried your idea of swapping my friend's RAM for mine (thanks btw), unfortunetly it didn't work (still "Not enough Memory"). What could it be that is not OS, HD, RAM or Tmpg related? (we have same OS, same version of Tmpg, and he has tried my HD and I have tried his RAM). Is there anything I am missing that goes into this equation? I also tried setting a start/end points throughout the clip and doing a batch encode to give it shorter clips to work with. I got farther this way, but I still ended up with not enough memory error before it finished. At least this way I can go back and just redo it from where I lost it, but that is not ideal. Thanks again for your help, Ill keep trying. -Jacy
da franksta
30th March 2002, 12:50
i'm afraid a lot of instability issues get labeled "not enough memory" by program by lack of a better response. really, your problem could be anything.
i understand this is not good news, but i think a fresh windows/tmpg install is the only thing that will solve your problem. just my 2 cents.
chainsaw135
30th March 2002, 21:11
@mob47 I left you a Pm messages last night, Like Da Fransta stated it could be anything thats pretty much what i was thinking at this point, Doing another clean install would not hurt for sure. If you do figure the problem out let us know tho because i'm curious hehe well good luck.
mob47
15th May 2002, 17:59
For anyone who helped me with ideas fixing this problem, I finally found a solution-buying a new motherboard and CPU. This seems to have fixed the problem, so if anyone gets the "not enough memory" error it doesn't really mean there isn't enough memory. In my case I thought it was a software problem because TMPG was the only program I was having serious problems with, look at your hardware if you get a similar error. Thanks again to anyone who offered advice. -Jacy
chainsaw135
15th May 2002, 18:08
Thats great glad you figured it out case closed:)
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.