I'm trying to port my Transmitter plugin to Windows, but most of the external libraries I use are related to MinGW, making them incompatible with the MSVC build system. I have then decided to rebuild the project from scratch with a GNU compiler and without using the template, generating a .dll library. I have added the right source files and linked the right dynamic libraries, none of which are missing when checking with the Dependencies tool, but when launching Premiere pro, my plugin is apparently unable to be loaded and so ignored. I was wondering if I might have been missing some steps, like configuring the manifest file, or explicitely defining the entrty point.
here are my project configuration CMake files
Sorry, we have zero experience with build systems other than Visual Studio / XCode.
There are many tricks to get plug-ins to load. I too am building a Transmitter plugin.
I assume you the the Premiere SDK manual.
There is a log file you should look at:
C:\Users\YourUserNameHere\AppData\Roaming\Adobe\Premiere Pro\23.0\Plugin Loading.log
Yours should be there but the path might be slightly different.
I assume that you are using the latest Premiere.
Look at the end of the file for your info.
You need to put the plugin here:
or whatever you named it dot prm.
All required DLL's must go in the Premiere directory:
"C:\Program Files\Adobe\Adobe Premiere Pro 2023"
There is a loading conflict with FFmpeg DLL's. Premiere loads them first so they are not available to you and your plug-in fails to load.
You need to use FFmpeg 6.0 "Von Neumann" and not the vcpkg release.
you should use avformat-60.dll as Premiere hogs loading avformat-59.dll
You get the idea.
the Plugin log file has been pretty unhelpful in general
this is the only information I have about the loading
(if I build libWindowsLib (not the best name I know), I just get message : The library could not be loaded, so no real difference)
Also I've been able to build and load using MSVC and the template sln with all the my actual code, so I don't think it's an issue with dll and package versions.
thank you for the consideration
> I've been able to build and load using MSVC and the template sln with all the my actual code
Given your success with the recommended dev environment, what's your motivation for continuing to use an unsupported dev environment?
I am currently integrating a custom library relying on minGW which isn't compatible with MSVC into the transmitter, but I can make it work by compiling my library through MSVC. Problem is that it involves jumping through many hoops which will hinder integration and automation in the long run, so I would much prefer being able to integrate my MinGw library as is