Troubleshooting
Most of these aren’t faults — they’re Mixture doing something deliberate that isn’t obvious from the outside. Grouped by what you’d actually notice.
The editor won’t open
Section titled “The editor won’t open”“Your browser is missing…”
Mixture probes for four capabilities — WebGPU, WebCodecs video decoding, and H.264 and AAC encoding — and refuses to open rather than half-work. Use Chrome or Edge on a desktop or laptop; recent Safari and Firefox pass too. Phones and touch-only tablets aren’t supported.
There’s a Continue anyway escape hatch, but what breaks past it is exactly what the list said would break. See Browser support.
Something looks wrong on the canvas
Section titled “Something looks wrong on the canvas”My filters have disappeared
Almost always the browser. If you clicked past the capability check on a browser without WebGPU, layers render without their filters rather than failing outright. Open the project in Chrome and they’ll be there.
The whole device went soft and grey
A depth-of-field filter on a 3D shot with very little actual depth. On a near-frontal device the whole thing sits in a thin slice of depth, so the focus swings violently and quantises into mottling. Use tilt shift instead, or tilt the device more. See depth-aware effects.
My layer is blurry and nothing is moving
A manual motion blur mode. Radial zoom, horizontal, vertical and diagonal apply a constant smear whether or not anything moves. Switch the mode to Auto, which derives blur from real motion and is zero when the layer is still. See motion blur and its modes.
The Mode dropdown says “Radial zoom” but it looks like real motion blur
A known display bug: on a motion blur you haven’t explicitly set a mode on, the panel shows Radial zoom while the canvas correctly renders Auto. The render is right. Set the mode explicitly to be sure which one you’re on.
My shape snapped back to its original form mid-animation
A chained morph whose source shape wasn’t set. Every morph after the first has to define its own source, or it starts from the layer’s original path. See chaining morphs.
My morph target renders tiny
Mismatched coordinate scale between the two endpoint shapes — they share one fixed frame for the whole scene. Author both at the same scale.
My text lost its clipping inside a 3D scene
Masks don’t apply inside the 3D bake. Pre-compose the masked content outside the 3D scene and place the result as the item.
Video behaves oddly
Section titled “Video behaves oddly”“Optimising source files” with a progress count
Mixture is building a one-time, editing-optimised copy of a recording so cuts can land on any frame. It runs in your browser, nothing is uploaded, and you can keep working while it goes. Exports always use your originals. It happens once per recording and is cached for future sessions. What it’s doing, and why.
My cut didn’t apply to the other camera angle
The clips probably aren’t linked. Linked media shares edits across every angle from one take; unlinked clips are independent.
Holds aren’t doing anything
Holds don’t yet combine with cuts or speed blocks on the same clip. When both are present, the holds win and the cut regions are ignored.
Export
Section titled “Export”My export came out smaller than my composition
Your device couldn’t encode at full size, so Mixture stepped down to the largest size it can encode and said so in the dialog. Your project keeps its real dimensions — exporting later from a more capable machine produces the full-resolution file.
An agent’s export came out silent
Headless renders need real Chrome. Bundled test builds of Chromium lack the AAC audio encoder, so audio comes out empty.
Agents
Section titled “Agents”My agent can’t see my project
The agent signs in as you the first time it connects, and from then on it can list every project on your account. If it can’t find one, check it’s looking in the right workspace — it can list those too, and projects live in exactly one.
The agent said it was done but the frames are wrong
Ask it “what would you improve about this frame?” Agents are held to a frame-check pass, and the fix for a named issue is an edit — not a list. See Make it look good.
The agent reported filters as broken
If a still render says filters weren’t applied, that’s the rendering context lacking WebGPU, not a fault in the document. Filters should be verified on a WebGPU-capable path.
Saving and workspaces
Section titled “Saving and workspaces”“This project just moved to another workspace” / “the project or workspace was deleted”
Something you’re editing moved out from under you — usually a teammate moved or deleted it while your tab was open. Mixture refuses the write rather than saving your changes into a workspace you’re no longer editing in. Reload and find the project in its new home.
If you see this and nobody moved or deleted anything, that’s worth reporting — it means a check is too strict.
I deleted something by mistake
Deleted projects and workspaces enter a 30-day window before a background sweep purges them. Within that window recovery is possible; after it, the data is gone.
Still stuck? The Discord community is the fastest route to us during early access.