carvercat
Docs menu · Troubleshooting

Find the cause before repeating an action.

Keep the source safe, check current state, and report the smallest useful reproduction.

  1. Keep your work safe first.
  2. Start with the symptom.
  3. Saved output and uncertain sends.
  4. Make the problem reproducible.

Keep your work safe first.

If the app responds, Save As a separate copy and check that it reopens. Do not delete preferences, media or caches as a first step. A project depends on external media and fonts. Do not rely on crash recovery.

If an operation seems stuck, note what was happening and check render/proxy status before starting more work.

Start with the symptom.

SymptomFirst checks
Save failsRead the error; check the folder is writable; keep the original and try a new path
Missing mediaFind the original files; a proxy is not a substitute; keep a copy before relinking
Missing font or changed wrappingRefresh fonts; check the face, style, bounds and availability on the other machine
Controls fadedCheck selection, nesting, locks and lower promotion links
One edit changes several usesCheck whether you entered the shared source rather than an instance
Instance stops followingRevert its override; a matching typed value stays overridden
Unexpected motionCheck clip range, comp time, animation lanes and keys in between
Output is blockedRead the message about pending templates, slots, media or format
Wrong duration/transparencyCheck actual frame count, rate and alpha, and how the destination reads them
AI connected but no projectOpen the project in carvercat and start with a state read

Saved output and uncertain sends.

After a known failed send, retry with the unchanged saved output. If the outcome is unknown, check Resolve or After Effects before repeating; the clip or comp may already be there. After a restart, the old session’s send state does not carry over.

A resumed local render uses its original snapshot. Later edits do not change that render. Resuming a render is not the same as sending another clip.

Make the problem reproducible.

  • carvercat version and OS; GPU and driver if relevant.
  • Resolve (Free or Studio) or After Effects version, or AI client and version, if involved.
  • Minimal steps, expected result, actual result and the exact error.
  • A screenshot or recording with private details removed, and an optional non-confidential sample.
  • Whether saving, reopening and checking the destination worked.

Do not share passwords, full client configuration, customer media or personal paths. Avoid repeating uncertain writes to Resolve or After Effects just to make a report.