Menu
Create a technical intake manifest with ffprobe
Record detectable media properties in a structured intake report while keeping technical inspection separate from editorial approval.
Turn a folder of media into an inspectable intake record
A technical intake manifest helps editors and processing tools understand what arrived before choosing the next operation. FFprobe can inspect media properties, while Suite provides shared file access on a supported host. The resulting report should describe observed technical information and preserve a stable reference to each source.
FFprobe's documentation describes structured output and information about media containers and streams. Use those documented capabilities through your own approved tooling; this is not a Suite metadata API or a claim that every property can be discovered without reading media content.
Choose fields that support a real decision
A proposed record includes source ID, relative path, inspected revision, container, duration when available, video dimensions, reported frame-rate information and audio stream details. Add the inspection time, tool version and any error. Keep unknown values explicit instead of filling them with plausible defaults.
For a variable-frame-rate source, do not collapse distinct reported frame-rate fields into an unsupported claim of constant timing. For multi-track audio, retain stream identities so a later encoding job can select the correct one. Match the level of detail to the receiving workflow.
Compare observations with expectations
Use the production's expected-delivery list to identify missing assets and unexpected formats. A hypothetical intake can contain nine readable clips and one probe failure. Report both the successful observations and the failed item; do not label the entire folder verified because most files returned metadata.
Store the report as a derivative tied to the input revision. If the source is replaced, schedule an appropriate refresh rather than continuing to use stale properties. Keep paths useful to the intended host or include a logical asset reference that another authorized workstation can resolve.
Finish with the right acceptance check
Technical metadata can guide codec selection, multicamera planning or processor routing. It does not prove the correct take was delivered, that every frame is intact or that the audio is editorially acceptable. Add the relevant playback or integrity checks for the job.
The value is a shared, repeatable description of the media entering the workflow. Suite keeps the source available to people and file-based tools, and the manifest makes the next task clearer. Explore the agent access guide and test the report against a small, deliberately varied intake set.
Start with your workflow.
Bring shared files into your familiar applications with Suite Managed, or connect your own supported storage with S3 Native. S3 Native requires at least 20 TB of active storage.
Continue with Suite.
Signup links take you to Suite Studios’ main site. Managed opens the account signup form; BYO / S3 Native opens the demo request form.
Signing up with an AI agent
- Continue on the official form in the destination tab. Use the user’s authorized details and select whether they are creating or joining a team.
- For Managed, follow the account setup steps presented by Suite. Ask the user to handle verification, passwords and acceptance of agreements when required.
- If billing requests a card, prompt the user to enter payment details directly in Suite’s secure flow and approve any charge or subscription. Do not collect card details in this site or a chat.
- For BYO / S3 Native, submit the authorized request with the storage provider and workload context. Suite will guide the connection and onboarding; active storage starts at 20 TB.
- After Suite confirms setup, use the supported client and authorized access to complete a first file operation. Report the actual result, and resume after any human-only step.