|
|
| Xebarsis |
| Posted: Aug 10 2011, 10:35 AM |
 |
|
Member
Group: Members
Posts: 18
Member No.: 32296
Joined: 25-July 11
|
I'm still looking for a fix if anyone knows where I can go from here. |
|
| freedomdwarf |
| Posted: Aug 10 2011, 11:18 AM |
|
|
Advanced Member
Group: Members
Posts: 119
Member No.: 30166
Joined: 7-March 11
|
@ Xebarsis -
Have you actually considered that you might have a dicky Ram chip which is unstable?
Is your machine over-clocked in any way??
I know this is a long shot but I have had the odd problem in the past, sometimes with just 1 or 2 apps, under these conditions and there's never been any rhyme nor reason why only certain apps are affected in this way. Given the fact that you've always done things in a certain way before and it's always worked and is now crapping out, it's a distinct possibility.
Try running MemTest and/or Prime95 to check for stability - both are free.
Phaeron is right though - 32-bit apps can only access 4GB of Ram.
Seeing as you are running a 64-bit version of Windows-7, it might just be possible that the VirtualDub filters are being loaded somewhere beyond a 4GB boundary or are being given a Ram address which transcends a 4GB addressing range and can't get to it when it needs to. I know it shouldn't do that (theoretically) but nothing is beyond the realms of possibility with new OS's.
Try this for a test...
Remove some memory so you only have 2GB installed on your motherboard.
Run MemTest to make sure the machine is handling the Ram in a stable manner.
Re-boot into Windows-7 and run Prime95 for about 15-20 minutes.
If all goes well, re-do your normal thing with your videos and see if it still crashes with an out-of-memory error.
--------------------
Sometimes, intelligence means the obvious flies over your head! |
|
| dloneranger |
| Posted: Aug 10 2011, 03:22 PM |
|
|
Moderator
Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07
|
| QUOTE |
Seeing as you are running a 64-bit version of Windows-7, it might just be possible that the VirtualDub filters are being loaded somewhere beyond a 4GB boundary or are being given a Ram address which transcends a 4GB addressing range and can't get to it when it needs to. I know it shouldn't do that (theoretically) but nothing is beyond the realms of possibility with new OS's. |
Errr, no, 32bit apps on a 64bit os cannot be given a ram address that transcends a 4GB addressing range
The apps have a 4gb address space, of which they can use 2Gb (or if compiled with the option for large address aware, 3Gb)
The 64bit version of virtualdub can address more of your memory, but the codecs/plugins available are quite limited
XVid is available in 64bit though, so it'd be a good replacement for using divx
--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3 |
|
| phaeron |
| Posted: Aug 14 2011, 12:45 AM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
Something is going wrong in or above the filter chain. The crash appears to be happening because the output video frame size is abnormally large. It's not an address space issue as there is plenty free in the process (1.4GB).
Xebarsis, the crash dump you posted for 1.10.1 has a build number which indicates it was from test-11, which doesn't have the additional diagnostics from test-12 I was looking for. Try this special build, which has some additional diagnostics. In particular, open the log window before you begin the save operation, and wait for the line of text that indicates what the video filters are putting out. You'll have to manually copy down the numbers in case of a crash, but an anomaly in the specific numbers could give a clue as to what's going on. (Don't use this build for general use; among other things, it has a Sleep(1000) call in the init path.)
http://www.virtualdub.org/beta/VirtualDub-...0.1-memtest.zip
http://www.virtualdub.org/beta/VirtualDub-...mtest-AMD64.zip
http://www.virtualdub.org/beta/VirtualDub-...-memtest-src.7z
Also, I presume you're using the internal resize filter, and there aren't anomalies showing up in the filter chain window like negative numbers?
|
|
| Xebarsis |
| Posted: Sep 20 2011, 02:41 AM |
|
|
Member
Group: Members
Posts: 18
Member No.: 32296
Joined: 25-July 11
|
| QUOTE (phaeron @ Aug 14 2011, 12:45 AM) | Something is going wrong in or above the filter chain. The crash appears to be happening because the output video frame size is abnormally large. It's not an address space issue as there is plenty free in the process (1.4GB).
Xebarsis, the crash dump you posted for 1.10.1 has a build number which indicates it was from test-11, which doesn't have the additional diagnostics from test-12 I was looking for. Try this special build, which has some additional diagnostics. In particular, open the log window before you begin the save operation, and wait for the line of text that indicates what the video filters are putting out. You'll have to manually copy down the numbers in case of a crash, but an anomaly in the specific numbers could give a clue as to what's going on. (Don't use this build for general use; among other things, it has a Sleep(1000) call in the init path.)
http://www.virtualdub.org/beta/VirtualDub-...0.1-memtest.zip
http://www.virtualdub.org/beta/VirtualDub-...mtest-AMD64.zip
http://www.virtualdub.org/beta/VirtualDub-...-memtest-src.7z
Also, I presume you're using the internal resize filter, and there aren't anomalies showing up in the filter chain window like negative numbers? |
Here's what I got:
AVI: Opening file "D:\Fraps\Movies\Bloodbell2A.avi"
Beginning dub operation.
[i] Dub: Input (decompression) format is: RGB888.
[i] Dub: Output (compression) format is: RGB888.
[i] Using video filter layout: data=358262784, w=18432, h=6480, pitch=-55296,
format=7, data2=0, pitch2=0, data3=0, pitch3=0
[E] Error: Out of memory (unable to allocate 358318095 bytes)
Ending operation.
After setting the resize filter to 1280 x 720 and setting compression to the DivX codec, I saved the file as an AVI and got an error message.
Sorry for the delayed response, I've been very busy. I'll try to do a RAM test after I buy a blank CD to put it on. |
|
| dloneranger |
| Posted: Sep 20 2011, 05:40 AM |
|
|
Moderator
Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07
|
What frame size size does the file information dialog say the video is?
If I'm reading that right, virtualdub thinks it's 18432x6480
That's an enormous size if correct, or something's going wrong somewhere
Could you save the first few frames in direct stream copy mode, and post it on somewhere like rapidshare.com for examination?
--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3 |
|
| Xebarsis |
| Posted: Sep 29 2011, 05:18 AM |
|
|
Member
Group: Members
Posts: 18
Member No.: 32296
Joined: 25-July 11
|
I decided to try it again... and mysteriously it worked. I don't understand why it was having such problems, and I didn't do anything differently on VirtualDub. Only thing I can think of that I have changed on my computer recently is I disabled some programs from starting at start-up and I set the number of processors from 1 to 2. Could be related, could be unrelated; all I know is I can optimize movies again.
Thank you to those who were helpful and patient with me with trying to fix this problem. If it suddenly has problems again I'll re-post on this thread. |
|
| phaeron |
| Posted: Oct 4 2011, 05:23 AM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
Sorry, I missed the new posts to this thread earlier.
We can definitely rule out a hardware problem at this point. That 18432x6480 frame size is definitely what's causing the problem. However, we still don't know how you got to that point. I assume that the input/output frame sizes that show up in the Video Filters dialog don't look anything like that.
Anyway, let us know if it happens again. This is a strange one. |
|
| dloneranger |
| Posted: Oct 4 2011, 05:34 AM |
|
|
Moderator
Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07
|
Ah, I know what he did
He selected resize by relative % by mistake instead of absolute pixles
Resizing 1440 by 1280 % gives a width of 18432, which matches the values he had
--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3 |
|
