Adobe Media Encoder

[tormento]

Is there any way to pipe Avisynth output to Adobe Media encoder?

[StainlessS]

You could take a look at this [Premiere plugin - might work], but is old.
https://www.mediafire.com/file/agaupm5xmayy9cm/Premiere-AVS_1-5.7z/file

Also, maybe could load AVS into VDub2, and use VDub2 frame server [maybe it works, has fake AVI file I think],
also I think AvsUtil might have some frameserver capability.

Good luck [Premiere plug will not have any HBD, in fact probably Avs v2.58 only - Includes source code].

[mp3dom]

There's the updated version by pinterf (I think, unless this is something else):
https://github.com/pinterf/PremiereAVSPlugin/releases

[StainlessS]

Cheers mp3, thats v1.96, mine was v1.5 [I think, never actually used it - I tend to collect stuff].

[tormento]

There's the updated version by pinterf
Thanks!

No way to pipe to Media Encoder without Premiere as an intermediate?

[DTL]

There were a AVFS plugin to pismo file mount. It create virtual folder with virtual .avi file - it should be compatible with any file read software.
https://turtlewar.org/avfs/

[Alex_ander]

No way to pipe to Media Encoder without Premiere as an intermediate?

If there's still an interest, I've just tested the 1.96 updated version with Media Encoder CS4 which is 32 bit and has the same plugins folder as Premiere, with .prm import files. To be sure, I specified file type for my .avs (from Avisynth+) as 'Windows AVI' in MP's dropdown next to the imported file name, then successfully encoded it. After that I 'upgraded' Encore CS4 in the same way, and it imported my .avs as 'Video file' with 're-encode' suggestions.

In my previous testings it failed to work with CS6 components which are already 64 bit.

[DTL]

May be simply attempt to build x64 version ? The documents says it is require
The headers from the Premiere 6.5/Pro SDK placed in Source/premiere-headers (or somewhere in the include path)
Download SDK from https://www.adobe.com/devnet/premiere/sdk/cs3.html#

But current Adobe developer site only lists Premiere SDKs for download from CC2015 to CC2019 and 2022 and 2024. Where to get Premiere 6.5/Pro SDK ?

Some history site https://ppro-plugins.docsforadobe.dev/history.html lists
19 July 2002
Zac Lam & Bruce Bullis
Version 6.5

Is it required Premiere 6.5/Pro SDK ?

We have some AP 202x (with Media Encoders) in our company as new standard NLEs so it is easy to test something possible to build.

[Alex_ander]

I finally solved it for CS6 Media Encoder after downloading the 64 bit .prm file from this page (their archive also contains unnecessary additions for a test example):
https://www.cnblogs.com/nlsoft/p/8420349.html

It still took some tricks to make it work (I have Avisynth+ 32/64 installed). At first, only simple scripts with an .avi file got opened, while those with .d2v indexing were rejected by the Encoder - with an error message. It looked like the actual decoder had to be also 64 bit, so I forced loading the 64-bit DGDecode.dll, which is available in versions 2.0.0.7 and 3.0.0.0 of DGMPGDec. My current AVSp is 32-bit; since it uses a path to 32-bit Avisynth.dll, it shows an extra error message at loading a 64-bit plugin, so I had to test the script externally, in MPC HC player (it didn't complain at the plugin, but showed that the parameter CPU=0, generated by AVSp in the import line, must be removed). And then it started to work!

note: before putting the .prm file in the plugins/common folder, I removed ' x64' from the file name since there's a self-reference to the file name within it (what if it matters?)

[DTL]

"It looked like the actual decoder had to be also 64 bit, "

All executable modules for 64bit processing in a single process space must be 64bit compiled. So all plugins for AVS and AVS core binary and AVS to adobe plugin and adobe final encoding engine. To check scripts with 64bit plugins you simply use any 64bit loading application like VirtualDub AMD64 build or avspmod or MPC-HC player 64bit .exe.

The only way of mixing 32 and 64bit software in a single workflow may be using some 'pipes' via operating system or virtual file emulation and so on.

[Alex_ander]

Yes, I already came to this conclusion. Just never cared about 64-bit plugins until this specific case. Now I've just added the 64-bit version of AVSp for finding out if all the 64-bit dll's are in their places, before importing a script into CS6 Encore or Media Encoder.