Problem with CEF/CEP Extension on another machine - buttons not responding, etc

New Here ,
Apr 18, 2022 Apr 18, 2022

Copy link to clipboard

Copied

I have an Adobe Premiere CEF extension I've written that works fine on my machine (and has been packaged and signed) but when run on someone else's machine (same version of adobe premiere, both on windows), it loads but doesn't respond at all to any buttons, and the extension panel is virtually unreadable and appears to be basically black text on dark gray background.

 

Anyone have any idea what's wrong and what these symptoms might mean?

TOPICS
Error or problem , SDK

Views

68

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

New Here , Apr 18, 2022 Apr 18, 2022
Hi Bruce,Thanks for the quick reply.To answer your questions, the extension was installed on the second machine using a signed vxp file.I have solved the mystery, and it was my fault.When testing the extensions on my local machine, I use hard links from the adobe extensions directory to my local development directory.The unresponsiveness of the extensions in the 2nd machine was due to javascript error on the extension page (it would be wonderful if adobe premiere could give us a log of such erro...

Likes

Translate

Translate
Adobe Employee ,
Apr 18, 2022 Apr 18, 2022

Copy link to clipboard

Copied

How was the extension installed, onto the second machine? 


Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 18, 2022 Apr 18, 2022

Copy link to clipboard

Copied

LATEST

Hi Bruce,

Thanks for the quick reply.

To answer your questions, the extension was installed on the second machine using a signed vxp file.

I have solved the mystery, and it was my fault.

When testing the extensions on my local machine, I use hard links from the adobe extensions directory to my local development directory.

The unresponsiveness of the extensions in the 2nd machine was due to javascript error on the extension page (it would be wonderful if adobe premiere could give us a log of such errors instead of silent error).

The ultimate cause turned out to be that when installing the extensions using vxp extension package, adobe was creating directory names based on the extension manifest file, which is very sensible, but my extensions were looking for each other (I know this is a weird thing to do but they do this for shared code purposes) using different directory names.

I should have tested it myself on my development machine and I would have caught the problem -- totally my fault.

All working well now (if anyone is curious here are the extensions on github: https://github.com/dcmouser/jrPremiere )

 

Thanks,

-jesse

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines