View Full Version : Avisynth 2.04 crashes
Boulder
10th August 2002, 11:03
I captured the Terry Gilliam movie 'Brazil' yesterday (an analog TV capture) using PicVideo MJPEG codec at the quality setting 19, chroma and luma quality set to 3. I created a standard Avisynth script - I have a default script which I just edit according to the bitrate used in encoding etc. - but Avisynth 2.04 won't work correctly. It crashes after a while, in this case it goes crazy after about 4000 frames have been encoded. I use CCE2.50 for the encoding, but I noticed the same crash using the latest VirtualDub, seeking through the movie for commercials. Avisynth version 1.0beta6 didn't crash.
I used BilinearResize for resizing and Tom's GreedyHMA plugin for deinterlacing. I've had some crashes before but this one happened almost at the same spot every time I tried it. I've tried it with Windows XP Pro and 98SE with similar results. I'll post the script if needed, unfortunately I don't have it on the computer I'm using right now.
Anybody else had similar problems?
Richard Berg
10th August 2002, 12:30
Please comment out one line at a time in turn until it works, then let us know which one was the culprit.
Blight
10th August 2002, 14:48
Trying to do Realtime playback (using zoom player), I got this error:
"AVISource : failed to decompress frame 115 (error -377)
Source is 768x576@25fps MJPEG with 44.1khz 16bit stereo PCM audio,
script is:
LoadPlugin("GreedyHMA.dll")
SegmentedAVISource("cap_14.avi")
ConvertToYUY2()
GreedyHMA(0,0,4,0,0,0,0,0)
This isn't consistant, error doesn't always show up...
BTW, I thought Greedy was supposed to be real-time, I was getting under 1fps screen updates on a p3/733.
Richard Berg
10th August 2002, 15:06
Greedy is very fast, but Avisynth as a whole doesn't play nicely with realtime readers -- the tricks they play to skip ahead when behind are ok when the lag is due to your filesystem/network/CPU, but will only confuse and overwork a true frameserver like Avisynth. OTOH, I'll bet you'd get nearly realtime "playback" just by loading it in VDub and holding the right arrow key, for instance.
Methinks the new AviSource code still has some issues.
wing1
10th August 2002, 15:37
I have experienced something like @boulder here as well. However, my sources are captured using Mpeg4VKI and Xvid codec. I have no problem with 2.04 with capture clips from Xvid codec but it always crashed with the Mpeg4VKI and B-frame, and it is precisely about 4.5 minutes into the encoding. This is what i've done to see what is the cause so far...
1. vdub1.4.10- compress with latest xvid (my own compilation)B-frame on - input is captured clip with xvid codec = no problem
2. vdub1.4.10- compress with latest xvid (my own compilation)B-frame on - input is captured clip with Mpeg4VKI codec = crashed precisely 4.5 minutes into encoding.
3. vdub1.4.10- compress with latest xvid no B-frame - input both xvid and Mpeg4VKI codecs = no problem
Here is the log of the crash:
031084d2: 0f6f12 movq mm2, [edx]
031084d5: 0f6f5a08 movq mm3, [edx+08]
031084d9: 0fe013 pavgb mm2, [ebx] <-- FAULT
031084dc: 01ca add edx, ecx
031084de: 0fe05b08 pavgb mm3, [ebx+08]
----------------------------------------------
EAX = 0418ab50
EBX = 045ff1e0
ECX = 000002c0
EDX = 040ab810
EBP = 00000007
DS:ESI = 0023:03a3979c
ES:EDI = 0023:0414c1e0
SS:ESP = 0023:051af0d0
CS:EIP = 001b:031084d9
FS = 003b
GS = 0000
EFLAGS = 00010206
MM0 = 4b4b4a4a47434141
MM1 = 5151515252504d4c
MM2 = 6866646363626162
MM3 = 6c6d6c6b696a6a6a
MM4 = 0000000000000000
MM5 = 000000000000097c
MM6 = 0000000000000a5f
MM7 = 0101010101010101
Crash reason: Access Violation
---------------------------------------
T:\projects\VirtualDub_old\main\Dub.cpp(2835)
T:\projects\VirtualDub_old\main\Dub.cpp(2840)
T:\projects\VirtualDub_old\main\VideoSequenceCompressor.cpp(358)
Thread 000003f0 (I/O processing)
---------------------------------------
00468316: Dubber::ProcessingThreadKickstart()
004800e8: _threadstart@4()
77e92ca8: KERNEL32!CreateFileA [77e80000+12b8d+11b]
77e9c008: KERNEL32!GetTempPathA [77e80000+1bf24+e4]
trbarry
10th August 2002, 15:42
Greedy/HM is real time in DScaler but that is with the data being DMA'd into memory by hardware and exiting via the AGP bus. That doesn't at all guarantee that Avisynth will be real time when you add compression/decompression and a bunch of copies of the buffers.
- Tom
edit: But that seems WAY too slow for your machine
J_p
10th August 2002, 17:42
I get error code from AVISource too. It comes from same frame every time with same source but with different source file the error code comes from different frame.
Error code when VirtualDubs frame count is something like 3x xxx frames
AVISource: failed to decopress frame 20613 (error -367)
Found out this error after moving to version 2.04.
Just finished encoding using 2.03.... no problems at all.
WarpEnterprises
10th August 2002, 21:20
As the error occurs somewhere in the middle and there are changes in audio-treatment couldn't it be audio-related?
(try without audio)
Boulder
11th August 2002, 10:02
Here's the script I used:
LoadPlugin("c:\windows\system\greedyhma.dll")
UnAlignedSplice(SegmentedAVISource("c:\temp\captures\brazil.avi"), SegmentedAVISource("d:\temp\captures\brazil.avi"))
Trim(385,48954)+Trim(52087,85004)+Trim(89160,123756)+Trim(127087,172879)+Trim(176788,216000)
FadeOut(200)
GreedyHMA(0,0,0,0,1,0,0,0)
BilinearResize(480,574)
AddBorders(0,1,0,1)
ResampleAudio(44100)
I can't find a specific filter which won't work, but it _might_ be Greedy as it's the only one I use on every encode, or it might be something in the PicVideo codec that Avisynth doesn't really like. I tried Avisynth v2.03 and it seems to work OK.
sh0dan
11th August 2002, 14:39
Could be related to the compressed audio problem.
dividee mentioned it in this thread (http://forum.doom9.org/showthread.php?s=&threadid=30484)
Try disabling sound using avisource("file",false) - to see if that helps.
Boulder
11th August 2002, 15:54
Thanks, I'll try it out. I'll let you know what happened later.
sh0dan
11th August 2002, 17:55
Originally posted by wing1
2. vdub1.4.10- compress with latest xvid (my own compilation)B-frame on - input is captured clip with Mpeg4VKI codec = crashed precisely 4.5 minutes into encoding.
@wing: The crash does not seem to directly linked to AVS (the code in the dump is not part of Avisynth, as far as I can tell, rather a part of the filter you use to compress the video), but could be related. A possibility is that AVS somehow gives an invalid frame reference (ebx) - could you post the same crash, but using BicubicResize(32,32) in the AVS file?
Are you using full processing or fast recompress?
Could you please post the avs-file?
tuco
11th August 2002, 20:16
Using this .avs file and Xvid 7/12/2002 (Koepi's) I get a crash 17 mins. into a 43 min video.
LoadPlugin("c:\avisynth\decomb.dll")
LoadPlugin("c:\avisynth\MPEG2DEC.dll")
LoadPlugin("c:\avisynth\temporalsoften2.dll")
clip = AVISource("farscape.avi")
det = BlendFields(clip)
rez = BicubicResize(det,480,360)
#soft = TemporalSoften2(rez,3,5,7)
soft = TemporalSmoother (rez,2,1)
ret = soft
return ret
note that it crashed both with compress audio and without audio and it crashes at the same point. I didn't have this problem with an older version of avisynth.
dividee
11th August 2002, 20:53
Could anyone that gets this crash in 2.04 and not in 2.03 cut the smallest possible AVI sequence that exhibit the problem (along with your script), and either post it or put on some webspace or mail it to me (dividee_AT_skynetDOTbe) ? Does the problem also appears if you preview the script till the crashing position in VirtualDub, or only when compressing ?
wing1
12th August 2002, 06:05
@Sh0dan
You are absolutely correct. It is not 2.04 that is causing the crash.
Import("c:\itvc\plugins.avs")
vin=OpenDMLSource("D:\sample1.avi").convertToYuY2()
v1=vin.tweak(bright=21,cont=0.98,sat=1.18)
v2=v1.Cnr2(mode=-1,ln=25).MergeLuma(v1.TemporalSmoother(4,1).unfilter(0,60))
m=v2.BicubicResize(640,192,-0.5,0.75,0,26,v2.width,v2.height-52).TomsMoComp(1,-1,1)
return m
This is the script that I used with the MPG4VKI clip, and it crashed during fast compression. Take out TomsMoComp(1,-1,1) from the script will solved the crash problem. This is not good :( because I like TomsMoComp.dll alot. It has to be my bad compilation of the xvid.dll with B-frame enable. Oh well no B-frame I guess.
Boulder
12th August 2002, 08:52
I tried disabling the sound, but it seems to work only on AviSource, not on SegmentedAVISource although adding 'false' to SAS won't give any error messages whatsoever.
I sure hope this is only a minor incompatibility between some filter (probably GreedyHMA) and AviSynth 2.04 as I'd very much like to use both of them.
trbarry
12th August 2002, 13:20
What kind of processor is everybody using that gets these crashes?
And do they also occur on Avisynth releases prior to 2.00?
There are still too many pieces in the puzzle. :(
- Tom
wing1
12th August 2002, 16:05
@trbarry
I have AMD XP chip on my PC. It happened to me even if i went back to 1.07d.
TomsMoComp + Mpeg4VKI(input)-> xvid+Bframe = crash
TomsMoComp + Mpeg4VKI(input)-> xvid+NOBframe = good
TomsMoComp + xvid(input)-> xvid+Bframe = good
Mpeg4VKI(input)-> xvid+Bframe = good
My choice is simple enough...No Bframe with Mpeg4VKI(input). Besides Bframe is still under development with xvid at the moment so the crash may not be due to TomsMoComp. The reason I like to use B-frame in xvid is that the file size saving I can get with it: I get ~10%-20% file size reduction with heavy tweaking and still retain good visual quality.
sh0dan
12th August 2002, 16:10
@All: As trbarry and dividee points out, we have to be able to reproduce the error. So if you got a really short clip, post a link or mail it to one of us. We need to know:
-Exact script
-Version numbers (avs, vdub, filters, compression/decompression codecs)
-Vdub settings (what's modified from startup settings)
-System config. (CPU / OS)
trbarry
12th August 2002, 16:41
My choice is simple enough...No Bframe with Mpeg4VKI(input). Besides Bframe is still under development with xvid at the moment so the crash may not be due to TomsMoComp. The reason I like to use B-frame in xvid is that the file size saving I can get with it: I get ~10%-20% file size reduction with heavy tweaking and still retain good visual quality.
Off hand there are a few things I can think of that cause funny complex interactions between filters and codec.
1) The no-EMMS problem, supposedly no longer an issue.
2) Using too much memory to have enough buffers.
3) My most likely candidate right now, the fact that TomsMoComp, GreedyHMA, and other IVTC filters ask for random access to the clips. Greedy may look at 6 frames at a time and TomsMoComp will usually also look at the previous frame, though that (IIRC) is not true for negative SearchEffort values. Maybe B-frames affects this somehow?
But GreedyHMA and TomsMoComp don't otherwise share much of a code base so I'm not sure where a common problem would come in.
- Tom
tuco
12th August 2002, 17:02
Originally posted by tuco
Using this .avs file and Xvid 7/12/2002 (Koepi's) I get a crash 17 mins. into a 43 min video.
LoadPlugin("c:\avisynth\decomb.dll")
LoadPlugin("c:\avisynth\MPEG2DEC.dll")
LoadPlugin("c:\avisynth\temporalsoften2.dll")
clip = AVISource("farscape.avi")
det = BlendFields(clip)
rez = BicubicResize(det,480,360)
#soft = TemporalSoften2(rez,3,5,7)
soft = TemporalSmoother (rez,2,1)
ret = soft
return ret
note that it crashed both with compress audio and without audio and it crashes at the same point. I didn't have this problem with an older version of avisynth.
Oh ya, I was using 2.01 and had no problems which I reinstalled and confirmed that it wasn't necessarily my source. I will get that error around the same point in multiple clips. It only happened when I was encoding. It never crashed when I was in vdub editing out commericals. It could be that temporalsmoother is broken since I am guessing that blendfields and bicubicresize haven't been touch for a long while.
J_p
12th August 2002, 19:26
AVISynth: 2.04
OS: Win2k
CPU: Athlon XP
ERROR:
AVISource: failed to decopress frame 20613 (error -367)
I was using script in VirtualDub.
VIDEO: Fast compress
AUDIO: No audio
COMP: XVID(Koepis build 8.8.2002)
Error appeared when VirtualDub was prosessing frame number 30 000 or something like that.
In any case it was way beoynd that frame 20613. I tried to encode 3 times and got
this same error from frame 20613 every time.
In VirtualDub I could preview frame 20613 with no errors
(maybe I should have previewed that 30000 something frame where AVIsynth crashed?)
Also If I cut movie in VirtualDub and encoded frames 20000-21000 I had no errors.
Changed back to 2.03... No problems. Encoding ended
succesfully.
I don't have same source anymore but maybe I can test 2.04 again with different source
tomorrow while in work.
My script was:
SegmentedAVISource("i:\Cube.avi")
Crop(4,3,632,566)
BicubicResize(480,368,0,0.5)
Cnr2().STMedianFilter(10,50,8,10,10,50)
Boulder
13th August 2002, 07:53
I have an Athlon XP chip as well. The problem has occurred a couple of times with 1.0beta6 but rather seldom. It mostly happens with beta6 and Windows XP, Windows 98SE is quite stable.
I don't know if this has anything to do with the crashes, but on Win XP the encoding is somewhat faster than on 98. Maybe something about that random access here?
sh0dan
14th August 2002, 09:08
Originally posted by J_p
[B]
ERROR:
AVISource: failed to decopress frame 20613 (error -367)
EDIT: Try grabbing the latest CVS binary from the cvs-snapshot place (http://cultact-server.novi.dk/kpo/avisynth/avs_cvs.html). And test if dividee resolved your problem.
WarpEnterprises
14th August 2002, 13:31
Are there any registry/PATH/ or alike settings that AviSynth modifies?
I ask because there was a strange behaviour in trying to load e.g. ImageSequence.dll:
First it wouldn't load.
After copying the DLL to SYSTEM, SYSTEM32, WINDOWS, ... at some point it worked. Then I removed all copies but that in the expected path (my plugin dir) and it continued to load.
First I thought I made some typos but my friend reported the same...
dividee
14th August 2002, 15:14
There are no such settings.
But ImageSequence.dll is special, in that it needs imglib.dll. Maybe that dll should be in the system directory ?
WarpEnterprises
14th August 2002, 16:28
Another "crash" question:
On my celeron850/Win98 the 2.04 crashes the application and the OS after EXITING the calling app
(i.e. opening script in VD, playing/saving, closing VD --> crash of VD and kernel.dll)
It occurs with BicubicResize(352, 288, 0, 0.5).
Have you some clues why?
(Testing is quite slow because it can only be reproduced when I reboot. v1.06 doesn't crash, didn't test v2.02)
sh0dan
14th August 2002, 17:47
@WE: Some memory access failures only show up, when the memory is deallocated (that means unloading the DLL). Do you have ANY other information?
Is the crash consistent?
Does it happend on other machines (could just be win98 acting up, kernel32.dll suggests that)?
Does it also happend, if you 1) Load the avs. 2) Plays/saves 3) Load an AVI. (Loading the AVI should also unload avisynth.dll, similar to closing down VD, IIRC).
hakko504
14th August 2002, 17:51
Originally posted by WarpEnterprises
Another "crash" question:
On my celeron850/Win98 the 2.04 crashes the application and the OS after EXITING the calling app
(i.e. opening script in VD, playing/saving, closing VD --> crash of VD and kernel.dll)
It occurs with BicubicResize(352, 288, 0, 0.5).
Have you some clues why?
I get the same problem, but only with certain clips. I had 2 captured files where I used the same .avs but only one file crashed! Only thing that differs is the trim command i used:
LoadPlugin(greedyhma.dll)
SegmentedAVISource(LD.avi) #Path differs between clips
ConvertToYUY2() #Needed for my MatroxMJPEG captures
GreedyHMA(1,0,0,0,0,0,0,0)
BicubicResize(352,288,0,0.5) #Tried VerticalReduce() without success
#Also tried BicubicResize(448,336,0,0.5)
trim(1870,135355) #With the other clip I used (2198,133896)
Source files where ~90min long captures in MatroxMJPEG. They were captured with the sync version of VirtualDub. I used 352x576x25fps for videocapture format and audio was 44.1kHz 16-bit mono. I also tried adding KillAudio to the script but to no avail.
hakko504
14th August 2002, 17:57
@sh0dan
Didn't see your response until I finished typing:
Is the crash consistent?Yes, with a given clip it is fully reproducable.Does it happend on other machines (could just be win98 acting up, kernel32.dll suggests that)?win98se is a very possible source for problems, I use it beacause I can't get w2k to work properly, at least not in a dual boot environment.Does it also happend, if you 1) Load the avs. 2) Plays/saves 3) Load an AVI. (Loading the AVI should also unload avisynth.dll, similar to closing down VD, IIRC).Not until VD is closed.
The exact error message is:
VIRTUALDUB orsakade ett ogiltigt sidfel i
modul KERNEL32.DLL på adress 01a7:bff9db61.
Registrerar:
EAX=c00309c4 CS=01a7 EIP=bff9db61 EFLGS=00010216
EBX=0072fe28 SS=01af ESP=0062ff24 EBP=006301c0
ECX=00000000 DS=01af ESI=00000000 FS=4c5f
EDX=bff76855 ES=01af EDI=bff79198 GS=0000
Byte på CS:EIP:
53 8b 15 e4 9c fc bf 56 89 4d e4 57 89 4d dc 89
Stackdump:
It means something like: illegal page in kernel32.dll at address 01a7:bff9db61. Then it lists the registers and then the actual contents of the faulty page (I think)
Boulder
14th August 2002, 20:36
I noticed that I get the "failed to decompress frame" crash if I move the seek bar in VirtualDub to the end of the AVS frameserved file. Sometimes it occurs immediately, sometimes it crashes after the bar has been moved a couple of times back and forth. I tried it on a 20-second capture, however encoding it went fine. Avisynth seems to add an empty frame to the end of the frameserved file as all the other frames are marked [K] except the last one. Is this done on purpose?
WarpEnterprises
14th August 2002, 21:17
my crash clip too was Matrox MJPEG, all the same as hakko.
What else shall I test to track down the bug?
sh0dan
15th August 2002, 08:55
Have you tried the 14th August CVS binary I mentioned above?
If not, try it, and add SetMemoryMax(64) to your script, and see how it works.
Does it also happend, if you use PicVideo or Morgan MJPEG for decompressing?
@hakko: I'm from .dk, so fortunately I understand the crash-message :)
J_p
15th August 2002, 15:10
So far no crashes for me with 2.04+ :)
Though, I've only encoded couple of 1h picvideo clips to XVID.
WarpEnterprises
15th August 2002, 22:06
1.It really seems to come from the matrox codec.
Using huffyuv works well, but how could I tell Avisynth to open a matrox file with another codec?
2.And it crashes with SetMemMax(64), v2.04+ and BilinearResize and BicubicResize, but NOT with ReduceBy2 !!
hakko504
15th August 2002, 22:22
1.It really seems to come from the matrox codec.
Using huffyuv works well, but how could I tell Avisynth to open a matrox file with another codec?
I wondered about that too :confused:
2.And it crashes with SetMemMax(64), v2.04+ and BilinearResize and BicubicResize, but NOT with ReduceBy2 !!Same thing here, crashes with bilinear and bicubic, haven't tried reduce. And right now I need to free some space so I have reverted to 2.02 which works OK (before new audio handling, BTW didn't someone (dividee?) say in another thread that there were a slight difference between audiohandling in AVISource and SegmentedAVIsource?)
EDIT: Tried to find the thread about audio-handling, but I can't find it right now, I'm too tired at the moment.
Just one more comment: Reduce has been changed also in 2.04 compared to 2.02, that could be why it works!?!
Sygma21
17th August 2002, 07:49
I got a crash with 2.04+ :
Error : Access Violation during Xvid 2nd pass frame 94343
Script
LoadPlugin("C:\PROGRA~1\GORDIA~1\mpeg2dec2.dll")
LoadPlugin("C:\PROGRA~1\GORDIA~1\temporalsoften2.dll")
LoadPlugin("C:\PROGRA~1\GORDIA~1\cnr2.dll")
SetMemoryMax(40)
source=mpeg2source("F:\Movie6\vts_01.d2v").crop(10,10,702,552)
luma=source.TemporalSoften2(3,2,0)
chroma=luma.Cnr2().MergeLuma(luma)
movie=chroma.Trim(0,132246).BicubicResize(592,320,0,0.5)
credits=source.Trim(132247,0).TemporalSoften2(2,50,0).BilinearResize(592,320)
return movie+credits
DebugViewLog (10 last entries)
00095386 14193.91640809 [4312] 2nd-pass: quant:3 MPEG inter stats1:3207 scaled:2539 actual:2100 overflow:-6228 movie
00095387 14194.06630508 [4312] 2nd-pass: quant:3 MPEG inter stats1:3516 scaled:2741 actual:2302 overflow:-5956 movie
00095388 14194.19760947 [4312] 2nd-pass: quant:3 MPEG inter stats1:3587 scaled:2787 actual:2446 overflow:-5782 movie
00095389 14194.35746079 [4312] 2nd-pass: quant:3 MPEG inter stats1:3897 scaled:2987 actual:2646 overflow:-5608 movie
00095390 14194.50655796 [4312] 2nd-pass: quant:4 H.263 inter stats1:4191 scaled:3174 actual:1570 overflow:-4171 movie
00095391 14194.65791267 [4312] 2nd-pass: quant:3 MPEG inter stats1:3774 scaled:2908 actual:3136 overflow:-4566 movie
00095392 14194.80819071 [4312] 2nd-pass: quant:3 MPEG inter stats1:3694 scaled:2856 actual:2572 overflow:-4449 movie
00095393 14194.93952807 [4312] 2nd-pass: quant:3 MPEG inter stats1:4023 scaled:3067 actual:2680 overflow:-4229 movie
00095394 14195.08875234 [4312] 2nd-pass: quant:3 MPEG inter stats1:3956 scaled:3025 actual:2786 overflow:-4157 movie
00095395 14195.25858147 [4312] 2nd-pass: quant:3 MPEG inter stats1:3926 scaled:3005 actual:2719 overflow:-4038 movie
System : W2KSP3 - PIII 933 - 512 SDR133
Xvid 07272002 Setting : 2nd pass int (628381KB)
SP : 6
QT : Modulated
FourCC : Xvid
Max I : 300
Min I : 10
Luma : disabled
Min/Max IQ : 1/7
Min/Max PQ : 1/31
Hinted ME : enabled
AltCC : enable Medium/Hi 250/Lo 90
Overflow 12000/60/60
Credits : enabled
Hope that could help you.
vinetu
17th August 2002, 13:10
@WarpEnterprises:
"...but how could I tell Avisynth to open a matrox file with another codec?..."
PicVideo MJPG,Morgan Multimedia MJPG(in my case "invert field order" should be checked for both encoder and decoder),LEADTOOLS MJPEG(tested version 1003),
MainConcept MJPEG(not sure).
WARNING -= If you install some of this codecs, your Matrox hardware will stop work properly. =-
( HOWEVER, I never seen Matrox HARDWARE AND/OR SOFTWARE(drivers-codecs) that work properly ).
My way is to install PicVideo codec(for exaple) in another windows,then copy the Pvmjpg20.dll(in case of PicVideo ver.210022)
to "%system folder%" of the Matrox infected Windows instalation,then run "regedit" -> find "Drivers32" and replace
the string value DATA(NOT NAME) "vidc.mjpg" with the "Pvmjpg20.dll"
EXAMPLE:
before - "vidc.mjpg = DigiVcap.dll"
after - "vidc.mjpg = Pvmjpg20.dll"
... then enjoy "Matrox disinfected Windows"...
... then (when you finish) you must revert old value to get all work as before ...
in case of windows98 you must do the same in both the registry and system.ini file(section [Drivers32] )
in case of Rainbow Runner I guess the string value name is "vidc.dmb1"
cheers!
vinetu
17th August 2002, 15:05
unfortunately I'm no longer one of the Proud owners of ""failed to decopress frame xxx (error -367)"" message (not today :)):
I have received this mesage 3-4 times about week ago ( same avi ,same scripts ,same avisynth version )
the avi file is captured from DV Camera through IEEE 1394 port, 1h 30min(20,520,333,756 bytes).(MainConcept DV codec used as VFW decoder)
Playing the avs with WMP ...
.................................
LoadPlugin(d:\progs\avisynth\decomb.dll)
AviSourse(e:\video\test.avi)
FieldDeinterlace()
..................................
today no error
next in VirtualDub direct stream copy:
..................................
LoadPlugin("d:\progs\avisynth\SimpleResize.dll")
LoadPlugin("d:\progs\avisynth\decomb.dll")
AviSourse("e:\video\test.avi")
FieldDeinterlace()
SimpleResize(32,32) -- for space limit and speed
..................................
no error ...
competitor:avisynth.dll v.2.04(August 07, 2002, 12:26:24 PM)
vinetu
hakko504
19th August 2002, 07:38
I was browsing AVIsynth2@Sourceforge (http://www.sourceforge.net/projects/avisynth2) and saw that Dividee had made a fix for bug 595725 (http://sourceforge.net/tracker/index.php?func=detail&aid=595725&group_id=57023&atid=482673) submitted by WarpEnterprises and it looks like it can be the source of our problems: sh0dan, could you please compile a new snapshot today so I can try it tonight?
sh0dan
19th August 2002, 08:16
New binary uploaded! Test away!
I was getting "AviSource: Failed to decompress frame XXXX (error: -100)" this weekend, when trying to stream a Divx3 with mp3-compresseed sound through AviSynth and out through zoomplayer. The strange thing was that it happened at random places (sometimes after 4000 frames, other times after 6000 frames). I'll investigate further.
(dividee - that FilteredResizeH bugfix rocks!!!)
dividee
19th August 2002, 08:20
@All
Note that the fix mentioned by Hakko caused memory access violations, this is not related to the "error -367". That one should have been fixed in the previous snapshot binary mentionned by sh0dan above.
Does someone still get "error -367" with that binary?
WarpEnterprises
19th August 2002, 08:49
I can (very very gladly ) :) :) )confirm the bugfix made by dividee.
Now + and ++ behaves as it should.
I'm going to check the MJPG/compress thing at night.
sh0dan
19th August 2002, 09:08
Hmmm.. can't reproduce the "-100 error" on my work machine. Either the bug is fixed (from last thursdays binary) , or it could be a Win98 thing (using win98 at home and XP at work).
WarpEnterprises
19th August 2002, 20:49
Now I have tried on a Win98. Here are the results
:) function is ok (that is ++ and + and DelayAudio do its work as intended)
:( now there too is a similar crash as the crash with "BilinearReszize/Matrox MJPG"
Those crashes occur either when exiting VD or when closing the (AVS)-video in VD.
I attach a VD crash info, maybe you can figure something out of it.
hakko504
20th August 2002, 07:17
I still have a similar crash as Warp, VD crashes on exit. If I go back to AVIsynth 2.02 everything works OK but newer versions just won't work properly with segmented AVI's. I think the problems started with the new audio handling but I haven't tried this clip I'm currently having problems with in A2.03, which I didn't have the new audio. I'll check that tonight.
ookzDVD
21st August 2002, 04:48
@Hakko504,
I just download the 2.02 and just install it,
but when I try the simple .avs which contain only version()
the result is 2.01, is that right ? :(
Thank you.
hakko504
21st August 2002, 07:06
Originally posted by ookzDVD
I just download the 2.02 and just install it,
but when I try the simple .avs which contain only version()
the result is 2.01, is that right ? :(
Unfortunately, yes, that's right. The person who did the release package forgot to update the version info. :eek: :rolleyes:
WarpEnterprises
21st August 2002, 07:07
Version() doesn't always show up correctly. Look at the date of the DLL for sure.
@Hakko: what processor is on your win98-system? Only to be sure it's not processor-related (altough fairly possible)
[edit] as I see in your reply only one similar thing. Mine is a Celeron850, Matrox Marvel G200
Could it be the Gx00 ??
hakko504
21st August 2002, 07:14
Full specs: Athlon 1100, 512MB RAM, ASUS A7V MB, 30GB+45GB(IBM)+2x80GB(Seagate) HD, Soundblaster Live5.1, 3com Ethernet (cable-modem), 8x CD (IDE, brand unknown), 16x6x4x CDRW (Yamaha,SCSI), 10x21x DVD(Pioneer 303S,SCSI), SCSI card unknown, 17" Samsung Trinitron, Matrox G400 Marvel-TV.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.