v0.145.4Internal beta docs
OverviewDocsForge tools

Beta documentation · eXLib v0.145.4. Public release is pending.

Sending Debug Logs

When eXLib support asks you for logs, this is the whole procedure.

The workflow

  1. Open Settings → Companion and turn on Debug logging (Verbose panel & companion logs).
  2. Reproduce the exact steps that trigger the problem.
  3. Click Export debug bundle. The button reads Exporting…, then the panel reports "Saved to your Desktop" with the full path.
  4. Send that file. Add the build stamp from Settings → About to your message — the line in the form version · short git SHA · build date — so the report maps to an exact build.
  5. Turn Debug logging back off when you're done. It's off by default and only needed while you're reproducing something.

Turning it off doesn't lose the basics — real errors and warnings are always recorded, on or off. What Debug logging adds is the finer detail (per-event traces, per-operation timings) that pins down something intermittent or hard to reproduce. Turn it on, reproduce the problem, then export — the bundle only ever contains what already happened by the time you click Export.

What's in the bundle

Export debug bundle writes one text file to your Desktop — exlib-debug-<version>-<date>-<time>.txt. Inside is the panel's own log and the native companion's log, each with their previous-generation backup if one exists, behind a short header naming your eXLib version and build, the companion's version, your host (After Effects version, OS), and current preferences. Attach that one file; it's everything support needs to line up a timeline of what happened.

The two logs it collects are panel.log (the panel) and aegp.log (the companion). Both live in eXLib's support folder — ~/Library/Application Support/eXLib on macOS, %APPDATA%\eXLib on Windows — each keeping one rotated older copy. You don't normally need to open them: the export collects them for you.

Privacy and what to review

The logging code is designed to record structure — event kinds, counts, timings, versions, internal match names, and error codes — rather than expression source. Every panel log line also redacts the account-name portion of a home-directory path: for example, /Users/alex/Documents/Rig.aep becomes ~/Documents/Rig.aep.

That is not anonymity. Folder and file names after ~ remain, and filesystem or host errors can include item names or other context supplied by After Effects. The companion log has its own producers, and the exported bundle cannot prove that every future error message contains structure only. Open the text bundle and review it before sending it to support; remove any line you do not want to share.