Known issues
Open problems in Prism for After Effects, each with a workaround: snapshot comp switching, panel reconnection, long AI generations, AI-generated H.264 footage, transcription markers, and generated-image file paths.
Problems we know about, each with what to do in the meantime. If you hit something that is not here, the panel now reports it to us on its own — you do not need to file anything.
This list is honest rather than flattering. A problem you can see coming costs far less than one you discover halfway through a job.
Snapshots can change your active composition
Rendering a snapshot can leave a temporary render composition active, or leave the wrong comp selected afterwards.
After asking for snapshots, bring your intended comp forward before the next request. If a later request seems to act on the wrong comp, this is usually why.
Occasionally a snapshot returns a stale frame — the image from before your last edit. Ask for the snapshot again, or make any small change to force a fresh render.
The panel may not reconnect on its own
If the panel is reloaded, or After Effects is left idle for a long time, the connection can drop
and not come back by itself. Requests then fail with not-connected even though the panel looks
open.
Close and reopen the panel from Window → Extensions → After Effects MCP. If your AI client still cannot reach Prism, restart the client too — most clients only load their connections at startup.
The connection can also drop briefly during heavy work. A request that was in flight when it dropped is usually still running inside After Effects and often completes. Ask your AI to check for recent results rather than re-running the work — repeating it can produce duplicate layers.
Long AI generations can lose their result
Transparent image generation and music generation can take several minutes. On some connections the stream drops before the result arrives.
The generation itself does not stop, and it usually completes. Do not re-run it — that costs a second generation. Ask your AI to check for recent results instead; completed work is reported there.
Generated images are placed from a temporary folder
An image Prism generates is linked from a temporary location. If your system clears that folder, the footage goes offline and the project shows it as missing.
After generating images you want to keep, collect the files into your project folder and relink them there before closing the project.
Take care when relinking generated stills: choosing the wrong dialog option in After Effects can interpret a single image as a sequence and damage other footage in the project.
AI-generated video may render black
Some H.264 files produced by AI video generators decode incorrectly in After Effects — the layer renders black or empty with no error anywhere.
If a generated video appears black, convert it to ProRes or another editing codec before importing.
Transcription places sentence markers
Word-level transcription is the goal; some transcriptions still produce markers at sentence boundaries rather than per word.
If you need word-level timing, say so explicitly in your request and check the marker spacing before building on it.
Billing counts failed calls
A request that fails still counts toward your monthly usage. We know this is wrong and it is being fixed.
If failures have consumed a meaningful part of your allowance, email support@oneprism.io and our support team will sort it out.
Windows is less proven than macOS
Prism runs on both, but every issue found and fixed so far was found on macOS. Windows has had far less real-world use.
If something behaves differently on Windows, it is worth reporting even if it seems small.
Related
- Prism cannot reach After Effects: when every request fails.
- When Prism rejects your script: scripts refused before they run.
- After Effects quirks: behaviours of After Effects itself.