AviSynth script error reporting

[andmor]

Whenever there is an error in a script, AviSynth creates a 10 second clip with text indicating the line position and error type.

Is there any other form of error reporting possible such as logging to a file or other ?

Thanks
andmor

[sh0dan]

Moved to Dev (as there isn't, except the dialog box in Virtual Dub).

Why do you need that?

[Ebobtron]

avsFilmCutter (http://forum.doom9.org/showthread.php?t=97438) will provide a dialog box like VirtualDub when configured to display the data seen at the top left of the following image, the dialog box shows before the view below is updated. Version 1.4 shown, little has changed in the script preview mode of use.

http://members.aol.com/avsfilmcutter/ss_03.jpg

This version though the last alpha are not always very source smart. The next version, 1.8b due soon, will be better at providing error data across the board. Ver 1.8b will not require an attemped preview to get error data. F8 will suggest an error based on its script output propreties currently but that method of output properties has no ability to get internal error data.

@andmor
Sorry one error at a time (there can be only one). Even if it could gen a list, it would be a list of one. I am often wrong, is there a next error thing I missed? At least with avsFilmCutter (http://forum.doom9.org/showthread.php?t=97438) I am trying to make the error correction part of script writing a little easier.


:)

[IanB]

I sympathize. I toyed with an implementation a while back, but the VFW AVI interface leaves little room to report errors. Basiclly you get to return EFAIL. Which is far from useful. And popping an error dialog from inside Avisynth is a definite no-no. The least awful solution I could think of at the time was an OutputDebugString() analogue or a fixed logfile (how to spec the path).

[Ebobtron]

I sympathize. ..... analogue or a fixed logfile (how to spec the path).

ini type file in the running scripts's folder could be filled will all matter of flags and switches to control anything. or a script like function. seems like a lot of work, multiple error parsing, yuk

:)

[IanB]

ini type file in the running scripts's folderShudder! :eek: Even worse than having rogue .avsi's in your plugin folder.

[andmor]

Sh0dan asked "Why do you need that?"

I need this because I'm passing an auto-generated .avs file on to a transcoder (in this case Digital Rapids StreamZ).
If there is an error in the script, I'd like to know before passing it on. From the transcoders view, it just sees an oddly shaped 10 second video clip. Error logging to a file or some other reporting would avoid this.

[stickboy]

Whenever there is an error in a script, AviSynth creates a 10 second clip with text indicating the line position and error type.

Is there any other form of error reporting possible such as logging to a file or other ?Not quite. Some errors are reported in the clip itself (typically those errors are from some failure within the filters themselves). Script errors are usually reported via an error dialog (although I think that's dependent on whether the scripting host supports it).

If you open the same script in VirtualDub, do you get an error dialog or a clip with the error message?