VDuB memory issue

[badshah]

I have P4, 256 RAM & more than 5GB free space on C & 30+GB on D

I have added setmemorymax(64) in the first line of avisynth script but still VduB takes all resources and I am hardly able to do anything else ... here are the screenshots

http://img206.imageshack.us/img206/2191/vd1mt7.jpg

http://img300.imageshack.us/img300/8371/vdaq4.jpg

thanks

[neuron2]

This was covered at the VirtualDub forum. fccHandler has released an updated version that fixes it. Try the latest build here:

http://fcchandler.home.comcast.net/stable

[badshah]

This was covered at the VirtualDub forum. fccHandler has released an updated version that fixes it. Try the latest build here:

http://fcchandler.home.comcast.net/stable

thank you sir :)

[fccHandler]

Actually, what I fixed was an erroneous "out of memory" popup, which terminates the loading. But since you made it this far, that fix isn't going to help you. The true memory usage (as shown in task manager) hasn't changed.

I'm seeing a memory usage of approx. 35 MB after loading a 1 GB VOB file. I suppose that could rise to 144 MB for a joined 4+ GB VOB. Unfortunately it's a necessary evil...

I'll try to reduce the memory usage in future builds, but for right now I think it would be better for you to switch to DGMPGDec to load your VOB file(s).

[LoRd_MuldeR]

Actually, what I fixed was an erroneous "out of memory" popup, which terminates the loading. But since you made it this far, that fix isn't going to help you. The true memory usage (as shown in task manager) hasn't changed.

I'm seeing a memory usage of approx. 35 MB after loading a 1 GB VOB file. I suppose that could rise to 144 MB for a joined 4+ GB VOB. Unfortunately it's a necessary evil...

I'll try to reduce the memory usage in future builds, but for right now I think it would be better for you to switch to DGMPGDec to load your VOB file(s).

Did you ever think about creating an Index file, as Avidemux does? So you don't need to re-index the MPEG each time?

[fccHandler]

Yes, I have. But I haven't decided on a precise format yet. It needs to be well thought out, because it won't be easy to change the format later without possibly breaking stuff. For example, the in-memory index structures are still undergoing changes. (And indeed I will need to change them again to reduce memory usage.) Therefore, I'm not ready to commit the indexes to a file format just yet.

[badshah]

Actually, what I fixed was an erroneous "out of memory" popup, which terminates the loading. But since you made it this far, that fix isn't going to help you. The true memory usage (as shown in task manager) hasn't changed.

I'm seeing a memory usage of approx. 35 MB after loading a 1 GB VOB file. I suppose that could rise to 144 MB for a joined 4+ GB VOB. Unfortunately it's a necessary evil...

I'll try to reduce the memory usage in future builds, but for right now I think it would be better for you to switch to DGMPGDec to load your VOB file(s).

thats why i was wonderin why it was same even after switching to new one ... :confused:

u r right ... :)

[LoRd_MuldeR]

Yes, I have. But I haven't decided on a precise format yet. It needs to be well thought out, because it won't be easy to change the format later without possibly breaking stuff. For example, the in-memory index structures are still undergoing changes. (And indeed I will need to change them again to reduce memory usage.) Therefore, I'm not ready to commit the indexes to a file format just yet.
Maybe you can use an XML based format, which makes it easy to extend at later point...
(you can put the XML into ZIP in order to reduce filesize)