View Full Version : XviD problem?!?
aketon
9th June 2004, 21:45
Hello,
I've just made an encode with the latest XviD 1.0.1 (Koepi)! Everything in the encoding went fine, but an error occurred when I tried to decode my encoded file! As I was playing the video in media player classic 6.4.8.2, suddelny it gave me some green blocks and the playback stopped and win XP gave me an error message! My first thought was, that there might be a problem with the player, so I tried other players too! All the players crashed in the same place! Then I decided to load the avi file in VirtualDub 1.5.10! When VirtualDub reached the time where every player crashed, it gave me the following:
An out-of-bounds memory access (access violation) occurred in module 'xvidcore'...
...while decompressing video frame 31694 with "XviD MPEG-4 Codec" [biCompression=44495658] (VideoSource.cpp:1772).
I can't understand the reason of this! The source was mod16!
The settings I used in XviD were:
Default settings
Trellis ON
Please HELP ME!
Thanks!
Koepi
9th June 2004, 21:48
Please take the time to find the keyframe _before_ the crash, write down the number.
Then try to go past that crashing frame and set that frame as end-frame.
Cut out that piece out of your video and save it using "direct stream copy".
Make that sample available for us so we can investigate.
Thanks!
Regards
Koepi
aketon
9th June 2004, 21:53
OK, I've done it! How can I make it available for you?:rolleyes:
I can e-mail it to you or someone else if you want! I can post the full crash info from VirtualDub if you want!
aketon
9th June 2004, 23:22
Here is the file! I hope that the link is going to work!
Sorry, the link didn't work! Is there anyone that can tell me if there is any place I can upload my file, so then someone else can download it???????
As I can't give the video to noone (for now at least)! Here is the full crash info from VirtualDub! (This crash info is from the file I cut out)
VirtualDub crash report -- build 18160 (release)
--------------------------------------
Disassembly:
018289e0: e00f loopnz 018289f1
018289e2: 6f outsd
018289e3: e90f6f5001 jmp 02d2f8f7
018289e8: 0f6f5c1001 movq mm3, [eax+edx+01]
018289ed: 0fe0c2 pavgb mm0, mm2
018289f0: 0fefd4 pxor mm2, mm4
018289f3: 0fe0cb pavgb mm1, mm3
018289f6: 8d0450 lea eax, [eax+edx*2]
018289f9: 0fefdd pxor mm3, mm5
018289fc: 0fdbd7 pand mm2, mm7
018289ff: 0fdbdf pand mm3, mm7
01828a02: 0ff8c2 psubb mm0, mm2
01828a05: 0f7f01 movq [ecx], mm0
01828a08: 0ff8cb psubb mm1, mm3
01828a0b: 0f7f0c11 movq [ecx+edx], mm1
01828a0f: 8d0c51 lea ecx, [ecx+edx*2]
01828a12: 0f6f00 movq mm0, [eax]
01828a15: 0f6f0c10 movq mm1, [eax+edx]
01828a19: 0f6fe0 movq mm4, mm0
01828a1c: 0f6fe9 movq mm5, mm1
01828a1f: 0f6f5001 movq mm2, [eax+01]
01828a23: 0f6f5c1001 movq mm3, [eax+edx+01]
01828a28: 0fe0c2 pavgb mm0, mm2
01828a2b: 0fefd4 pxor mm2, mm4
01828a2e: 0fe0cb pavgb mm1, mm3
01828a31: 8d0450 lea eax, [eax+edx*2]
01828a34: 0fefdd pxor mm3, mm5
01828a37: 0fdbd7 pand mm2, mm7
01828a3a: 0fdbdf pand mm3, mm7
01828a3d: 0ff8c2 psubb mm0, mm2
01828a40: 0f7f01 movq [ecx], mm0
01828a43: 0ff8cb psubb mm1, mm3
01828a46: 0f7f0c11 movq [ecx+edx], mm1
01828a4a: c3 ret
01828a4b: 90 nop
01828a4c: 90 nop
01828a4d: 90 nop
01828a4e: 90 nop
01828a4f: 90 nop
01828a50: 8b442410 mov eax, [esp+10]
01828a54: 8b4c2404 mov ecx, [esp+04]
01828a58: 85c0 test eax, eax
01828a5a: 8b442408 mov eax, [esp+08]
01828a5e: 8b54240c mov edx, [esp+0c]
01828a62: 0f856a000000 jnz 01828ad2
01828a68: 0f6f00 movq mm0, [eax] <-- FAULT
01828a6b: 0f6f0c10 movq mm1, [eax+edx]
01828a6f: 0fe0c1 pavgb mm0, mm1
01828a72: 0fe00c50 pavgb mm1, [eax+edx*2]
01828a76: 8d0450 lea eax, [eax+edx*2]
01828a79: 0f7f01 movq [ecx], mm0
01828a7c: 0f7f0c11 movq [ecx+edx], mm1
01828a80: 8d0c51 lea ecx, [ecx+edx*2]
01828a83: 0f6f00 movq mm0, [eax]
01828a86: 0f6f0c10 movq mm1, [eax+edx]
01828a8a: 0fe0c1 pavgb mm0, mm1
01828a8d: 0fe00c50 pavgb mm1, [eax+edx*2]
01828a91: 8d0450 lea eax, [eax+edx*2]
01828a94: 0f7f01 movq [ecx], mm0
01828a97: 0f7f0c11 movq [ecx+edx], mm1
01828a9b: 8d0c51 lea ecx, [ecx+edx*2]
01828a9e: 0f6f00 movq mm0, [eax]
01828aa1: 0f6f0c10 movq mm1, [eax+edx]
01828aa5: 0fe0c1 pavgb mm0, mm1
01828aa8: 0fe00c50 pavgb mm1, [eax+edx*2]
01828aac: 8d0450 lea eax, [eax+edx*2]
01828aaf: 0f7f01 movq [ecx], mm0
01828ab2: 0f7f0c11 movq [ecx+edx], mm1
01828ab6: 8d0c51 lea ecx, [ecx+edx*2]
01828ab9: 0f6f00 movq mm0, [eax]
01828abc: 0f6f0c10 movq mm1, [eax+edx]
01828ac0: 0fe0c1 pavgb mm0, mm1
01828ac3: 0fe00c50 pavgb mm1, [eax+edx*2]
01828ac7: 8d0450 lea eax, [eax+edx*2]
01828aca: 0f7f01 movq [ecx], mm0
01828acd: 0f7f0c11 movq [ecx+edx], mm1
01828ad1: c3 ret
01828ad2: 0f6f3db02f8d01 movq mm7, [018d2fb0]
01828ad9: 0f6f10 movq mm2, [eax]
01828adc: 01d0 add eax, edx
01828ade: 0f db 0f
01828adf: 6f outsd
Windows 5.1 (Windows XP build 2600) [Service Pack 1]
EAX = 019dffde
EBX = 00000001
ECX = 01a63180
EDX = 00000178
EBP = 000000e0
DS:ESI = 0023:000002f0
ES:EDI = 0023:018e0080
SS:ESP = 0023:0012cf68
CS:EIP = 001b:01828a68
FS = 0038
GS = 0000
EFLAGS = 00010246
FPUCW = ffff027f
FPUTW = ffffaaaa
MM0 = 2727272728282828
MM1 = 2727272728282828
MM2 = 0000000000000000
MM3 = 0000000000000000
MM4 = 8484848484848484
MM5 = 4242424242424242
MM6 = 0000000000000000
MM7 = 0101010101010101
Crash reason: Access Violation
Crash context:
An out-of-bounds memory access (access violation) occurred in module 'xvidcore'...
...while decompressing video frame 22 with "XviD MPEG-4 Codec" [biCompression=44495658] (VideoSource.cpp:1772).
Thread traces:
Thread 000007ec (Main thread)
C:\p4root\dev_stable\VirtualDub\source\VideoSource.cpp(1786)
C:\p4root\dev_stable\VirtualDub\source\VideoSource.cpp(1768)
C:\p4root\dev_stable\VirtualDub\source\VideoSource.cpp(1786)
C:\p4root\dev_stable\VirtualDub\source\VideoSource.cpp(1768)
C:\p4root\dev_stable\VirtualDub\source\VideoSource.cpp(1786)
C:\p4root\dev_stable\VirtualDub\source\VideoSource.cpp(1768)
C:\p4root\dev_stable\VirtualDub\source\VideoSource.cpp(1786)
C:\p4root\dev_stable\VirtualDub\source\VideoSource.cpp(1768)
C:\p4root\dev_stable\VirtualDub\source\VideoSource.cpp(1786)
C:\p4root\dev_stable\VirtualDub\source\VideoSource.cpp(1768)
C:\p4root\dev_stable\VirtualDub\source\VideoSource.cpp(1786)
C:\p4root\dev_stable\VirtualDub\source\VideoSource.cpp(1768)
C:\p4root\dev_stable\VirtualDub\source\VideoSource.cpp(1786)
C:\p4root\dev_stable\VirtualDub\source\VideoSource.cpp(1768)
C:\p4root\dev_stable\VirtualDub\source\VideoSource.cpp(1786)
C:\p4root\dev_stable\VirtualDub\source\VideoSource.cpp(1768)
Thread call stack:01828a68: xvidcore!xvid_plugin_dump [017c0000+57248+11820]
0180aa27: xvidcore!xvid_decore [017c0000+3fbb4+ae73]
0180f31b: xvidcore!xvid_decore [017c0000+3fbb4+f767]
0180e636: xvidcore!xvid_decore [017c0000+3fbb4+ea82]
0180f34c: xvidcore!xvid_decore [017c0000+3fbb4+f798]
0180f35d: xvidcore!xvid_decore [017c0000+3fbb4+f7a9]
0180d39e: xvidcore!xvid_decore [017c0000+3fbb4+d7ea]
01809e30: xvidcore!xvid_decore [017c0000+3fbb4+a27c]
017fffc0: xvidcore!xvid_decore [017c0000+3fbb4+40c]
01800163: xvidcore!xvid_decore [017c0000+3fbb4+5af]
01801487: xvidcore!xvid_decore [017c0000+3fbb4+18d3]
77d47981: USER32!IsZoomed [77d40000+7978+9]
5ad745c9: uxtheme!CloseThemeData [5ad70000+42d7+2f2]
77d4a9a4: USER32!GetWindowInfo [77d40000+a937+6d]
77d4aa08: USER32!GetWindowInfo [77d40000+a937+d1]
5ad73f5c: uxtheme!GetThemeColor [5ad70000+3ab8+4a4]
5ad73eee: uxtheme!GetThemeColor [5ad70000+3ab8+436]
5ad73f40: uxtheme!GetThemeColor [5ad70000+3ab8+488]
5ad73f5c: uxtheme!GetThemeColor [5ad70000+3ab8+4a4]
5ad75643: uxtheme!CloseThemeData [5ad70000+42d7+136c]
77f517e6: ntdll!RtlAllocateHeap [77f50000+16a1+145]
77f517e6: ntdll!RtlAllocateHeap [77f50000+16a1+145]
77f51778: ntdll!RtlAllocateHeap [77f50000+16a1+d7]
77f517b2: ntdll!RtlAllocateHeap [77f50000+16a1+111]
5ad71b48: uxtheme!DrawThemeParentBackground [5ad70000+1677+4d1]
77d45a7b: USER32!GetWindowThreadProcessId [77d40000+59e5+96]
77d4413c: USER32!GetWindowLongW [77d40000+40aa+92]
77d458bf: USER32!DefWindowProcW [77d40000+5846+79]
77f517e6: ntdll!RtlAllocateHeap [77f50000+16a1+145]
77f517e6: ntdll!RtlAllocateHeap [77f50000+16a1+145]
77f51778: ntdll!RtlAllocateHeap [77f50000+16a1+d7]
77f517b2: ntdll!RtlAllocateHeap [77f50000+16a1+111]
5ad73c51: uxtheme!GetThemeColor [5ad70000+3ab8+199]
77f51690: ntdll!RtlFreeHeap [77f50000+156b+125]
77f51690: ntdll!RtlFreeHeap [77f50000+156b+125]
77f5164e: ntdll!RtlFreeHeap [77f50000+156b+e3]
77f5166a: ntdll!RtlFreeHeap [77f50000+156b+ff]
77d43b4b: USER32!00003b4b
77f51690: ntdll!RtlFreeHeap [77f50000+156b+125]
77f5164e: ntdll!RtlFreeHeap [77f50000+156b+e3]
77f5166a: ntdll!RtlFreeHeap [77f50000+156b+ff]
77d47b55: USER32!SetPropW [77d40000+7af5+60]
5ad74670: uxtheme!CloseThemeData [5ad70000+42d7+399]
77f5166a: ntdll!RtlFreeHeap [77f50000+156b+ff]
77c2ab2e: msvcrt!free [77c10000+1aa6b+c3]
77c2ab33: msvcrt!free [77c10000+1aa6b+c8]
5ad740cd: uxtheme!GetThemeColor [5ad70000+3ab8+615]
77f5166a: ntdll!RtlFreeHeap [77f50000+156b+ff]
77c2ab2e: msvcrt!free [77c10000+1aa6b+c3]
77c2ab33: msvcrt!free [77c10000+1aa6b+c8]
5ad75e43: uxtheme!DrawThemeBackgroundEx [5ad70000+5a44+3ff]
77c2ab33: msvcrt!free [77c10000+1aa6b+c8]
5ad75fc0: uxtheme!DrawThemeBackgroundEx [5ad70000+5a44+57c]
77f5166a: ntdll!RtlFreeHeap [77f50000+156b+ff]
77c2ab2e: msvcrt!free [77c10000+1aa6b+c3]
77d4a9a4: USER32!GetWindowInfo [77d40000+a937+6d]
77d4aa08: USER32!GetWindowInfo [77d40000+a937+d1]
77d47981: USER32!IsZoomed [77d40000+7978+9]
5ad745c9: uxtheme!CloseThemeData [5ad70000+42d7+2f2]
5ad73eee: uxtheme!GetThemeColor [5ad70000+3ab8+436]
5ad73f40: uxtheme!GetThemeColor [5ad70000+3ab8+488]
5ad73f5c: uxtheme!GetThemeColor [5ad70000+3ab8+4a4]
5ad75643: uxtheme!CloseThemeData [5ad70000+42d7+136c]
77d458e6: USER32!DefWindowProcW [77d40000+5846+a0]
5ad71b11: uxtheme!DrawThemeParentBackground [5ad70000+1677+49a]
5ad71b48: uxtheme!DrawThemeParentBackground [5ad70000+1677+4d1]
77f5f80c: ntdll!LdrLoadAlternateResourceModule [77f50000+f7da+32]
77d458bf: USER32!DefWindowProcW [77d40000+5846+79]
77d458b1: USER32!DefWindowProcW [77d40000+5846+6b]
77d458b1: USER32!DefWindowProcW [77d40000+5846+6b]
5ad755a1: uxtheme!CloseThemeData [5ad70000+42d7+12ca]
5ad71b71: uxtheme!DrawThemeParentBackground [5ad70000+1677+4fa]
5ad73c51: uxtheme!GetThemeColor [5ad70000+3ab8+199]
77d4a8d6: USER32!wsprintfA [77d40000+a6e3+1f3]
77d43b67: USER32!00003b67
77d43b4b: USER32!00003b4b
77d43b4b: USER32!00003b4b
77d4450d: USER32!PostMessageA [77d40000+4460+ad]
77d44518: USER32!PostMessageA [77d40000+4460+b8]
77d44518: USER32!PostMessageA [77d40000+4460+b8]
77d47b55: USER32!SetPropW [77d40000+7af5+60]
77d47b65: USER32!SetPropW [77d40000+7af5+70]
77fb4da6: ntdll!KiUserCallbackDispatcher [77f50000+64d93+13]
77d45968: USER32!DefWindowProcW [77d40000+5846+122]
77d45968: USER32!DefWindowProcW [77d40000+5846+122]
77d45937: USER32!DefWindowProcW [77d40000+5846+f1]
77c72a52: GDI32!GdiReleaseDC [77c70000+2a42+10]
77d44165: USER32!GetWindowLongW [77d40000+40aa+bb]
77d4535c: USER32!ReleaseDC [77d40000+5341+1b]
5ad77d30: uxtheme!GetThemeBackgroundRegion [5ad70000+6eda+e56]
5ad71596: uxtheme!00001596
5ad734a3: uxtheme!GetThemePartSize [5ad70000+2e2e+675]
5ad734b2: uxtheme!GetThemePartSize [5ad70000+2e2e+684]
77d4413c: USER32!GetWindowLongW [77d40000+40aa+92]
77d46070: USER32!GetSystemMetrics [77d40000+6017+59]
77d46062: USER32!GetSystemMetrics [77d40000+6017+4b]
77d46062: USER32!GetSystemMetrics [77d40000+6017+4b]
5ad73842: uxtheme!IsThemeBackgroundPartiallyTransparent [5ad70000+35aa+298]
5ad77943: uxtheme!GetThemeBackgroundRegion [5ad70000+6eda+a69]
77d45937: USER32!DefWindowProcW [77d40000+5846+f1]
-- End of report
sysKin
10th June 2004, 04:12
plugin_dump??
plugin_dump called from xvid_decore ?? but decoder does not even call any plugins...
The last time I saw a crash on a not-used plugin was on overclocked system, but that was during *en*coding and was, of course, not reproducable.
Please give us the sample as soon as you can, something very funny must be going on :)
Radek
aketon
10th June 2004, 08:17
OK, here is the avi file!
http://www.sharemation.com/aketon/for-test.avi
(I hope the link works now)
If the link don't work, please let me know!
ViCroié
10th June 2004, 11:46
Well I downloaded the file, and it played fine with my FFDshow20040520, though when i switched to XviD Decoder I got the error too :(:confused:
stephanV
10th June 2004, 12:05
yep, i got a similar result:
3ivx, DivX 5.1.1 and ffdshow/ffvfw 05/20/2004 played the file fine. only the XviD decoder (latest binary from koepi) seemed to crash on it.
aketon
10th June 2004, 13:52
At least I am happy with the fact that there is no problem with my encoded file and it is just a decoder problem! I hope that they are going to fix it soon!
BYE!!!
Caleb666
10th June 2004, 22:58
Well, looks like it crashes on almost ANY movie here with the new v1.01!
Rolled back to nic's old deocder and everything works properly now.
Some movies do load up with the new version (v1.01) but then when i try to seek they crash!
sysKin
11th June 2004, 10:34
I can't reproduce the crash :( neither with my builds nor with Koepi's build.
aketon
11th June 2004, 10:37
Originally posted by sysKin
I can't reproduce the crash :( neither with my builds nor with Koepi's build.
Strange, what player did you used?
Did you try to play the video from the beginning to the end and it didn't crash? Virtualdub doesn't show the error when it plays the problematic(!) frame, only when it stops the playback in the end of the file!
aketon
11th June 2004, 14:22
The video plays without problems with the latest Gamr build XviD-pentium4-200405270038!
demonmagnet
11th June 2004, 16:12
Originally posted by sysKin
I can't reproduce the crash :( neither with my builds nor with Koepi's build.
i saw the crash fine :P, using xvid 1.01 and media player classic 6482.
Processor : athlonxp
other specs: probably not relevant
Seems to be quite a few problems with this build http://forum.doom9.org/showthread.php?s=&threadid=77616&perpage=20&pagenumber=2, maybe it should be pulled until further testing can be done.
Just a thought, the people who have been reporting crashes have been using athlonxp's(which are missing some instructions, sse2). Syskin do u have a p4?
Koepi
11th June 2004, 16:27
demonmagnet:
i fear your conclusion to draw back the build are a bit early. It seems to me that the error is on the user's computer side, as I can't reproduce as many others can't. (Tested: celeron 1.8ghz, athlon xp 2000+, athlon xp 2800+, media player 6.4, media player classic 6.4.8.2).
Ok, going on further coding/testing the automatic screenshot stuff...
Regards
Koepi
demonmagnet
11th June 2004, 16:40
yes it was a fairly early conclusion. Its just that ive seen a few different posts reporting problems with the new build. Though problems are not uncommon they are fortunately becoming rarer with the newer builds.
In this thread 4/6 people have been able to reproduce the problem. With only you and syskin not having the problem. are u two holding out on us :P
So it seems ever more likely that the problem is not a user specific problem.
amk316
11th June 2004, 17:18
i install the "XviD-pentium4-200405270038" and it solve some problems (when i open a folder with a specific avi file the explorer resart!) but my oregnal problem is with VirtualDubMod 2439. i want to fix some file, but when i run the file it give me a "out-of-bounds memory access"!!!!
any update i should do?
regards;
dragongodz
11th June 2004, 17:32
ok tested that file with my athlon xp 2400+ using mediaplayerclassic 6.4.8.2.
with overlay set in MPC = crash half way through playing
with VRM7(windowed) in MPC = MPC closing(no error) halfway through
with force colour space to RGB24 in xvid decoder setting = plays the whole clip, error when manually closing MPC
i have only played a couple of other my old xvid files and have not seen any problems like this so there must be something about that clip specifically aswell. :)
aketon
11th June 2004, 21:48
Originally posted by Koepi
It seems to me that the error is on the user's computer side, as I can't reproduce as many others can't. (Tested: celeron 1.8ghz, athlon xp 2000+, athlon xp 2800+, media player 6.4, media player classic 6.4.8.2).
Ok, going on further coding/testing the automatic screenshot stuff...
Regards
Koepi [/B]
But if the error is on the user's computer side, then why do I've got the error only with your build? Isn't it strange that other builds don't crash? I can also play the video with VLC 0.7.2 without any problems! The only question I've got is "what is happening in the frame 22 (this is the frame where VirtualDub says that the problem is)???"
My own little test; Using Koepi's build and that file (on my little Athlon 1800xp, Win2k).
Well it plays fine in mplayer2 and in MPC. But if I turn on MPC with Windowed VRM9 then windows blue screens (but I've never used VRM9 so it may be coincidence)....Not very useful tests, and can't debug it because of the blue screen, but I thought I'd mention it :)
-Nic
sysKin
12th June 2004, 03:26
Originally posted by demonmagnet
Syskin do u have a p4? Nope, athlonxp. I just followed all your instructions about switching to different renderers, as well as trying all players I could get - still nothing.
Radek
virus
12th June 2004, 17:12
I can confirm the crash under MPC 6.4.8.2 (using Overlay, address 0167:05678a68) and VDub 1.5.10 (at the end of the bitstream).
It does not crash with ViPlay 2.08 and WMP 7. It does not crash with XviD 1.0.0, regardless of the player.
my config: P4 2.4 GHz (no overclock), GeForce4 Ti, Win98SE.
hope this helps :)
virus
niamh
12th June 2004, 18:17
Win2K pro, P4 2ghz , ATI radeon 9200 >>>>>>> I have no issue whatsoever playing the file, and no crashes. I used the latest koepi build to decode(1.0.1).
I have tried every single setting I could think of , still no crash.
Put through Vdub1.5.4.1, the file plays properly,frame by frame too, but if I go to show bad frames, i get "the following frames could not be decoded:22-126"(they are though), and if i move backwards through the frames, vdub dies on me, no error no nothing, just dies.(same behaviour with 1.5.1.0).That, only if show input video is checked(obviously). If I preview the file, 1.5.1.0 dies at the end of the preview no matter what(as virus said), 1.5.4.1 does not.
I've checked to see if that happened in the media players(wmp6.4,TCMP,BSplayer), everything is fine and goes backwards and forward with no errors. Real player chokes on it if I go backwards(it freezes for a bit, it seems it has problems seeking) but that's it, it doesn't crash.
That's all I can come up with :)
downimp
12th June 2004, 18:38
My mpc also crash here:
AppName: mplayerc.exe AppVer: 6.4.7.8 ModName: xvidcore.dll ModVer: 0.0.0.0 Offset: 0068a68
P.S. with XviD-1.0-09052004 the file played just fine. The crash appear after installing XviD-1.0.1-05062004 (without uninstaling the old xvid version).
niamh
12th June 2004, 18:52
I finally got round to reinstalling build 1.0 final, ran the file through VDM 1.5.4.1 and 1.5.10 both, and there is no bad frame detected this time, let alone any error previewing, so it looks like it's definitely a decoder issue in the latest build . :(
Soulhunter
12th June 2004, 19:22
Regarding my crash problem in this (http://forum.doom9.org/showthread.php?s=&threadid=77616&perpage=&pagenumber=2) thread...
I wrote that the crash happened while encoding !!!
Right, but I should also mention that Ive re-encoded from a XviD file... :o
So, there is the chance that the crash happens by decoding the source !!!
Bye
niamh
12th June 2004, 20:45
I've run that offending file in DivX DRF analyzer, and this is what I found:
#bla bla
FourCC: XVID
Codec: XviD0035
Resolution: [ Width: 624 Height: 336 ]
#bla bla
There are NO frame drops ( NO drops is better )
Recomended Resolution: [640x336] (Target DRF/quantizer=2.8)
Performance Caracteristics:
Macroblocks per frame: 819
The Width is not multiple of 32. May degrade performance in some systems.
Now I wonder would that be a cause of issues with the new build...I can't find another non 32X16X movie on my pc, so I encoded two tests but with 2000 frames only (takes forever otherwise), and the results were not conclusive, I don't get bad frames...Can anybody else who have several other files crashing confirm or infirm that the resolution could be involved?
@soulhunter:
-I suppose your source xvid would return some bad frames through VDM scanning, or plain die previewing the source movie(with 1.0.1 set as decoder), roughly at the place you crashed while encoding, if it's the same sort of issue? and probably show all clear with 1.0 as decoder?
-That source XviD doesn't happen to be non-32x16x resolution by any chance? :D
Soulhunter
12th June 2004, 20:53
Tested with two different sources, both have a resolution of 1024x576 !!!
I will re-install Koepis 1.0.1 build n' test if it crashes while de-coding... ;)
Bye
niamh
12th June 2004, 20:55
Damn, there goes my half baked theory ;) ah well, it was a thought :D
virus
12th June 2004, 21:01
As far as I can tell, the MPC splitter is to blame, not the XviD decoder. I've tried the rendering in graphedit and the chain:
AVI splitter -> XviD decoder -> Overlay Mixer2 -> renderer
worked perfectly. AFAIK this is the same rendering chain used by MPC with OM enabled, except for the splitter...
So I disabled Gabest's splitter in MPC and guess what? It plays perfectly. No more crashes. If I re-enable Gabest's splitter, it crashes again. IMHO the decoder is OK. Don't know what to think about VDub, but it may be a different problem.
virus
niamh
12th June 2004, 21:31
So I disabled Gabest's splitter in MPC and guess what? It plays perfectly.
I can confirm that, I just downloaded MPC to have a look , and it's as virus says :). It still doesn't explain the vdub issue though :) and why does it have bad frames showing under 1.01, and none under 1.0.
So I wouldn't say it's Gabest's splitter's fault, but rather, it's the only one that's affected by the "issue", as far as we know ;)
Soulhunter
12th June 2004, 21:47
Ok, I can confirm the sources get decoded without any problem !!!
But, encoding works now too without crashing... :scared:
Really, I cant reproduce this problem anymore !!!
Source, decoder, programs are exactly the same... :confused:
Only thing I did was un-installing Jawors build n' re-installing Koepis then !!!
Confusing, should I be happy or worry now ???
Bye
niamh
12th June 2004, 23:07
Ok, I can confirm the sources get decoded without any problem !!!
So my silly theory still stands for now :)
Really, I cant reproduce this problem anymore !!!
I've noticed that the simple fact to post something here gets it solved most of the time ;)
Soulhunter
13th June 2004, 00:01
Originally posted by niamh
I've noticed that the simple fact to post something here gets it solved most of the time ;) Hehe, a SSP (Self-Solving-Problem)... :D
But the fact that I cant reproduce this crashing worry's me !!!
Only thing I could think of, it has to do with the registry stuff...
Maybe there was something "wrong" with the v.1 final un-installation ???
Bye
niamh
13th June 2004, 00:12
Hehe, a SSP (Self-Solving-Problem)...
Notice that if you wait 3 months to post, the problem will dutifully wait 3 months to solve itself too ;)
And surely after years with Microsoft, you shouldn't worry anymore! :D maybe only a reboot was needed...I'd say that's one less to worry about for syskin and koepi :)
dragongodz
13th June 2004, 04:41
damn you guys beat me to it about the splitter.
ok heres something interesting to add then. in virtualdub if you use gamr's build and run check for vidio errors it comes up with 1. now in media player classic i turned brightness up using gamr's build and watched and you can see a corrupt frame flash indeed right at the point 1.0.1 quits/crashs. so that bad frame appears to be the problem for 1.0.1.
aketon
13th June 2004, 10:21
I've noticed something strange also in VirtualDub! If I load the video I posted with the problem and I just push play, VirtualDub plays the whole file and when it stops at the end of the file it just crash and it tells me about a problem in frame 22! But, if I first run "Scan video stream for errors..." in VirtualDub (which is telling me that everything is fine) and then play the video, then it plays fine and without problem!
P.S.: The encoded file was made with avs2avi 1.38 and it is the first time I've noticed a problem like that!!!
BYE!!!!!
niamh
13th June 2004, 16:42
I will just add that this encode is showing the same bad frames with the latest celticdruid build (13/06/2004) in VDM, and I rechecked yet again, it's still showing clean with the 1.0 build :)
CruNcher
15th June 2004, 07:01
such problems could also be caused by damaged Windows Application Acceleration Prefetch files in your prefetch folder just clear it from time to time or deativate this function :) see my bug report about avs2avi 1.38 in the dev forum what i mean *Windows is Evil*
celtic_druid
15th June 2004, 08:41
That build if I remember had fixes ported from 1.0.1, so I guess it would behave more like 1.0.1 than previous cvs head builds.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.