AviSynth+ thread Vol.2

[ravewulf]

PremiereAVSPlugin v1.95 causes Premiere CS3 to crash with both 3.6.0 and 3.6.1 test6 while it was working with previous versions of AviSynth+. I'm not too skilled in C/C++ (web development is more my forte) but was able to compile a debug version of PremiereAVSPlugin to find where the crash was within the plugin. Note that compiling requires premiere_pro_cs3_r1_sdk_win.exe or similar and the project on SourceForge needed to be modified to include some existing header/cpp files that weren't loaded by default.

GetInfo.cpp Line 299

res = fi->scriptEnvironment->Invoke("Import", AVSValue(&arg, 1));

Exception thrown at 0x26E1938C (AviSynth.dll) in Adobe Premiere Pro.exe: 0xC0000005: Access violation reading location 0xC7FBC448

I'm guessing it could use updating to new interfaces but the project seems to be abandoned given it was last updated in 2009 and I'm not sure how to fix it myself. Probably a low priority issue as I can work around it by skipping the Premiere plugin and either using MakeAVIS to create a "fake" avi for Premiere to load or else rendering out an actual avi file. More of a "nice to have" if it can be fixed

[pinterf]

Originally Posted by ravewulf

[[/code]
I'm guessing it could use updating to new interfaces but the project seems to be abandoned given it was last updated in 2009 and I'm not sure how to fix it myself. Probably a low priority issue as I can work around it by skipping the Premiere plugin and either using MakeAVIS to create a "fake" avi for Premiere to load or else rendering out an actual avi file. More of a "nice to have" if it can be fixed

I have placed you two links at the first post in this thread.
I'm curious so
- first: please try your _existing_ plugin with the test7 avisynth.dll (only 32 bit version provided)
- second: try the _updated_ plugin (Avisynth version can remain)
Let me know your results after both cases.

[pinterf]

Originally Posted by Gavino

This has always been so, at least in 'classic' Avisynth.
(or is this a bug-fix for something that crept in recently?)

Simple test:

Version()
function f() { return 0 }

That was a recent one.
It was a regression (appearing in 3.6) after incorporating Neo-fork updates.

[pinterf]

Originally Posted by FranceBB

Actually I gotta say that I found yet another thing... (sorry).
MPPipeline works, but if you go to XYZ and then come back to YUV it doesn't work...

MP_Pipeline("""
ColorBars(848, 480, pixel_type="YV12")

ConvertBits(16)

### ###

ConvertYUVtoXYZ()

### ###

ConvertXYZtoYUV(Color=1, pColor=2)

""")

Well, the output of ConvertYUVtoXYZ() is using RGB64 and not planar RGB, probably we could eliminate the use of 'packed' formats and prefer planar RGB instead.

And why you saw such blackness: because I prepared MP_Pipeline high bit depth for planar colorspaces only and forgot about RGB48 and RGB64. Until then use a ConvertToPlanarRGB(A) after the YUV-XYZ conversion.
edit: Check MP_Pipeline 0.21

[Reel.Deel]

Originally Posted by ravewulf

PremiereAVSPlugin v1.95 causes Premiere CS3 to crash with both 3.6.0 and 3.6.1 test6 while it was working with previous versions of AviSynth+.

This wont fix your problem but there is another variant of this plugin that supported CS3 and CS4, also released in 2009. I wonder if they have the same problem. I don't have any Adobe products so I can't test it myself.

csavs: Premiere CS AVS Importer for CS3 and CS4

• https://web.archive.org/web/20180320...ion.net/csavs/

Later on there was an update to that plugin to support CS5 and 64-bit.

csavs64: Premiere CS AVS Importer x64 1.1 (pre CS5 plugins will not work)

• setup: https://web.archive.org/web/20150324...grams/csavs64/
• source: http://pwolfamv.com/programs/csavs64/

[kedautinh12]

Pinterf was released PremiereAvsPlugin 1.96 for Avisynth+ and Avisynth 2.6 interface.
https://github.com/pinterf/PremiereAVSPlugin/releases

[kedautinh12]

Also updated MP_Pipeline
https://github.com/pinterf/MP_Pipeline

[ravewulf]

Originally Posted by pinterf

I have placed you two links at the first post in this thread.
I'm curious so
- first: please try your _existing_ plugin with the test7 avisynth.dll (only 32 bit version provided)
- second: try the _updated_ plugin (Avisynth version can remain)
Let me know your results after both cases.

Not sure if this is expected but AvsPmod Version 2.6.2.5 gives an ignorable error with test7

Exception WindowsError: 'exception: access violation reading 0x9DE18AFD' in <bound method AVS_ScriptEnvironment.__del__ of <avisynth.AVS_ScriptEnvironment object at 0x03857690>> ignored

The results of the first test were a bit surprising. Using the test7 build with the existing Premiere plugin works if the script is video-only. But if the script has video and audio (or audio alone) it causes Premiere to crash. Tested with both external audio files and the built-in ColorBars function.

The new updated Premiere plugin works perfectly with video and audio for both 3.6.0 and 3.6.1 test7.

Let me know if you want me to test the old Premiere plugin with future test updates to see if the audio issue can be fixed as a test case for similar plugins. Otherwise, I'll just use the new version of the plugin you built. Thank you!

Originally Posted by Reel.Deel

This wont fix your problem but there is another variant of this plugin that supported CS3 and CS4, also released in 2009. I wonder if they have the same problem. I don't have any Adobe products so I can't test it myself.

csavs: Premiere CS AVS Importer for CS3 and CS4

• https://web.archive.org/web/20180320...ion.net/csavs/

Later on there was an update to that plugin to support CS5 and 64-bit.

csavs64: Premiere CS AVS Importer x64 1.1 (pre CS5 plugins will not work)

• setup: https://web.archive.org/web/20150324...grams/csavs64/
• source: http://pwolfamv.com/programs/csavs64/

Looks like the 32-bit version of this plugin has similar results to the first test where it crashes with 3.6.0, crashes with video+audio in 3.6.1 test7, and works for video-only clips in 3.6.1 test7.

I don't have the newer 64-bit versions of Premiere to test the 64-bit plugin though. I use CS3 to have audio playback and a zoom-able timeline while I work on cuts/timing issues then go back to 64-bit AviSynth/AvsPmod for everything else after exporting an EDL file. No need to sink a ton of money in subscription fees to Adobe for new features/encoding support I don't use

[MeteorRain]

https://github.com/HomeOfAviSynthPlu...f3kdb/issues/4

Seems like 3.6 added some enums from VapourSynth and thus directly conflicts with VapourSynth headers. Any good ways we can get around with it and include both headers in one file?

[feisty2]

Originally Posted by MeteorRain

https://github.com/HomeOfAviSynthPlu...f3kdb/issues/4

Seems like 3.6 added some enums from VapourSynth and thus directly conflicts with VapourSynth headers. Any good ways we can get around with it and include both headers in one file?

you need "enum class"
https://godbolt.org/z/dKLqkB

[Selur]

I can confirm that HDRAGC works fine with Avisynth_3.6.1_20200604_test6.
And SmoothCurve also works now.
Thanks! Now I can switch to 3.6.x

[pinterf]

Originally Posted by feisty2

you need "enum class"
https://godbolt.org/z/dKLqkB

Yes, I was planning that. But I'll guard it with ifdefs. You know it requires C++11.

[StainlessS]

Originally Posted by pinterf

You know it requires C++11.

Feisty, cares not a jot for compatibility.

[feisty2]

Originally Posted by pinterf

Yes, I was planning that. But I'll guard it with ifdefs. You know it requires C++11.

ancient compilers that do not even support c++11 up until this day should just die.

[feisty2]

besides there're many workarounds other than enums
you may use a namespace

namespace PropTypes {
    constexpr auto ptUnset = 'u';
    constexpr auto ptNode = 'n';
    ...
}

auto x = PropTypes::ptNode;

you may also place these constants in a struct as static variables

struct PropTypes final {
    static constexpr auto ptUnset = 'u';
    static constexpr auto ptNode = 'n';
    ...
};

auto x = PropTypes::ptNode;

[gispos]

Originally Posted by ravewulf

Not sure if this is expected but AvsPmod Version 2.6.2.5 gives an ignorable error with test7

Exception WindowsError: 'exception: access violation reading 0x9DE18AFD' in <bound method AVS_ScriptEnvironment.__del__ of <avisynth.AVS_ScriptEnvironment object at 0x03857690>> ignored

Who wants to play with the avisynth test 7 version and AvsPmod.
This eliminates the window error message on startup.

Exchange the included library.zip with the one in the lib folder. 32bit only.

Removed. The problem is deeper

Edit: test7 seems to have a problem releasing the IScriptEnvironment

[stax76]

Seems like 3.6 added some enums from VapourSynth and thus directly conflicts with VapourSynth headers. Any good ways we can get around with it and include both headers in one file?

I just disabled these new definitions using comments, it's easy and for now works for me, I hope it doesn't become an issue in the future.

[MeteorRain]

The issue with the conflicts, for now, is that filters will include headers from system directories (/usr/include or whatever), so I can't touch that for now, unless I choose to ignore that and always use an old version of headers that I carry.

I think maybe I should just wait until the issue is resolved.

[tormento]

Out of curiosity: why do you keep devil.dll in a "system" directory, separate from avisynth.dll? They will go in the same windows directory, at the end.

[stax76]

Originally Posted by tormento

Out of curiosity: why do you keep devil.dll in a "system" directory, separate from avisynth.dll? They will go in the same windows directory, at the end.

I wondered about that too.