AviSynth 2.6.0 [May 31st, 2015]

[RRD]

I installed AviSynth 2.6.0 [May 31st, 2015], three files were created in the /AviSynth/plugins folder:


Whenever I try to use SoundOut() I get “Script error: there is no function named "SoundOut"”.

I downloaded Wilbert's SoundOut26-1.1.1.zip (that he posted in http://forum.doom9.org/showpost.php?...&postcount=185). If I put SoundOut.dll and libsndfile-1.dll in the /AviSynth/plugins folder, SoundOut() works.

Several pages indicate that the SoundOut plugin is included in AviSynth from 2.6.0 on (http://avisynth.nl/index.php/SoundOut), so I believe the behaviour I am experiencing is not normal.

Oddly, it is not mentioned in the 2.6.0 changelog (AviSynth/Docs/English/changelist26.htm file).

The same issue occurred on my two PCs (Windows 7 32-bit and Windows 7 64-bit) and I fail to see what I did wrong.

[Groucho2004]

Originally Posted by RRD

Several pages indicate that the SoundOut plugin is included in AviSynth from 2.6.0 on (http://avisynth.nl/index.php/SoundOut), so I believe the behaviour I am experiencing is not normal.
Oddly, it is not mentioned in the 2.6.0 changelog

All I can tell you is that SoundOut is not part of the Avisynth core no matter what is written on some pages.
The change log is the most reliable source.

[Wilbert]

Yes it's not part of the core yet, i will update the documentation.

[ryrynz]

Wilbert, using ffdshow and Avisynth 2.6 with Tritical's NNEDI3 using the following syntax

nnedi3_rpow2(rfactor=2)

is causing display issues (interlaced, stretched and wrong colors) in the media player MPDN, this issue does not occur with MPC so the developer thinks it's related to to memory corruption which .NET is quite strict on. I haven't encountered any issues using any other filters in MPDN with ffdshow.

Any chance I could get you track down where the issue lies?

The only thing that seems to affect it is setting RGB out in ffdshow, this changes the colors to match the original frames.

This issue occurs also with Avisynth MT and jpsdr's NNEDI3.
Cheers.

[hello_hello]

Originally Posted by ryrynz

The only thing that seems to affect it is setting RGB out in ffdshow, this changes the colors to match the original frames.

I don't know about the stretching, but I've found (using XP) that MPC-HC uses the wrong colorimetry for HD video (rec.601) when opening Avisynth scripts, unless ffdshow's raw video decoder is enabled in which case it displays using rec.709. I don't understand why, but a different set of filters is used.

With ffdshow's raw video decoder enabled (for YUV):
AVI/wav file source
ffdshow video decoder
WMR9 (renderless)

With ffdshow's raw video decoder disabled:
AVI/wav file source
AVI decompressor (YV12)
colour space converter
WMR9 (renderless)

In the second case I assume the colour space converter is converting to RGB using the wrong colorimetry.

[Groucho2004]

Originally Posted by ryrynz

causing display issues (interlaced, stretched and wrong colors) in the media player MPDN, this issue does not occur with MPC so the developer thinks it's related to to memory corruption

I can't follow the logic here. How does this point to Avisynth being the cause?

You should start with the most likely candidates for this problem,
- player/renderer
- ffdshow

Have you tried with AVS+?

[Groucho2004]

Originally Posted by hello_hello

I don't know about the stretching, but I've found (using XP) that MPC-HC uses the wrong colorimetry for HD video (rec.601) when opening Avisynth scripts, unless ffdshow's raw video decoder is enabled in which case it displays using rec.709. I don't understand why, but a different set of filters is used.

Why is this in the Avisynth thread?

[ryrynz]

Originally Posted by Groucho2004

I can't follow the logic here. How does this point to Avisynth being the cause?

You should start with the most likely candidates for this problem,
- player/renderer
- ffdshow

Have you tried with AVS+?

The logic is to start where you think someone can help

Player - I've already asked as above, perhaps his conclusion could be wrong, IDK, that's what I'm trying to figure out.
Renderer - No options to switch renderer in MPDN, but I've already tried all the options for output. Either I get no image or a distorted one.
ffdshow - no dev, no help. Again I've already looked at all the options, no difference.

Yes, same issue with AVS+ too (1576) Also occurs on my Intel graphics system running 7 (the other is running 10 with a 750Ti) so it's not related to any Windows version or graphics card drivers.

It would be quite simple to replicate, just need someone who can determine what's causing it and my first thought was Wilbert. Any help is appreciated.

[Groucho2004]

Originally Posted by ryrynz

The logic is to start where you think someone can help

Player - I've already asked as above, perhaps his conclusion could be wrong, IDK, that's what I'm trying to figure out.
Renderer - No options to switch renderer in MPDN, but I've already tried all the options for output. Either I get no image or a distorted one.
ffdshow - no dev, no help. Again I've already looked at all the options, no difference.

Yes, same issue with AVS+ too (1576) Also occurs on my Intel graphics system running 7 (the other is running 10 with a 750Ti) so it's not related to any Windows version or graphics card drivers.

It would be quite simple to replicate, just need someone who can determine what's causing it and my first thought was Wilbert. Any help is appreciated.

OK. All Avisynth versions show the same behaviour. I'm quite certain that you can rule out Avisynth.
You mentioned MPC, I would try MPC-HC and/or MPC-BE (or any other suitable player you can think of). If your problem doesn't show up with those I think you have found your culprit.

Edit: One more thing you could try is setting the internal number of threads to 1 in nnedi3.

[ryrynz]

Originally Posted by Groucho2004

OK. All Avisynth versions show the same behaviour. I'm quite certain that you can rule out Avisynth.
You mentioned MPC, I would try MPC-HC and/or MPC-BE (or any other suitable player you can think of). If your problem doesn't show up with those I think you have found your culprit.

No issues with HC, BE, Zoomplayer or Potplayer. Guess I'll need Zach to look into it further.. I do wonder though what's different about the output of NNEDI3 that causes this to happen. I've had no issues with any other filters.

[Groucho2004]

Originally Posted by ryrynz

I do wonder though what's different about the output of NNEDI3 that causes this to happen. I've had no issues with any other filters.

Have you tried what I suggested in my edit above?

[ryrynz]

Tried it, threads=1 and 0, also tried opt=1 and fapprox=0, no change.

[foxyshadis]

Try ending the scripts with Info() to figure out what colorspace nnedi3 is converting to. Maybe that'll sort it.

[real.finder]

ColorBars(width=640, height=480, pixel_type="RGB32")
ConvertToYV12(interlaced=true,chromaoutplacement="dv")
SeparateFields
uToY

ColorBars(width=640, height=480, pixel_type="RGB32")
Dither_convert_rgb_to_yuv(cplace ="dv",interlaced=true)
SeparateFields
uToY

there are a noticeable difference in vertical shift between them, I think the ConvertToYV12 do the dv-pal chroma with reverse u and v in shifting

----


edit: look like it not in ConvertToYV12 only

test with yv16

ColorBars(width=640, height=480, pixel_type="RGB32")
ConvertToYV16(interlaced=true)
SeparateFields
uToY

ColorBars(width=640, height=480, pixel_type="RGB32")
Dither_convert_rgb_to_yuv(cplace ="dv",interlaced=true)
ConvertToYV16(chromainplacement="dv", interlaced=true)
SeparateFields
uToY

edit: YToUV(VToY8(), UToY8(), ConvertToY8()) (or SwapUV()) before and after ConvertToXXX will solve the problem

[ryrynz]

Originally Posted by foxyshadis

Try ending the scripts with Info() to figure out what colorspace nnedi3 is converting to. Maybe that'll sort it.

Info() just shows that YV12 being used. Subtitles delivered by xysubfilter appear perfectly normal on top of the stretched pink and green distorted display. Still no closer to figuring this one out. One thing I didn't mention is that nnedi3 used with awarp4 delivers the proper output.

Also if I launch a script playing that doesn't have nnedi3 in it and then change to one that does via ffdshow raw the output is correct, if I start with that script then the picture is distorted.

Another thing I've noticed is that when using MPC and nnedi3/ffdshow any subtitles displayed get processed by nnedi3, with MPDN they don't.. could that be related somehow? Disabling subtitles completely in MPDN doesn't change anything so I guess not.

[StainlessS]

Below Fails in v2.5 but works ok in v2.6.

INPUT=avisource("F:\V\cabaret.avi")
return last

Only mentions of 'Last' in v2.6 ChangeList below

Fixed AviSource NULL GetWritePtr() failure due to premature setting of last_frame. 
WriteFileStart/End save current_frame and set Last. 
Change implicit Last parsing for argless, bracketless calls to match bracketed cases. (Gavino)

Is it a bug or undocumented change ?

EDIT: Same for

INPUT=Directshowsource("F:\V\cabaret.avi")
return last

EDIT: IGNORE ABOVE ...
Uninstalled Avisynth completely. Deleted remaining Avisynth directory. Ran CCleaner and Cleaned registry too.
Re-installed Avisynth v2.6. No longer succeeds with above code snippit.
No idea at all why it succeeded before

[Groucho2004]

Originally Posted by rean

Hello. Anyone compiled Avisynth using Visual C++ 2015?

Don't do it.
Newer compilers expect the code to be compliant with SEH (Microsoft Structured Exception Handling) which the current code base is not.

Apparently, Avisynth 2.6.1 will be compatible with newer compilers.

[Groucho2004]

Originally Posted by rean

Groucho2004, /SAFESEH:NO

Never used it, I'd have to research what it does and if/how it would help.

[Groucho2004]

Originally Posted by rean

I have successfully compiled it (with SEt MT mod). It seems work correctly and exceptions are work too.

Ok. Please run this script with AVSMeter and tell us what happens:

setmemorymax(9999)
n = 12
colorbars(width = 1920 * n, height = 1080 * n, pixel_type = "yv12").killaudio().assumefps(25, 1).trim(0, 9999)
pointresize(width() - 64, height() - 64).turnleft()
temporalsoften(2,4,8,15,2)
pointresize(width() + 64, height() + 64).turnright()
temporalsoften(2,4,8,15,2)
a=selectevery(3, 0).addborders(0,0, 16,0).crop(0,0, -16,0)
b=selectevery(3, 1).addborders(0,0, 32,0).crop(0,0, -32,0)
c=selectevery(3, 2).addborders(0,0, 64,0).crop(0,0, -64,0)
interleave(a, b, c)

[Groucho2004]

Originally Posted by rean

Groucho2004,
You mean benchmark or memory usage? It works with the same speed as the reference mt 2.6 build and it eats the same memory (using your script or my real usage scripts). The difference is +/-1 %

That script causes Avisynth to throw an out of memory exception after reading 1 or 2 frames. I just wanted to know if your DLL behaves correctly in this situation.

Originally Posted by rean

It works with the same speed as the reference mt 2.6 build and it eats the same memory (using your script or my real usage scripts).

I'm surprised, to say the least, that the script actually worked for you.