Custom video collection

Video data collection for AI, filmed to spec with per-participant consent

Commission video recordings built for a training run: talking-head and conversational footage, facial expression and gesture sets, liveness and anti-spoofing sequences, and in-cabin captures. Participants are recruited and filmed to your camera, lighting, and coverage plan, with consent documented per participant.

Free sample: Describe the footage you need: scenario, camera setup, and the model it will train. The team prepares a matching example and sends it manually within 48 hours, free of charge.

Collection specification

Capture
1080p to 4K at an agreed frame rate, single or multi-camera, with synchronized audio when the use needs it
Scenarios
Talking-head and dialogue footage, expression and gesture sets, liveness sequences, in-cabin and device-held recordings
Coverage
Participants recruited to demographic, pose, lighting, distance, and device targets
Metadata
Participant, session, device, lighting, pose, and approved-use fields keyed to every clip
Rights
Likeness, biometric, and AI-training consent signed per participant before filming
Status
Custom collection; footage is recorded to order, and catalogue rights are never assumed to cover a new use
Pricing
Custom, scoped to your conditions

What each kind of video team actually commissions

Avatar and lip-sync teams commission talking-head footage: framed faces, clean audio sync, and enough speakers, lighting setups, and cameras that a generated head does not inherit one studio's look. Audiovisual speech recognition teams want the same faces in worse conditions, because the visual stream earns its keep where the microphone struggles. Emotion teams commission facial expression data across elicited and spontaneous states, with the capture plan and label taxonomy designed together so the footage and its expression labels are specified as one deliverable.

Liveness and anti-spoofing buyers need genuine presentations recorded on the phone cameras their KYC flow will actually meet, alongside scripted attack material. Driver and occupant monitoring teams need in-cabin footage across seating positions, eyewear, and light that runs from noon glare to near darkness. The spec sheets differ, but a human video dataset stands or falls on the same operation underneath: recruit the right people, film to the sheet, check every clip.

Consent is what a scraped face dataset cannot retrofit

A face on video is biometric-adjacent data: the footage identifies a person whether or not your model cares who they are, and under the GDPR biometric data used for identification sits in the special categories. Several widely used public face datasets have been withdrawn after scrutiny of where their images came from, because permission that was never collected cannot be added later. Whatever license text accompanies a scraped set, the people in the frames were not asked about model training.

Commissioning face data collection inverts that. Every participant signs likeness, biometric, and AI-training language that names the intended use before the camera rolls, and the signed record travels with the delivery. Spirelight runs the same recruitment, consent, and QA operation for video that it built for speech collection, so the rights review happens at scoping rather than after a due-diligence question.

What arrives is a dataset, not a drive of files

What separates video data collection services is rarely the camera; it is what arrives at the end. Spirelight delivers a custom video dataset structured for a training pipeline: every clip keyed to a manifest entry with participant, session, device, lighting, pose, and approved-use fields, in a schema agreed before the first session. Annotation, from bounding boxes to expression labels, can be layered onto the same clips so footage and labels never drift apart.

Video datasets for machine learning fail on unglamorous defects, so QA checks for them per clip: face visibility and framing, focus and exposure, audio sync wherever the spec includes sound, and metadata completeness. Clips that fail are reshot under the same consent rather than patched in post. The check runs before delivery, so what arrives is the dataset rather than a snag list.

This offer is not the right fit when

  • You want to scrape public faces or license footage of people who were never asked about model training.
  • You need footage this week; recruited and consented capture is scoped and scheduled, not pulled from stock.
  • Your target model use cannot be stated plainly in a consent form.

Get a free sample

  1. Your details
  2. Your project
  3. Verify

Three short steps. The team then follows up manually within 48 hours, and confirms volume, rights, QA, and delivery if you want the scope priced.

Would rather talk it through first? Scope a video collection

Prepare the brief

Bring a specification your vendors can price consistently

Use the free worksheet to define coverage, rights, delivery fields, held-out rules, and acceptance tests before requesting a collection plan.

Build a dataset specification

Buyer documentation

Specimen data card and provenance structure, evaluation brief template, and acceptance and held-out questions.

Related services

Guides for this decision

Need a scoped collection plan? Send the language, channel, volume, annotation, and timing you know. The quote form opens directly in project-brief mode.