Vfile types
Video transfer
The copy of a video file, where codec, container, and size decide the door more than the word video does.
How it works
A review proxy may be 200 MB. A camera master may be 80 GB. Both are video. Email can take the proxy and will reject the master. Players tolerate some truncation and then desync audio. A hash is the completion test. A player that opens is not. Send the container you agreed, not a rewrap the other side did not ask for.
A 4.8 GB ProRes file is the delivery. The editor also makes a 180 MB H.264 proxy for notes. The proxy goes by link in minutes. The ProRes uses multipart and a six-hour window. Notes on the proxy are accepted only after the ProRes hash matches, so they are not approving a different encode.
How it differs
Video transfer is not streaming playback. Streaming can start before the file exists locally. Delivery means the recipient holds the file.
Variable frame rate from a phone breaks editorial tools after a clean copy. The transfer succeeded. The file contract did not.
Audio-only followers sometimes drop in a rewrap. State channel count in the delivery note.
On the ticket
- The practical close is a log line: time, actor, byte count, result.
- Without that line the transfer is a story.
- With it, the next person can see whether this door did what the ticket claimed.
- If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
Related
Sources
- RFC 9110, HTTP Semantics
Methods and status codes for the transfer