Help Center

Each project in Developing Tank is an isolated workspace for a single show or production. Files, workflows, and team access are scoped to the project.

Setup checklist

1. Enter the project name using your show's working title.
2. Set the frame rate. This affects retime calculations and sequence processing.
3. Configure naming conventions if your show uses custom formats.
4. Set up marker rules.
5. Invite core team members with appropriate roles.

Naming convention notes

• The delimiter can be any character, but it must be consistent between scene, take, and camera values.
• Use the same delimiter for VFX shot names.

Marker rule notes

• Marker rules can auto-detect VFX shots, ADR notes, and online/optical notes.

Roles are project-scoped. A user can have different roles across projects. Roles control what a user can do.

Role definitions

Grant Admin only when the responsibility requires it. Admins can change other members' roles.

Project access is managed at the project level. Each person you invite receives an email link to join. You can invite existing users and users who do not yet have accounts.

How to invite someone

1. Open Project Settings.
2. Enter the collaborator's email address.
3. Assign a role (Viewer, Editor, or Admin).
4. Send the invitation.

The recipient must accept the invitation before they appear as an active project member.

Troubleshooting access issues

User received the invite but cannot access the project

• Confirm they opened the link while signed in to the correct account.
• Confirm the invitation was accepted, not only viewed.

Invitation is not showing up

• On next sign-in, the user should be prompted to accept or reject pending invitations.
• Ask the invitee to check spam/junk folders.

Error when sending invites

• Confirm you have the Admin role on that project.

This page covers the operational checklist for running dailies prep on a real project.

For background on automation behavior, see: How Dailies Automation Works.

Before you start

• Confirm project frame rate in Project Settings.
• Have your ALE, AVB, or AAF file ready from the day's transfer.
• Confirm naming conventions if your show uses custom formats.

Common issues

Clips are not grouping correctly

• Scene and take columns are prioritized before clip names.
• Verify scene/take values exist and are correct.
• Then verify clip naming format uses a consistent delimiter: scene<delimiter>take<delimiter>camera

Offspeed clips are not flagged

• Confirm project frame rate is set.
• Offspeed detection uses both cfps and trailing clip-name numbers.

Examples:

• 2C_04_A_120 — 120 fps
• 3A_1_D_48 — 48 fps
• 3A_1_D_47.97 — 47.976 fps

Sequence processing reads your cut and updates VFX tracking, scene tracking, and downstream reporting.

Accepted formats

• AAF (up to 100 MB)
• AVB (up to 50 MB)
• EDL (up to 5 MB)

EDL and AAF files must be uploaded one at a time and cannot be included in multi-file batch uploads.

Step-by-step

1. Ensure the sequence has no groups.
2. Open the Sequences page in your project.
3. Click Upload Sequence.
4. Select your AAF, AVB, or EDL file.
5. Click Process Sequence.
6. Review shot count, scene detections, marker detections, and duration.
7. Confirm downstream pages (VFX, Scenes) reflect expected updates.

Common issues

Sequence processed but VFX shots are empty

• Confirm your VFX naming convention is in use.
• If using markers, confirm marker rules are configured and used consistently.

Detected scenes are incorrect

• This can happen with intercutting, unusual scene length changes, or takes crossing scenes.
• Correct scenes manually. Subsequent uploads should reflect those corrections.

Upload rejected

• Confirm file type and size are within limits.
• If limits are valid, the sequence may be too complex and need simplification.
• See Upload Limits.

• All uploads in a batch must be of the same file type.

File size limits by type

Batch upload limits

• AAF: 50 files per batch
• Avid Bin (AVB): 5 files per batch
• CSV / ALE: 50 files per batch
• Maximum 145 MB total across all files in a single batch
• EDL files and AAF sequences must be uploaded one at a time — they cannot be included in a multi-file batch

When a file exceeds its limit, the upload is rejected with an error message showing the file size and the limit for that type.

If you hit a limit

• Reduce batch size — split a large batch into smaller runs
• For large AAF or AVB files, confirm the export settings are not including embedded media unnecessarily
• EDLs rarely exceed 5 MB unless something is wrong with the export; re-export from your NLE with a standard profile