AviSynth 2.5.6 RC 2 Release Candidate [October 7th]

[Wilbert]

I'm sure IanB will look at these issues (cache problems). But Boulder, could you empty plugin folder and try again.

[GrofLuigi]

No problems with beta2 here.

GL

[clickit]

Since now I used all plugins without the loadplugin(....) command
but in this beta doesn't seems to work without it
I tried to play this simple script

MPEG2Source("film.d2v")

in MPC and the application just closed !!!
when i put the loadplugin("....\DGDecode.dll") command it worked fine

edit : all that happened with latest beta2

[IanB]

Tritical,

:o Yes indeed the windout code is not working. A problem with the way I hacked in allowing more arguments. I've CVS'ed up the repairs.

Get a replacement DLL from here. Feb 28th, 2005 Avisynth.dll (http://avisynth2.sourceforge.net/28Feb2005/avisynth.dll) Replace the one in C:\Windows\System.

Richard,

:confused: I can't reproduce it, but I did have a big hack at "Evaluate: Unrecognized exception!" code to make it fess up what the exception actually was. I could have broken it, or it could be a manefestation of the destructor bug above, this bug made things very sick in lots of unrelated places. Try again with the fixed version.

IanB

[JuanC]

Thanks a lot IanB, I have just dnlded the new DLL, but there's still the "vanishing" problem with a simple sintax error.

[IanB]

JuanC, Richard,

:confused: What are your platform details?

AMD or Intel? K6, Piii, Piv, Opteron, etc

OS? W98, Wme, W2K, XP, XPsp2, etc

Config? etc?

IanB

[JuanC]

My PC is a P4/2GHz(Northwood), 1GB DDR266, intel 845 chipset. WinXP-SP2.

[tritical]

@IanB
Yep, works fine on my comp now, thanks.

[Wilbert]

If I make errors in my script (using VDubMod's script editor) the following happens: Instead of showing the proper error message it says

"Cannot open file "": The system can't find the path specified."

If I reopen the faulty script in VDubMod I get the proper error message.

Athlon XP, W2K SP4.

[Richard Berg]

Same problem with new DLL. Plugin dir is empty. Scripts w/o errors work ok. Athlon XP. Windows XP SP2.

What compiler are we using now?

[JuanC]

Well, definitely it’s not a hardware related issue (in my case at least). My PC is multi booted. I have Win ME as an option. It’s rather clean/ naked, with just the critical updates; Directx 7.1, wmp 7.0…; and some old programs. I just tried AVIsynth 2.56 beta2 and also the latest dll running VdubMod. The syntax errors show as they should: VDubMod is not "vanishing" in WinME.

Some ideas come to my mind: Though my WinXP installation is rather old (I haven’t re-installed it since 2-3 years ago), it's fully functional. No problems with the previous AVIsynth 2.56 beta (jan.6). I was wondering what the relevant differences are between my XP and ME installations, and then I think I’d ask: Could these two make any difference: ?

Some time ago I had Visual Studio 6.0 with SP5 (and/or 6???) installed. Could there be some remaining stuff?
Also, to use some application(s?) (I don’t remember which one) I had to install MS .NET runtime, and it has been "windowsupdated" at least once.

Hope this helps…

[IanB]

Dear all,

DAMN! Microsoft SP2

Stay tuned...

IanB


Richard,

I'm still using the standard VC6 sp5 + PP.

[Richard Berg]

I will try a compiler that's not 7 years old and see if it helps anything :)

(free download (http://lab.msdn.microsoft.com/express/visualc/))

[Arachnotron]

I was playing a bit with sysinternals filemon and the 210205 build. Upon an error in an avs script, vdubmod and mplayerRC simply crash (no file not found error)

I tried a trace with filemon while opening a test.avs from the explorer using the "open with" context menu to open it in mplayerRC. I get this stuff in the log. Mind, I get the same when playing back an avs without an error in it. Maybe it is of help to someone. :)

22:20:37 explorer.exe:2564 OPEN C:\cap\AviSynth 2.56\test.avs\:Docf_SummaryInformation:$DATA FILE NOT FOUND Options: Open Access: All
22:20:37 explorer.exe:2564 OPEN C:\cap\AviSynth 2.56\test.avs\:SummaryInformation:$DATA FILE NOT FOUND Options: Open Access: All
22:20:37 explorer.exe:2564 OPEN C:\cap\AviSynth 2.56\test.avs\:Docf_SummaryInformation:$DATA FILE NOT FOUND Options: Open Access: All
22:20:37 explorer.exe:2564 OPEN C:\cap\AviSynth 2.56\test.avs\:SummaryInformation:$DATA FILE NOT FOUND Options: Open Access: All
22:20:37 explorer.exe:2564 OPEN C:\cap\AviSynth 2.56\test.avs\:Docf_SummaryInformation:$DATA FILE NOT FOUND Options: Open Access: All
22:20:37 explorer.exe:2564 OPEN C:\cap\AviSynth 2.56\test.avs\:SummaryInformation:$DATA FILE NOT FOUND Options: Open Access: All
22:20:37 explorer.exe:2564 OPEN C:\cap\AviSynth 2.56\test.avs\:Docf_SummaryInformation:$DATA FILE NOT FOUND Options: Open Access: All
22:20:37 explorer.exe:2564 OPEN C:\cap\AviSynth 2.56\test.avs\:SummaryInformation:$DATA FILE NOT FOUND Options: Open Access: All
22:20:37 explorer.exe:2564 OPEN C:\cap\AviSynth 2.56\test.avs\:Docf_SummaryInformation:$DATA FILE NOT FOUND Options: Open Access: All
22:20:37 explorer.exe:2564 OPEN C:\cap\AviSynth 2.56\test.avs\:SummaryInformation:$DATA FILE NOT FOUND Options: Open Access: All
22:20:37 explorer.exe:2564 OPEN C:\cap\AviSynth 2.56\test.avs\:Docf_SummaryInformation:$DATA FILE NOT FOUND Options: Open Access: All
22:20:37 explorer.exe:2564 OPEN C:\cap\AviSynth 2.56\test.avs\:SummaryInformation:$DATA FILE NOT FOUND Options: Open Access: All
22:20:37 explorer.exe:2564 OPEN C:\cap\AviSynth 2.56\test.avs\:Docf_SummaryInformation:$DATA FILE NOT FOUND Options: Open Access: All

[edit] Never mind, just installed 2.55 and while with that the avs error messages work as they should, these file not found errors are still in the filemon output.

[azsd]

with this feb28 dll replaced with installed beta1 2005-01-06
when I use unassigned variables or some other arg incorrecly,it will terminal the VDubMod directly(in last 01-06 build it will give an tip),and some correct scripts working in provours builds will randomizely get nero recode disappear while 2pass encoding,some times at 60%,some time at 80%.

So I choice get to use that alpha version back soon.

[IanB]

Here is an attempt to resolve the problems with XP sp2 and script exceptions causing fatal aborts.

XP sp2 users please test!

A replacement .dll is available here Mar 10th, 2005 Avisynth.dll (http://avisynth2.sourceforge.net/10Mar2005/avisynth.dll), just replace the one in your windows system directory.

A little help from someone with a VC6sp5 development environment on XP sp2 might be needed. I have no problem with W2K or W98 so I am guessing blind as to the problems cause.

Regards
IanB

[esby]

@IanB:

I am under windows XP & SP2.
I can test if you want.
Just tell me what kind of scripts to test.
I also have vc6.2 installed.

esby

[IanB]

Esby,

Originally posted by esby
I am under windows XP & SP2.
I can test if you want.
Just tell me what kind of scripts to test.
Ta muchly!

The reported problem was that script errors cause various video editors (Vdub, Tmpg, etc) to just cold abort, instead of reporting the syntax error. So run script with a syntax error, i.e. missing comma or bracket, a spelling mistake, etc...

I guess the test is reproduce the problem with both Wilberts 21st Feb release and my 28th Feb replacement avisynth.dll, then try my Mar 10th replacment avisynth.dll to see if the problem is fixed. If so then report it here, jobs done :D

If the problem still occurs, then suck down the latest CVS, build a debug version, check to see the problem still occurs and then run it up under the debugger and start with the bug spray. The most likely place to look is in "avisynth/src/core/parser/expression.cpp", the code near the top the file, the __try/__except addition is where I was last working.

T.I.A.

IanB

[esby]

Well I did some testing.

BigError.avs

BigError()


BigError2.avs

try{
BigError()
}
catch(error)
{
version()
}


with the dll I got from your link:

First, it says jan 23 2005 with version().

BigError.avs crashes abruptely.
BigError2.avs crashes abruptely.

Now if I build a cvs version.

Apparently it seems a bit weird.
with a debug version,
BigError.avs will display the normal error message.
BigError2.avs will display the version message, which is normal.
and with a release version, it will crashes.
I am not sure of what's going on, but I'll check sunday.

esby

[IanB]

Dear XP-sp2 users,

Well here is another attempt, I'm sort of figuring on a compiler glitch, so I've tweaked the code to improve the readability of the generated assembler and have proof read it.

Mar 15th, 2005 Avisynth.dll (http://avisynth2.sourceforge.net/15Mar2005/avisynth.dll), it is intended as a direct replacement of the avisynth.dll from the released 2.5.6alpha2 package. (Just put it in your Windows\System directory).

@Esby,

Thanks, try the new one please. The CVS commit should trickle thru to the public server in a few hours.

IanB

[JuanC]

I still get vdubmod "vanishing" on any avisynth syntax error with this last (march 15th) build.

Thanks for your hard work Ian. Is there any other thing, besides compiling avisynth (I wouldn't be able to do so), I could do to help test?

[IanB]

JuanC,

This is very frustrating :mad: blind debugging is a real <insert favourite profanity here>!!

Here is a version with what I think is the problem change backed out, can someone please test this.

Back out Avisynth.dll (http://avisynth2.sourceforge.net/15Mar2005backout/avisynth.dll), it is intended as a direct replacement of the avisynth.dll from the released 2.5.6alpha2 package. (Just put it in your Windows\System directory).

IanB

[Boulder]

With that dll, I get a correct error message when I try to load a clip that isn't there. If that's what you were after, it works:)

EDIT: and syntax errors appear correctly as well.

[IanB]

Boulder,

Thanks, at least I know I have the right haystack now I have to find the needle:( maybe if I just sit down it will stick me.:sly:

To confirm :-

1. You are running XP-sp2,
2. the .DLL I put up this morning causes silent aborts with script errors,
3. the backout .DLL I put up the evening works A-Okay.

Looks like I am gunna have to get onto an XP-sp2 to solve this.:mad:M$

Regards
IanB

[Boulder]

Originally posted by IanB

To confirm :-

1. You are running XP-sp2,
2. the .DLL I put up this morning causes silent aborts with script errors,
3. the backout .DLL I put up the evening works A-Okay.

Yep, all three match.

[IanB]

Boulder, others,

Just a thought, did M$ update MSVCRT.DLL in SP2 because the runtime routine _except_handler3() is the other variable in the equation.

I'm currently running version 6.10.8924.0, what version does SP2 clock up?

Thinking out loud...

IanB

[Boulder]

I've got 7.0.2600.2180, which kind of adds up since isn't .2600.2180 XP w/ SP2, at least .2600 means WinXP.

The file creation date is in August 2004 so it would be around the time when SP2 was released.

[Zom-B]

in my WinXP SP2 C:\WINDOWS\system32 the msvcrt.dll got this Version Info:

7.0.2600.2180 (xpsp_sp2_rtm.040803-2158)

[IanB]

Yes those needles in haystacks really do sting when you sit on them.

Just did a quick google and it looks like M$ :devil: has done something bad with MSCVRT.DLL version 7.0.2600.2180, no concrete proof yet but it's a place to start to look.

Later dudes
IanB

[JuanC]

Just confirming:

\WINDOWS\SYSTEM32\MSVCRT.DLL 7.0.2600.2180 (xpsp_sp2_rtm.040803-2158)

The newer build doesn't make vdubmod to "vanish" on avisynth script syntax errors. It displays the correct error message. :) Thanks againg for your work!

EDIT: I noticed a change in the color bands to each side of the image showing the invalid colors in YV12 (<16 & >235), when using the Histogram() filter in classic mode. :) I preferred the old darker color in previous builds ;)

[Wilbert]

EDIT: I noticed a change in the color bands to each side of the image showing the invalid colors in YV12 (<16 & >235), when using the Histogram() filter in classic mode. :) I preferred the old darker color in previous builds ;)
I changed that. Those old dark colors are barely visible when making screenshots. Btw, it works for YUY2 too now.

[JuanC]

Originally posted by Wilbert
...Btw, it works for YUY2 too now. Great! Thanks :)

[azsd]

LanczosResize/BicubicResize/BilinearResize have strange frames in special target size:

when target width beside in 732 to 916,it's have an offseted channel s picture:

http://my1993.com/PpsDES/Cap/avs_resize_w852.jpg

Windows 2003,Avisynth 2.5.6 Pre-Releases.

[azsd]

sorry,I found the strange images may caused by xvid as YV12 decoder.

[digitalman]

This build fixed the problems I was having with DVR MPEG2 files. It would crash with certain plugins, or with certain programs like QUENC.

[Wilbert]

AviSynth 2.5.6 beta 3 Release (May 5th):

additions:
- Added method VideoInfo.MulDivFPS(unsigned multiplier, unsigned divisor) does rational scaling with normalizing and overflow protection of FPS property.
- Added offsets, gamma and analyze option (ala ColorYUV) in RGBAdjust.
- Added Spline16Resize, Spline36Resize, GaussResize and LanczosResize(tap=xx)
- Added options to ShowFrameNumber: ShowFrameNumber(offset=10, x=360, y=576, font="georgia", size=24, text_color=$ff0000)
- Added integer offset to ShowSMPTE: ShowSMPTE(offset_f=10)

fixes:
- Fixed FPS overflow with Select...(), Interleave() and variants.
- Fixed subtract mode in Overlay (chroma is correctly subtracted).
- Fixed align parameter in Subtitle.
- Revert "Evaluate: Unrecognized exception!" change for hard quit whenever there's an exception instead of showing error message (XPsp2 possible problem due to XPsp2's new msvcrt.dll).
- Windout code is working again (broking in the previous betas).
- Corrected multi-channel audio fading.

optimizations:
- Text overlay antialiaser tweaked, 8% faster Work in progress, more to come.
- RGB32 FlipHorizontal() code tweaked.

changes:
- Planar alignment (default 16 bytes) now based on chroma planes, luma alignment is (still) 2x chroma.
- Support for [vfr content in DSS]: DirectShowSource("F:\Guides\Hybrid\vfr_startrek.mkv", fps=119.88, convertfps=true) turns vfr into cfr stream by adding frames.

As usual download from Sourceforge (http://sourceforge.net/projects/avisynth2/).

[Boulder]

Something is broken..setting any postprocessing level in MPEG2Source (the latest DGIndex/DGDecode combination) gives garbage output. With parameter CPU=0 no problems. IanB's last version works just fine.

[tritical]

I noticed that as well, but it appears to be a bug in dgdecode not avisynth. When dgdecode calls postprocess it uses width as the pitch instead of the actual y plane pitch. In this avisynth release it looks like UV pitch is calculated first for YV12, and by default is 16 byte aligned, so the y pitch ends up being 32 byte aligned, and thus not equal to the width for non-mod 32 frames (720xXXX for example). Only one line needs to be changed to fix things though :).

[stickboy]

Originally posted by Wilbert
- Added method VideoInfo.MulDivFPS(unsigned multiplier, unsigned divisor) does rational scaling with normalizing and overflow protection of FPS property.

- Fixed FPS overflow with Select...(), Interleave() and variants.Awesome. I kept meaning to add some code to do this (analogous to my AssumeScaledFPS (http://www.avisynth.org/stickboy/) function) but laziness and other work kept overwhelming me. :)

[IanB]

Guys,

This version has the "Evaluate: (Un)Recognise(d) Exception." code back in, very much distilled and refined, and under XPsp2 it still cause host programs (editors/viewers) to hard terminate. Under XPsp1/W2K/Nt4/98/Me everything seems to work A-Okay.

So I am again looking for some very kind soul with an XPsp2 platform with VS6sp5+pp (std AVS build env) development environment, to build a "Release" .dll with symbols and run it up under the debugger, load a script with a deliberate error and tell me where, why, how, when and what Microsoft did in sp2 that so royally screws this simple piece of code.

The problem is in the 3 routines around line 144 of core\parser\expression.cpp and seems to be something awry in msvcrt.dll to do with the routine __except_handler3

T.I.A.
IanB

[iNFO-DVD]

just tried this beta 3 release and now have a green bar down the left side when viewing movie's via avs, wern't there in previous version, doesn't happen with all movies.

[IanB]

Originally posted by iNFO-DVD
just tried this beta 3 release and now have a green bar down the left side when viewing movie's via avs, wern't there in previous version, doesn't happen with all movies.
:script:
At a guess I'm gonna say this is something to do the increased YV12 plane alignment, and odds are it's not gonna be in the core avisynth.dll (but it might be:o ). However we do support a very large number of client pluggins and server applications, Tritical has already found one in DGdecode, so a little bit of extra information like :-
1. The application(s) that exhibit the problem.
2. Some info about the movies like formats and frame sizes.
3. Your script.
4. Width of the green bar, 8 pixels, 16 pixels, 100 pixels.
5. Your OS platform (XPsp2, XP, W2K, Nt4, ME, 98, etc)
6. Your processor P-III, P-IV, K6, Athelon, etc

Any little bit can be extremely helpful.

IanB

[iNFO-DVD]

I've removed it now and haven't got time to test right now as it's 2:40 am, and bed's calling.... :D

But, my OS = WinXP Pro SP2
Intel P4 3GHz

The green bar appeared in an NTSC clip (29.970), but not in my PAL or FILM clip, but that could have been coincidence. I tried to snapshot the green bar, but failed, I'd guess it was somewhere between 8 to 16 pixels wide, ran down the left and appeared to have interlacing..... you know, thick weave bars....

the script was just a simple one, the bare minimum.

Get more info for ya when i wake...

[iNFO-DVD]

It was on my mind, I re-installed it and managed to get a screen-shot of it, it's attached to this message.

It's an NTSC clip, well, a bit hybrid actually, anyway, doesn't happen all the way through, just different places and when displayed, it flashes.

[sh0dan]

:script:

[IanB]

For reference the image is 726x486.
The image seems to have a 3 pixel border all around.
The green bars are 16 pixels wide and 2 pixels high with a 2 pixel gap.
The 1st occurance, lines 01, seems absent.
The pattern appears on lines 45,89,...
The lower half of the green bar is effected by the adjacent luma, this may be a JPG artifact local to the image.

Starting to smell like the DGDecode problem from a few posts up.

IanB

Edit : B I N G O Look, smells, feels, quacks like a duck - must be a duck:sly:

[iNFO-DVD]

my script was simply:

LoadPlugin(blah blah blah \DGDecode.dll")
MPEG2Source( blah blah blah \VTS_03_PGC_04_1.d2v")

BTW, the movie/clip in question is:

UNBREAKABLE
NTSC REGION 1
(DISK 2) SPECIAL FEATURES
VTS03
PGC04

[Boulder]

Originally posted by IanB

Starting to smell like the DGDecode problem from a few posts up.

Is Don aware of the issue? I didn't see any posts in the appropriate forum regarding it.

[Guest]

Please explain the alignment changes and why they are considered important enough to break existing applications.

[Guest]

Originally posted by iNFO-DVD
LoadPlugin(blah blah blah \DGDecode.dll")
MPEG2Source( blah blah blah \VTS_03_PGC_04_1.d2v")
I don't see any post-processing here. Are you guys saying that DGDecode is broken for everything now, and not just for PP?