Sample Rate and Frame Rate: Agreeing the Sound Workflow

Two rates with different jobs

Sample rate describes the number of audio samples recorded each second. Frame rate describes the number of picture frames per second, or the time base used by the relevant video system. These values interact within a workflow, but they are not the same measurement. Changing a camera’s frame rate is therefore not an automatic instruction to make an arbitrary change to the sound recorder’s sample rate.

Before filming, agree how material will be recorded, labelled, imported and delivered. Saying that a production is “for the internet” is not a sufficient technical specification. Online video still needs a consistent project and understandable metadata. Confirm the settings with the person responsible for editorial or technical finishing before the first proper scene is recorded.

Write exact values in full

23.976 and 24 fps are not identical, and neither are 29.97 and 30 fps. A rounded value in a production note can lead to incorrect interpretation. The agreement should identify the precise camera, sound and timecode settings, along with any intended speed changes. On a multi-camera production, confirm every camera configuration rather than checking only the main camera.

Distinguish the image capture rate from the way the material will play in the project. Slow-motion footage may serve a different purpose from ordinary synchronous dialogue. Sound needs to know which scenes require natural speech aligned with the image and which are intended only for a visual montage. Without that information, the recording requirements cannot be assessed properly.

Historical rules are not a project specification

Older advice based on PAL and NTSC divisions can explain historical workflows, but it should not automatically determine settings for a current project. Choose the actual values according to production and post-production requirements. If the project involves a speed conversion or another specialised process, document and test that step explicitly instead of inferring it from the country where filming takes place.

Use manufacturer documentation to establish how the equipment behaves. Recorders and cameras do not necessarily store or interpret every setting in the same way. The behaviour of the editing software matters as well. A value being available in a menu does not establish that it is appropriate for the particular editorial project and its finishing workflow.

Test the complete chain

Before a demanding shoot, record test pictures and sound with a synchronisation reference. Import them through the same process planned for the real material. Check alignment at the beginning and end of a longer take, and confirm that the required metadata survives. This catches problems before an entire day of material has been recorded with the wrong assumptions.

Keep the approved settings in a short technical note available to camera, sound and editorial. Record any changes during production and identify the affected files. If a requirement is unclear, ask for an explicit confirmation. In production sound, precise workflow communication matters as much as connecting a microphone correctly. It prevents avoidable corrective work from becoming a problem for the entire team later.

Make the technical note available when crew responsibilities change. A new assistant or replacement camera operator should not infer settings from a previous project. When uncertain, compare the note with the device’s current menu and inform the other departments. The document then becomes a practical continuity check rather than an attachment nobody opens after the preparation meeting.