Closed mcardeiro closed 5 years ago
@mcardeiro which sample did you try to use?
PProPanel
On Tuesday, March 19, 2019, 11:24:10 AM EDT, dkstevekwak notifications@github.com wrote:
@mcardeiro which sample did you try to use?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
@mcardeiro have you followed the instructions noted in https://github.com/Adobe-CEP/Samples/blob/master/PProPanel/ReadMe.md? especially step #2 and #3. Also, if you enable debugging by following the fourth step, you should be able to debug further
I did everything but step 4. Just did step 4, tried opening panel (didnt open). went to browser and typed localhost: 7777 and got a file can't be reached error.
On Tuesday, March 19, 2019, 11:32:45 AM EDT, dkstevekwak <notifications@github.com> wrote:
@mcardeiro have you followed the instructions noted in https://github.com/Adobe-CEP/Samples/blob/master/PProPanel/ReadMe.md? especially step #2 and #3. Also, if you enable debugging by following the fourth step, you should be able to debug further
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
If the extension appears in the menu but cannot be opened, then the loading of debug panels (PlayerDebugMode) has not been enabled for this version of PPro.
Try enabling PlayerDebugMode for both CSXS.8 (PPro 11 and 12), and CSXS.9 (PPro 13).
just enabled for CSXS.8, restarted premiere and tried to launch panel and...same, nothing happens On Tuesday, March 19, 2019, 1:57:10 PM EDT, Bruce Bullis notifications@github.com wrote:
If the extension appears in the menu but cannot be opened, then the loading of debug panels (PlayerDebugMode) has not been enabled for this version of PPro.
Try enabling PlayerDebugMode for both CSXS.8 (PPro 11 and 12), and CSXS.9 (PPro 13).
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
Different versions of Chrome can cause problems. Which browser are you using?
That's odd; send me the panel? [day job address = b b b at adobe dot com]
Hello, I'm having the same issue. Adobe Premiere Pro 2018 (12.0), followed the instructions as well. nothing happens when the sample is invoked via (Premiere Pro) Window > Extensions > PProPanel (SDK Sample Panel).
Also, I'm using Chrome Version 73.0.3683.86 (Official Build) (64-bit)
I'll update if I get mine working. Thanks!
Behavior when PlayerDebugMode isn't set = The sample appears on the menu but does nothing when invoked. jmatt04, have you restarted the system since setting PlayerDebugMode, for CSXS.8?
I got it working! Here's what I did. I tried restarting the system, it didn't work. I then updated my Premiere to 12.1. Still it didn't work. I then tried using the 12.1 sample as I've updated the Premiere, and still it didn't work. I then deleted the registry entry for PlayerDebugMode and created a new one. basically the same. For some reason it did work lol. I think what made it work was redoing the PlayerDebugMode step. Thanks!
Glad you got it sorted! Hadn't heard of Windows ignoring a registry entry, before...
I've never heard a registry entry being ignored either. Glad the sample is working for you now. Closing the issue
Submit an issue
Note: issues submitted on this repo should be related to the samples contained within. If you have a general question about CEP, ExtendScript, or related topics, please visit the Extensions development forum.
Topic
This is an issue regarding:
Versions
8.x+
for this repo]:Description of the issue
Proposed solution or attempted solutions that failed