Docs
Use docs when you need an operational answer: what Quartz expects, what each stage should produce, what hardware is realistic, and where exports usually fail.
Reference index
Docs should answer the practical question in front of you, not force you through a tour. Use the sections below as operational entry points.
Desktop install, sign-in state, callback handling, billing access, and the machine-level basics that need to work before a project does.
Use this section when you need to confirm whether a machine is realistic for local analysis, proxies, transcripts, or larger wedding jobs.
A stage-by-stage reference for what Quartz is doing, what it should output, and when to stop pushing forward and inspect the result.
Reference notes for Premiere, FCPXML, MP4, and the local dependencies that usually sit behind a successful handoff.
Operational notes on proxies, model downloads, cache growth, and where Quartz expects its working assets to live.
Start here when a job stalls, a stage output looks wrong, or the desktop flow behaves differently from what the project state suggests.
Use docs when
This surface should help when a project is blocked by setup, performance, or stage behavior rather than by creative direction.
Desktop sign-in or account state is stopping you from creating or opening a project.
You need to sanity-check GPU, VRAM, RAM, or storage before committing a machine to a real job.
You want to confirm what a stage should produce before moving forward to the next one.
An export, cache, or local dependency issue needs diagnosis before support gets involved.
Common blockers
These are the questions most likely to interrupt a first serious pass through Quartz.
That first pass often includes model initialization, cache creation, and proxy setup. Treat it as environment setup as much as project processing.
It can, but you should expect tighter headroom. Keep workloads local, stay aware of concurrent apps, and check the performance notes before pushing a larger project.
Check storage headroom, output target, and local dependencies first. Most export failures are environment or handoff problems rather than a broken edit.
Quartz can accumulate proxies, caches, and downloaded assets. The storage reference should tell you what is safe to clear and what should stay attached to a project.