Use the source for the claim.
Our guides connect practical explanations to published standards, official manufacturer documentation and stated calculations. Numbered citations identify the claim they support; the source note names a section, heading or relevant scope. A source for a counting rule does not certify every example, calculator or workflow on the page.
Standards references identify an edition where relevant. A cited edition is not a promise that it is the latest or the edition required by your delivery contract. Camera and software behavior can depend on model, firmware and version. Check the linked documentation for your equipment.
Keep labels, frames and seconds separate.
A timecode label, a whole-frame count and elapsed seconds are different quantities. The site uses exact rational rates: 23.976 means 24000/1001, 29.97 means 30000/1001 and 59.94 means 60000/1001 frames per second. Decimal labels remain convenient shorthand.
The full-rate 59.94 tools count 00–59 in the frame field. That display convention does not specify LTC, SDI ancillary packets or every high-rate implementation. Signed-duration tools do not wrap after 24 hours; in/out tools ask explicitly about endpoints and crossing into the next day. The mathematics reference records these conventions.
Make the arithmetic reproducible.
Worked examples state their rate, count and endpoint assumptions. Our own equations and test examples are explanatory calculations, distinct from the source documents. For example, 1,800 frame periods at 30000/1001 fps last exactly 60.06 seconds. Changing DF/NDF labels does not change those pictures or that elapsed interval.
The downloadable validation examples include expected labels, whole-frame results, numerical tolerances and invalid inputs. Automated checks compare the website calculations with those expectations. They do not establish standards conformance or replace an independent check against the receiving system.
State what an estimate leaves out.
Film planning uses declared gauge, perforation format, nominal footage factors and reserve assumptions. Storage planning uses declared bitrates or pixel layouts, copies and allowances. Clock-drift bounds are a model of specified clock accuracy, not a measurement of a recorder or camera. Real media, clocks and production conditions can differ.
The guides and calculators do not inspect source files, resample audio, convert pictures, measure synchronization or certify a broadcast delivery. Use the standards map alongside the recipient’s specification and equipment documentation.
Carry the same assumptions across languages.
English, French, German and Spanish editions preserve technical identifiers, exact rate relationships and worked examples. Numeric input fields use the stated input convention; localized output formatting does not change the calculation. A translated reference label may still open the original-language source.
If wording or an example appears ambiguous, compare the rate, counting mode, units, endpoint convention and linked source before relying on the result. Keep the page URL, input settings and expected result when documenting a discrepancy. The support page explains the available product help.
Separate technical explanation from app promotion.
This library is published by DesignThink alongside Timecode Pro. Purchase links promote the separate Mac and iPhone/iPad apps. A manufacturer or standards citation supports the stated technical point; it does not imply endorsement of Timecode Pro.
Material corrections should update the explanation, affected examples and language editions together. Dates and author or reviewer credits should describe actual publication and review activity. The privacy policy explains optional website analytics and App Store campaign links.