ClipWhat is Rush?
Rush is ClipLogger's hosted batch reasoning service. The app prepares evidence, submits the batch, and brings the results back into the logging review workflow with their route recorded. It is useful when local hardware or model setup would hold up the work. Review the run disclosure, credit balance, and eligible clip list before submitting.
Why use Rush when the local engine is free?
Rush lets the batch use hosted reasoning capacity while your Mac remains available for other work. Local reasoning can fit an offline or controlled workflow; Rush can fit a deadline where hosted execution is worth paying for. Compare elapsed time, correction effort, and packet transfer on the same sample. Neither route makes ambiguous footage certain.
How fast is it, really?
Time includes preparation, upload, queueing, provider execution, and result retrieval. Source duration, evidence size, network conditions, and service load all affect it. Inspect Jobs and the per-clip result state. Current worker scheduling can add about a minute before processing starts; do not promise a fixed batch completion time.
What does it cost?
The submission disclosure is the place to inspect the batch count, credit requirement, balance, and eligibility before committing a run. Consult the current Pricing page for plan and pack terms. Avoid estimating a large job from an old screenshot or a training video's historical allowance.
What are the limits?
The app and server enforce the eligible batch size, clip or range duration, credit balance, and concurrent-job limits. Inspect exclusions and their reasons in the submission flow. Use a relevant supported range for long material rather than assuming the whole source file is eligible. A virtual clip has its own analysis scope.
What happens if clips fail, or I cancel?
Credits are reserved and settled against server-side outcomes. Cancelling can stop undispatched work while already-dispatched clips finish. Inspect both per-clip status and the final account settlement instead of assuming that closing the window cancels or refunds the batch. Preserve an error receipt if the result and balance appear inconsistent.
What plans and packs exist?
See Pricing for plans, monthly allowances and credit top-ups. Settings → Account shows your current plan and balance. Studio pools Rush credits across the team; it does not distribute local processing across several Macs.
When do I actually need to sign in?
Use sign-in for Rush and account-based features. Your own cloud API route also requires its paid entitlement. Basic local browsing and manual logging are separate from those services. Check the engine chooser and Account tab when a route is unavailable rather than assuming every installed key or model is eligible.
Can everyone on a team spend the credit pool?
Studio seats share a pooled balance, and viewer seats can see work but cannot spend. The server refuses viewer submissions, and the app hides the Rush option for viewers rather than offering a button that would fail.