Your China production partner delivers a polished luggage film. The zipper opens, the handle extends and the wheels roll away. For the next campaign cut, your team removes the handle shot. Can the editor remove that sound while keeping the approved zipper and wheel performance intact?
That is a useful procurement question as AI makes it easier to explore several sound events in one generation. The relevant purchase is the amount of independent control your next edit will actually need.
One prompt can contain several future revision requests
ElevenLabs' SFX v3 announcement, published October 29, 2026 and updated October 30, describes generating multiple sounds from one prompt. Its November 2 developer guide recommends listing events in their intended sequence and using short, concrete prompts for individual sounds.
Those are vendor descriptions of a particular model. ONCE has not run a comparative generation test. Our production inference is that easier scene-level exploration makes the eventual editing arrangement more consequential. A successful preview establishes a creative direction; the delivered assets establish what another team can change.
An effects stem separated from dialogue and music can still contain every product action mixed together. Where sounds overlap, cutting out a handle click may also cut the zipper's decay. If the source layers are unavailable, the suitability of later separation work needs assessment. A file labelled “SFX” does not resolve that question.
ONCE's event change map
Before requesting more files, list the revisions you reasonably expect. For each revision, identify the sounds that must remain unchanged. Use that relationship to set the asset granularity.
| Likely revision | Control to preserve | Handover to demonstrate |
|---|---|---|
| A retailer cut removes the handle shot | Approved zipper and wheels remain | Remove the handle event independently |
| A new SKU uses another wheel assembly | The rest of the sequence remains | Replace the wheel asset at its picture position |
| A one-off atmospheric transition stays intact | Only overall timing and level change | A mixed clip may meet the brief |
This luggage example is hypothetical. Actual operating sounds require a check against the product; generated effects do not establish noise levels, durability or mechanical feedback. Recording, licensed libraries and generation are alternative production inputs, subject to the brief and usage rights.
The map does not require every sound to become a separate deliverable. A background that will always move with its scene can remain grouped. A component sound that will change between SKUs deserves independent control. Describe the expected edit to your product video production team before agreeing the handover scope.
Pay for flexibility where the expected work supports it
Ask for the additional preparation cost of event-level assets over a mixed delivery. Compare it with the sum, across plausible revision scenarios, of each scenario's probability multiplied by the total revision cost that the extra control could avoid.
Include candidate replacement, synchronization, mixing and review in that revision cost. Keep mutually exclusive scenarios separate so the same rework is not counted twice. When probabilities are uncertain, compare low-change, planned-change and high-change cases instead of inventing a precise percentage.
A locked, single-use film may justify a mixed sequence. A product family with scheduled component and cutdown changes may justify selected independent assets. Additional organization and quality checks also cost money. More stems alone are not a savings claim.
Accept the handover by making one expected change
Have the receiving editor perform an agreed revision using the delivered materials. Remove the handle event, for example, and check that the zipper tail and wheel entrance survive at their intended picture positions. Then listen with dialogue and music restored. Opening the project and seeing named tracks is only the first step.
Record any dependency on a plugin, online model or originating account. Retain the approved audio files, picture positions, usage scope and an asset index. Prompts and model details are useful supporting records; a future generation still needs review against the approved creative.
For an ongoing ONCE content service, the reusable asset is an approved sound with a known application and an understood editing limit. Recording the actual changes and reuse would allow a future margin assessment. No saving or client result is claimed here.
Sources checked November 8, 2026. The event change map and cost comparison are ONCE's proposed procurement methods. The original AI-generated cover is a conceptual illustration.
