Zack Lovatt

I focus on toolkitting, building custom studio pipelines, expression rigging projects, and creating data-driven animation workflows.

Mail GitHub LinkedIn Skype Vimeo
October 3, 2016

CEP: Logging Errors

Posted In: extensions, scripting

When working on Flow, we were looking for a way to log standard JS console errors to a file, so that if something broke we’d be able to quickly diagnose the problem and fix it in a patch. Straightforward enough! However, as the CEP standard is evolving, we found that there was some discrepancy in behaviors between different versions of AE with respect to how to enable logging and where the log files are saved. With any luck, this can help.

The CEP documentation mentions that there are many Chromium Command Line Switches you can make use of in extensions; good place to start. I went through all of the logging options here to find out how these worked and what benefits they provided.

Flow currently uses CSXS 5.0, so this info may be not apply to other versions.

Simply, I found that just adding <Parameter>–v=0</Parameter> to your manifest was the best route, for a variety of reasons. Below you’ll see the what I’ve found by poking around the switches, and the behavior it provides between AE versions.

Log File Locations

The Switches

(No flags set) –enable-logging –v=X
Tagged: , , ,

Would you like to share your thoughts?

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.