Closed albino1 closed 5 years ago
I went ahead and created a Bug Bounty for this project which you can find here:
It is possible to do multiple session rendering with the plugin, however, it is a pain:
Debugmode will then work again for another, single use.
Thanks for the workflow @jonno85uk, even if it's cumbersome I still appreciate it.
I have found that the plugin does not load on PrPro CC 2019 and made some small fixes to let it work (see https://github.com/satishsampath/frame-server/issues/43#issuecomment-453723267). With this build, I can export multiple times and save the project without problem, using the "Export" option in the Export dialog.
I don't have AME installed so I am not sure if "Queue" is working properly, and not able to reproduce the AME issue. I'll test the AME issue later if I have time.
This issue is fixed with the release of Frameserver 3.0 today. Get it at https://www.debugmode.com/frameserver/
What is it: Debugmode Frameserver is a plugin that acts as an intermediary between Adobe Premiere and other programs. Basically it allows the user to pass video files to third party encoders.
Where is it at now: The last update to Frameserver was 2.14 which added support for Adobe Premiere CS6.
What needs to be fixed: With the release of Adobe Premiere CC, Frameserver is able to run once, after which it fails to load. More importantly, Adobe Media Encoder appears to crash when launching and you may need to uninstall Frameserver to recover AME. Since it seems to work the first time it would appear that the basic functionality of Frameserver is still intact, though what happens next to cause it to fail is unknown.
Bug Bounty Goal: Improve the stability of Frameserver in Adobe Premiere CC to the point where you can render multiple files and close/re-open AME without incident.