Closed wangqr closed 5 years ago
I've re-build the plugin with latest Pr plugin SDK. Debugger showed that some exception happened at PremiereFS.cpp#L58. I replaced the debug
function with a dummy one. Now it works fine.
If you can make a version of frame server that works correctly with Premiere CC without any weird workarounds then you can make a pull request and claim this 3+ year outstanding $100 bounty once it gets merged:
https://www.bountysource.com/issues/25095447-update-debugmode-frameserver-for-adobe-premiere-cc
Just throwing that out there in case you're interested :)
I do have a build that works on my PrPro CC 2019 @ Win10, at https://ftp.wangqr.tk/frame-server/, and source at wangqr/frame-server. I haven't tested it on the mentioned issues.
To use it, install the original 2.14 version without installing any plugin, and put the prm file into C:\Program Files\Adobe\Adobe Premiere Pro CC 2019\Plug-Ins\Common
I use your modify version .but in premiere cc 2019 v12.0, when video encoder read virtual avi file, report error?
I use your modify version .but in premiere cc 2019 v12.0, when video encoder read virtual avi file, report error?
What is the encoder you are using and what is the error you see? I'm using the AVI in AviSynth, which should work fine. There are some softwares which are not able to read the AVI directly and you may need to create an AviSynth script to load the AVI, for example ffmpeg
.
I do have a build that works on my PrPro CC 2019 @ Win10, at https://ftp.wangqr.tk/frame-server/, and source at wangqr/frame-server. I haven't tested it on the mentioned issues.
To use it, install the original 2.14 version without installing any plugin, and put the prm file into
C:\Program Files\Adobe\Adobe Premiere Pro CC 2019\Plug-Ins\Common
It works fine on CC 2019.
@dmirandaa @wangqr @albino1 I have an installer tested on Win7 64bit with the latest Premiere Elements. Can I request your help in trying it out? I'd like to verify if it works on Premiere Pro and on Windows 10 before releasing. You can email me at 'satish -at- debugmode.com' and I'll send the build/exe for testing.
Hi, sorry for the late reply.
Of course I can help you.
Please, let me know how to do it.
On Sat, 15 Jun 2019, 18:57 Satish Sampath, notifications@github.com wrote:
@dmirandaa https://github.com/dmirandaa @wangqr https://github.com/wangqr @albino1 https://github.com/albino1 I have an installer tested on Win7 64bit with the latest Premiere Elements. Can I request your help in trying it out? I'd like to verify if it works on Premiere Pro and on Windows 10 before releasing. You can email me at 'satish -at- debugmode.com' and I'll send the build/exe for testing.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/satishsampath/frame-server/issues/43?email_source=notifications&email_token=AAQXRTY3IERFZYVDVFRMCJDP2VQU5A5CNFSM4GPQJGH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXZA3FQ#issuecomment-502402454, or mute the thread https://github.com/notifications/unsubscribe-auth/AAQXRT27GT3IBJYAVXNUGMDP2VQU5ANCNFSM4GPQJGHQ .
This issue is fixed with the release of Frameserver 3.0 today. Get it at https://www.debugmode.com/frameserver/
Hmm, upgraded to 3.0 and now only exporting Green Frames from Premiere Pro CC 13.1.2 on Windows 10.
Update: DMFS is exporting solid green frames with YUY2 format selected, solid black frames with RGB24 selected.
There is no FrameServer export option in the export dialog. When premiere starts, a warning is shown in the "Events" panel:
Relevant parts in
Plugin Loading.log
:The plugin was working fine on Pr CC 2018 on the same machine.