PDA

View Full Version : Avisynth caught access violation


Piff99
2nd January 2002, 17:20
Hi,

maybe my problem already is posted somewhere else, but I'm not able to search the forum.

I'm converting divx to svcd using avisynth and cce(2.50). most of the time everything worked fine, but now avisynth is not frameserving but showing an error message like "Avisynth caught an access violation at ..." in the converted file.

I believe there's something wrong, but I don't know where to start searching.
Playing the avs-files in media player works fine.

Has anyone an idea ?

Thanks Piff

kdiddy
2nd January 2002, 21:23
Are using Blur or Sharpen command?

Piff99
2nd January 2002, 22:16
No.

Here is my avs File:

LoadPlugin("I:\DVD\MPEG2DEC.dll")
AviSource("F:\dummy.avi")
BicubicResize(464,409,0,0.6,0,0,640,352)
#TemporalSmoother(3,5)
AddBorders(8,83,8,84)
#Trim(0,146325).FadeOut(150)
ResampleAudio(48000)

Except 'ResampleAudio...' it is generated by FitCD.

It may be interesting that I am using WinXP Prof on an AMD Athlon system.

Thanks,
Piff

kdiddy
3rd January 2002, 06:39
O well I have no clue, I get this error with the Blur/Sharpen command.

Krajensky
13th January 2002, 05:31
Remove those commands one by one until you find the one that causes the violation. My guess (not based on your software configuration) is that the resize is causing it, and a ConvertToRgb before the resize would probably fix it...of course that'll take the quality down a little because it's doing a colorspace conversion, and you will lose quite a bit of speed (up to 15%).

Krajensky

daxab
18th January 2002, 05:58
I've seen access violations in Crop(). In fact, I had one case where when with a horizontal size of 480 it was fine, but 240 caused an access violation.

Roginator
18th January 2002, 07:33
I had that error when I used the latest IVTC plugin. I can only assume it was because I had a signal drop in my capture. When I switched to GreedyHMA to do the inverse telecining, the problem went away.

Normally I have no problem with IVTC.

raven
26th January 2002, 23:35
I ripped (for some reason) only a few chapter with smartripper and in one of those chapters, I got the same avisynth-message, when working with dvd2svcd vs.1.06.
I ripped the part of the DVD which includes the chapter with the internal routine of dvd2svcd an everything works fine.
Maybe this is one clue to solve the problem.

Piranha
19th March 2002, 06:22
On Road Trip, the avs violation doesn't occur, but, when i load it up with Heat, the violation occurs... Got any ideas?

Piranha
20th March 2002, 00:24
And this is the script file i'm using:

LoadPlugIn("F:\decomb.dll")
LoadPlugin("F:\MPEG2DEC.DLL")
mpeg2source("Heat.d2v")
Telecide
Decimate(5)
temporalsmoother(1,2)
crop(0,60,720,360)
bicubicresize(480,288,0,0.5)
addborders(0,96,0,96)
ResampleAudio(44100)

bb
21st March 2002, 07:26
Well, the first time I encountered this error was yesterday when I tried to convert a (probably broken?) MPEG2 stream.

The stream was captured from a DVB source. I used DVD2AVI to get a project file, then GordianKnot to generate the AVS file with all the cropping & resizing stuff.

bb

Boulder
25th March 2002, 10:49
I've had those error messages when converting captured AVIs. DVD2SVCD has worked fine without a single crash (knocking on wood;) ). Usually it happens in the last pass, and there is nothing more irritating than wasting 8 hours on the first three passes + vaf creation, waking up in the morning and noticing that the notorious access violation had struck an hour ago.

freddycat
26th March 2002, 08:01
I am also having the same avisynth error. For me it occurs at random places. The strange thing is that I ran the first pass once without the error and it showed up on the second pass. When I tried to encode again from scratch it occured during the first pass at different places each time. So it seems to be somewhat random. There was another post entitled "Access Violation" that talked about this and neuron2 said it was due to a temporalsmoother thing in that case, but I'm not using a temporalsmoother in my script (I don't think I am but I am pretty new to all this). I tried running it with different settings. The last run I ran I tried not to use as many settings. The last time I got the error my script was (the script is the "".avs file with the lines without the # symbol in front of it right? Did I mention I am new to all this? :D ):

LoadPlugin("C:\PROGRA~1\GORDIA~1\mpeg2dec.dll")
mpeg2source("C:Test\test.d2v")
crop(0,0,720,480)
BicubicResize(656,480,0.333,0.333)


I don't know what's going on. From the different posts I've read there doesn't seem to be a definitive explanation for the error. I'm getting frustrated. :(

trbarry
26th March 2002, 22:41
There seem to be at least 3 sources of errors like this.

1) There is a missing emms assembler instruction in the current version of (I think) BicubicResize. You can switch to SimpleResize or BilinearResize, or download a new version of Avisynth mentioned in another of these Access Violation threads.

2) If you have garbage data like occurs in my HDTV captures, and probably in DVB cards, then it can cause an access violation in DVD2AVI or mpeg2dec.dll in the motion compensatino routines. I'm testing an ugly temporary fix for this by just doubling the internal buffer sizes so the data access doesn't fall off the end of them.

3) Unforetunately, the mpeg2dec.dll source I'm working on also has errors with random seeking in the file such as would be used by an IVTC type routine. This can cause other possibly similar errors, but maybe not access violations. I don't know what the fix is for this yet and I don't know which versions of mpeg2dec.dll probably have the problem. But it is also responsible for very jerky playback, as if there were missing frames.

- Tom

bb
27th March 2002, 08:47
As far as my investigations go, I could eliminate the problems with the DVB source using PVAStrumento. This software corrects the MPEG2 transport stream.

@trbarry:
When I move the slider in VDub when using AviSynth frameserving through mpeg2dec.dll the program hangs. It's ok for some frames, but when I move further like a few hundred frames, then it gets stuck. I can only kill VDub then.
Do you think this has to do with the problem you mentioned under 3) ?

bb

trbarry
27th March 2002, 13:53
bb -

It's more likely the one in #2 but it could be either.

The problem in #3 will cause the vdub display to be much more jerky or even get 'stuck' motion in vdub if you move the slider very slowly.

PM me and I'll send you a test version of mpeg2dec.dll that has #2 fixed but #3 still a problem, so we'll know. Hopefully I can fix #3 today also but it's in code I don't understand yet, so who knows?

- Tom