Timecode only works when everyone understands the frame rate behind it. A production at 23.976 fps, 24 fps, 25 fps, 29.97 fps, or 30 fps may display similar-looking timecode values, but those values do not always translate cleanly without the right project setting.
Why editors care about frame rate
Editorial teams are responsible for turning production information into decisions on a timeline. If a note arrives without frame rate context, the assistant editor may need to verify the project setup, inspect media metadata, and adjust by hand before the note becomes a reliable marker.
That extra work is avoidable. A production notes workflow should capture the frame rate at the project level and keep it attached to exported notes. The note text explains the issue; the frame rate helps place the issue correctly.
How to make frame rate explicit
Meta Note includes project frame rate controls because timing is a core part of the handoff. Crews can set the project rate before notes are captured, reducing ambiguity for post when notes become markers or review references.
Frame rate is not glamorous, but it is one of the small pieces of metadata that keeps production notes from becoming guesswork.