Yes, that's one of the locations where production distribution works - the location isn't the problem.
I'm just looking to see if there's some feedback I can obtain from launching Premiere from the CL so I can determine something like an extension not loading because it can't find the files.
We never test following symlinks; PPro expects the actual files to be in the right location.
You can also turn up the log level, next to where you turned on the loading of debug panels:
The LogLevel key can be updated at the following location (The application should be restarted for the log level changes to take effect):
- Win: regedit > HKEY_CURRENT_USER/Software/Adobe/CSXS.6
- Mac: /Users/USERNAME/Library/Preferences/com.adobe.CSXS.6.plist
For example of Mac, in the terminal do:
defaults write com.adobe.CSXS.6 LogLevel 6
CEPHtmlEngine Logs
In CEP 6.1 and later releases, CEPHtmlEngine generates logs. Each CEPHtmlEngine instance usually genereate two log files, one for browser process, the other for renderer process.
These files are generated with the following naming conventions:
- Browser process: CEPHtmlEngine<versionNumber>-<HostID>-<HostVersion>-<ExtensionID>.log
- Renderer process: CEPHtmlEngine<versionNumber>-<HostID>-<HostVersion>-<ExtensionID>-renderer.log
For example:
- CEPHtmlEngine6-PHXS-16.0.0-com.adobe.DesignLibraries.angular.log
- CEPHtmlEngine6-PHXS-16.0.0-com.adobe.DesignLibraries.angular-renderer.log
They are also controlled by the PlugPlug log level.
CEF Log
In CEP 4.0 - 6.0, the Chromium Embedded Framework (CEF) in CEPHtmlEngine also generates a log:
- Win: C:\Users\USERNAME\AppData\Local\Temp\cef_debug.log
- Mac: /Users/USERNAME/Library/Logs/CSXS/cef_debug.log
In CEP 6.1 and later releases, this log is merged into CEPHtmlEngine log.
AdChoices