Low Virtual Memory with DivX5.0.3 encoding.

[LeonMcNichol]

Yeah... Has anyone run accross this problem? It happens when I do a dvd to avi encode. It happens when I do 2 pass (because I haven't tested 1 pass.) First off, my computer lags quite a bit. Then it gets to about halfway and either the windows error pops up saying low virtual memory, virtual dub crashes, or both. It's rather frustraiting and the sad thing is, it worked before. I did Area 88 episode 1 (50 minutes) with 2 pass encode and it went through. I went to my mom's for 3 days and came back and tried to encode Bubblegum Crash episode 1 (45 minutes) and it keeps doing this to me. Right now, I'm trying with 1 pass. (Don't like the quality 1 pass gives.)

....

Yep, ok, does it with 1 pass too. Virtualdub just crashed. (I started writing this post close to about the spot it crashes each time.) What can cause this problem? Maybe Avisynth and DivX5 aren't getting along? Possibly IVTC?

LoadPlugin("C:\PROGRA~1\GORDIA~1\mpeg2dec.dll")
LoadPlugin("C:\PROGRA~1\GORDIA~1\decomb.dll")
mpeg2source("C:\Documents and Settings\default\My Documents\Rips\Bubblegum Crash! - 01 - Illegal Army.d2v")
Telecide().Decimate(5)
crop(10,0,698,480)
BilinearResize(512,384)

-bvn1 914 -psy 1 -key 30 -log "c:\divx.log" -mv "C:\Documents and Settings\default\My Documents\Rips\Bubblegum Crash! - 01 - Illegal Army.bin" -p -b -sc 50 -pq 5 -profile 0

Can someone give me some ideas on how to fix this? Maybe tweaking something on my computer or something. I'm not that smart when it comes to "tweaking". I've never had a problem like this and it so far is only happening during dvd conversions. I did 3 mpeg-2(svcd) conversions (but only 24 minutes each) last night and they worked fine.

[BoNz1]

Yes, I had problems with this before 5.03 and even before 5.02, on my desktop. It got so bad after I while that I couldn't do anything, I couldn't surf then net or even play movies, let alone encode them. I tried everything, I played around with the cache size and did almost everything that I could possibly think of but nothing worked. Eventually, I got so frustrated with it that I decided to phone the people that sold me the computer, after approx 1.5hrs on hold they suggested to me that maybe I needed to reinstall my OS. Not too helpful, it was the next thing I was going to do. I did that and everything works now, no more virtual memory problems. However, when I shut down the computer every once in a while it will say that it is low on virtual memory. I don't think this will help you too much though, but maybe it is somewhat reassuring to know that there are others with the same problem.:)

[hakko504]

Same problem here, didn't pinpoint the source, but it seemed to get worse after I installed virtualdubmod/avisynth2.5. Adctually it got so bad that I got a BSOD with the message 'Plese reinstall WIN98SE'. I didn't. I chose Win2k instad. That could be a way of improving memory usage. What OS do you use?

[LeonMcNichol]

It's Windows XP SP1, but it's an upgrade from WinME, so it's still FAT32...

*sigh* So two people suggest a clean install of windows. Ok, I'll give that a shot tomorrow and see if that helps. (I just really hate having to reinstall all the programs I use.) Thanks for the help.

[BoNz1]

I'm using XP as well SP1, NTFS. Personally, I'd really like to isolate this problem rather than having to re-install the OS everytime this happens.:(

[Mango Madness]

(windows xp sp 1 on a duron 1ghz OCed to 1.333 (133/133) on 256meg of PC133. )

I will also report my problems. Virtualdubmod and virtualdub both crash at the end of the encode due to insufficient memory. Before this, I was having virtual memory problems but I fixed that by manually configuring the paging file to max. When looking at the task manager during encoding, divx 5.0.3 uses like 2.5gig worth of swap space which is absolutely absurd. Anyways, my problems are unsolved and renders 5.0.3 useless.

[janosch]

buhh... i am not alone :D
I made tests with DVX2.52, DVX3.0 and Virtualdub/FVAPI, all with the sam result "nicht genügend virtueller Speicher" or " not enough virtual memory".
Reinstall the OS isn't a good idea, i made it 2 days ago.
I will try something, tell you my results later.

CU
Janos

[The Edge]

Same here folks. Only happens to me when the second pass kicks in in VDub 1.4.13. I think it is related to AVISynth 2.5 as it started to happen since I installed it. Running WinXp SP1 but I believe it's not OS related. More testing needed:(

Edge

[N_F]

That's strange... I've been using DivX 5.03/VirtualDubMOD/Avisynth 2.5 beta a lot the last few days (can't get enough of seeing the speed increase of YV12 :)) without a single problem.

If anything, I belive I've noticed VDubMOD uses less memory when using YV12 compared to earlier when I used YUV12, but I may be imagining things.


Edit: BTW LeonMcNichol: Using that low (30) maximum key frame interval will give you unnecesary bad quality. The default value is 300 which I personally find too high. I usually change it to 125-150, which IMO is the perfect offset for quality/size and "searchability".

[LeonMcNichol]

I've not done the clean install yet, waiting for this dang download to finish, but if I'm not the only one, maybe it's divx5.0.3 that's causing the problem.

I have a Compaq, 1.2ghz tbird, 512mbs ram. I also recently purchased a ATI 64MB video card (before divx5.0.3 came out).

Originally posted by N_F
Edit: BTW LeonMcNichol: Using that low (30) maximum key frame interval will give you unnecesary bad quality. The default value is 300 which I personally find too high. I usually change it to 125-150, which IMO is the perfect offset for quality/size and "searchability".

Really? Quality wise, 30 seems to give a lot better results than 300. The distance between keyframes I think is too great and it gets a grainy look. If I can ever get it to encode w/o death, I'll give 125 a shot.

[Mango Madness]

Virtual memory problems can sometimes be alleviated by going into My Computer -> properties -> advanced -> performance -> advanced -> virtual memory settings and change it to custom size....i usually have mine set to minimum 384 and maximum 4096. This solved my virtual memory crashes. But, at the end of the first pass when it's saving the log files or whatever, vdub crashes with a "out of memory" error. I don't know if this is due to vdub, divx, or some funky settings elsewhere.

[The Edge]

I have found a few things that might interest some.
My page file starts to increase as soon as 2700 frames are encoded and keeps increasing until WinXP(SP1) locks.
Same if I use VirtualDubMod. B-Frame/GMC/QP/MV Hint enabled/disabled makes no difference.
Different AVIsynth script has no effect.

If I set Scene Change Threshold to 100% I get the problem at frame 2700. (Around this frame there is alot of action)
If I set Scene Change Threshold to 50% it seems fine.
Another thing I found is that if is set my starting point 1 frame ahead from beginning and start encoding, all is fine.

I have posted 2 log files. The first, if you look, stops at frame 2697 while the second has no problems.
This is what I have found at the moment but it might not be correct. If anybody else can confirm/deny this then please do.

Edge

[N_F]

Originally posted by LeonMcNichol
Really? Quality wise, 30 seems to give a lot better results than 300. The distance between keyframes I think is too great and it gets a grainy look. If I can ever get it to encode w/o death, I'll give 125 a shot.

You can try encoding at quant 2 with different keyframe values. You'll see that very low values give very high filesizes while higher values give smaller filesizes.

You'll also find that the difference in filesize is minimal after ~100 (which is the reason I find 300 to be unnecesary).

[LeonMcNichol]

Well, I clean installed windows and got rid of the comcrap, winme linger, and fat32. I'm now running a fresh windows xp sp1 ntfs. (Don't you just hate getting all your programs you are used to again and then installing them all?) I gave the first bubblegum crash! episode a try again and it went through. All 5 passes! I set the keyframe interval to 125 and it looks pretty good. One thing I noticed though, pass 2 and pass 3 were not the same size, but pass 4 and 5 were almost exact! Two and three got a little larger each time. (In KB that is, MB they were all 306. ;) ) And again, compairing between pass 2 and 5, pass 5 is much better. Each frame I compair comes out sharper and better. (And I'm using bilinear resize to boot.) The blocks that can somewhat be seen in high motion scenes are almost non-existant in pass 5.

I'll have to give another test for the virtual memory issue, because I was able to encode one whole 50 minute episode before and after that, it died.

[janosch]

I'm now running a fresh windows xp sp1 ntfs with all postfixes.
I have 1 GB RAM and 5 GB pagefile. VirtualDub crashes with a "out of memory" error. Has anybody found a solution ?

[The Edge]

If I set Scene Change Threshold to 100% I get the problem at frame 2700. (Around this frame there is alot of action)
If I set Scene Change Threshold to 50% it seems fine.
Another thing I found is that if is set my starting point 1 frame ahead from beginning and start encoding, all is fine.

Both of the above seem to fix the issue for me.

Edge