Menu

Keep Requested, Measured, and Billable Video Duration Separate
📰

Keep Requested, Measured, and Billable Video Duration Separate

DEV Community: backend·TokenPeak·10 days ago
#yIWVLS46
#devtobackend#devto#dev#duration#frame
Reading 0:00
15s threshold

A Seedance brief asks for ten seconds. A local media inspection reports a duration slightly above ten seconds. A cost worksheet still contains the original request value. Which number should replace the others?

Usually none of them should be overwritten. Requested duration expresses intent; measured duration describes an observed media artifact; billable duration or usage follows the provider's charging contract. Treating them as one field destroys useful evidence.

Store values with their basis

A local record might contain requested_seconds , measured_stream_seconds , and billable_quantity , with the last field left unknown until supported by settlement evidence. These are application fields, not a Seedance response schema.

The measurement should also identify the artifact and the method. A container duration, a selected video stream duration, and a calculation from an assumed constant frame rate are different bases.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.