FAQ: Everything About Avid Dailies Automation and VFX Tracking
This FAQ covers the most common questions from assistant editors, VFX editors, producers, and picture editors considering Developing Tank for post-production automation. Browse by topic or search for your specific question. If you don't find an answer, reach out - we're happy to help.
Developing Tank is post-production automation software for assistant editors, VFX editors, producers, and editorial teams. It reads Avid files and sequence data to automate repetitive work like dailies prep, VFX shot tracking, pull lists, continuity reports, and tracker updates.
No. Developing Tank uses deterministic automation and professional scripting, not generative AI. Your data is handled with logic, not guesses.
Developing Tank supports common Avid editorial files including AVB, AAF, EDL, and ALE. File support varies by workflow, so the upload page will show which formats are accepted for each task.
Upload supported Avid files from the day. Developing Tank can build scene bins, organize clips, prepare groups, apply offspeed retimes, and populate report data from the metadata already in your project.
Yes. It detects offspeed material such as 48, 72, 96, and 120 fps clips, calculates the required retime for the project frame rate, and prepares the material for editorial review.
Developing Tank reads the latest uploaded sequence, identifies configured VFX markers, compares the cut against prior uploads, flags frame-count changes, remembers deleted markers, and keeps the shot tracker current.
Yes. Developing Tank flags shots that are new, extended, shortened, deleted, or otherwise changed between sequence uploads so the team can review differences before sending vendors updated pulls.
Yes. Selected shots can be exported as pull packages with handles, including EDL, AVB, CSV, and PDF outputs depending on the workflow.
Yes. VFX and tracking data can sync with Google Sheets so producers, coordinators, and vendors can review familiar sheets while the database remains the source of truth.
Yes. Project collaborators can be invited with access levels such as viewer, editor, or admin, depending on what they need to review or change.
Post-production automation uses software to remove repetitive manual tasks such as file parsing, metadata entry, report generation, retime calculations, and tracker updates while leaving creative decisions to the editorial team.
The public tools are free to use. Full project automation is currently limited while pricing and early access are being finalized.
Paid plans are being shaped during the beta period. Early users will be told clearly before pricing changes apply.
Uploaded files are used only for the workflow you request and are not sold or shared with third parties. You keep ownership of your production data.
The most common causes are unsupported file exports, missing metadata, file corruption, or a workflow-specific format mismatch. Try exporting again from Avid and confirm the upload page accepts that file type.
Spreadsheets and FileMaker can store tracking data, but they still rely on manual updates. Developing Tank reads the sequence and updates the tracker from the editorial source files.