Translators working on video delivery forms, broadcast QC reports or podcast production notes often meet LUFS, LKFS, dBTP and loudness range beside an ordinary instruction such as ‘make it louder’. Readers searching how to translate LUFS or audio true-peak specifications need a guide that keeps every unit attached to the property it measures. Integrated loudness is not a peak meter, and a delivery target is not the same as the loudness of the current file.
A broadcast sheet may require integrated programme loudness of −23 LUFS and a maximum true peak of −1 dBTP under EBU R 128. A version that says ‘the file has 23 decibels of volume and one decibel of headroom’ has discarded two crucial references, a minus sign and the distinction between a target and a ceiling. That wording can lead a sound engineer to adjust the wrong control or deliver a file that fails quality control.
This guide explains how to translate loudness metadata, measurement reports, target tolerances and handoff instructions with enough precision for a multilingual audio workflow. The examples concern the meaning of audio measurements and contracted delivery requirements; they do not impose one broadcast target on every streaming service or replace the recipient’s current technical delivery specification.
Quick answer: what this document actually says
Integrated loudness is a programme-level measure generally expressed in LUFS or LKFS within the relevant standard; loudness difference may be expressed in LU. Maximum true peak is expressed in dBTP, which is different from ordinary sample-peak dBFS. Loudness range (LRA) describes variations, not average loudness. The signed target, permitted ceiling, standard edition, time window and actual measurements must survive translation.
The translation problem before the first sentence
Technical translation succeeds when the target-language reader can make the same practical decision as the source-language reader. In broadcast, podcast and streaming audio loudness delivery sheets, a number without a defined property may look authoritative while answering the wrong question. First identify the object being measured, then the method, then the units, then any acceptance threshold. Resist the temptation to supply missing evidence because the prose sounds smoother after simplification.
A useful working file has two columns: the original technical expression and the proposed reader-facing interpretation. Add a third column for evidence that supports that interpretation. If the original says a sample was tested, keep ‘sample’; if it says a requirement must be met, keep the obligation; if it reports a target, do not turn it into an observation. These distinctions survive far more translations than a list of one-word equivalents.
The editorial hierarchy matters too. An illustrative calculation demonstrates a method, but it is not a replacement for the laboratory certificate, carrier tariff or contractual schedule governing a real transaction. Describe uncertainty honestly; cite the named standard or provider; and avoid universal claims in fields where a different test edition, application or delivery platform would produce a different answer.
A practical source-to-target verification workflow
- Preserve the original expression, every sign, code, unit and identifier before drafting an explanatory sentence.
- Identify the measured quantity and distinguish it from an estimate, a target, a threshold, a range and an observed result.
- Record the applicable method, edition, configuration, recipient and scope of evidence; do not silently modernise a cited standard.
- Translate the human-readable words while keeping technical identifiers stable unless the source explicitly supplies an authorised local equivalent.
- Test the translated sentence against a simple practical example and ask whether it would lead to the same decision as the original.
- Check all exclusions and conditions; have a suitably qualified reviewer examine consequential safety, billing or compliance claims.
Read the following cases as a decision practice rather than as a dictionary. Each begins with a plausible excerpt. The figures and situations are teaching examples unless attributed to an identified published rule. The purpose is to explain why apparently small language choices change the meaning of a real technical record.
Part I — Read the quantity and its units
1. Integrated LUFS target
Illustrative source situation. A delivery form requests −23 LUFS integrated. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. The negative signed figure is a full-programme loudness target using the applicable measurement algorithm. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Dropping the minus sign or treating 23 as a sound pressure level changes the requirement. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Target integrated programme loudness: −23 LUFS, measured under the specified standard. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Keep sign, decimal precision and reference standard. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
2. LKFS and LUFS notation
Illustrative source situation. An international broadcaster uses LKFS instead of LUFS. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Both notations appear in standards-based programme-loudness contexts, with definitions tied to the stated method. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Treating LKFS as a different unverified sound format can prompt unnecessary file conversion. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Keep LKFS as written, explain its loudness-measure role, and note any method equivalence carefully. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Check version of ITU-R BS.1770 and delivery contract. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
3. True peak dBTP
Illustrative source situation. A quality report gives maximum true peak −1 dBTP. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. This quantity describes an estimated reconstructed waveform peak, including between-sample behaviour. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Translating dBTP as an average loudness unit conceals a peak-limit problem. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Maximum permitted true-peak level: −1 dBTP for the stated delivery path. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Verify the meter method and whether the value is a limit or observed measurement. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
4. Sample peak dBFS
Illustrative source situation. A workstation displays sample peaks in dBFS. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Sample-peak indication reads the digital samples and can differ from oversampled true-peak measurements. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Assuming a −1 dBFS sample peak automatically passes a −1 dBTP specification is unsafe. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Label sample peak as sample peak, with dBFS, distinct from dBTP. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Run a true-peak meter when a true-peak ceiling is specified. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
5. Loudness Range LRA
Illustrative source situation. A QC report lists LRA of 8 LU. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Loudness range describes variation over time rather than the programme’s absolute loudness target. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Turning LRA into 8 LUFS of average loudness changes the quantity. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Loudness range: 8 LU as measured by the named method. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Check that LRA was measured over meaningful duration with the declared tool. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
6. Loudness Units LU
Illustrative source situation. A note asks for a reduction of 2 LU. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. An LU difference expresses a relative loudness change, not a new absolute integrated target. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Converting −23 LUFS minus 2 LU into an increase to −21 LUFS reverses the adjustment. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Reduce programme loudness by 2 LU relative to its starting measurement. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Compute the new value with the correct sign and check the resulting peaks. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
7. Momentary window
Illustrative source situation. A meter shows momentary loudness. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Momentary readings reflect a short measurement window and are not the same as programme integrated value. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. A brief loud moment cannot replace a whole-programme delivery measurement. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Momentary loudness reading, labelled by the meter’s time scale. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Confirm window definition and sample location when quoting readings. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
8. Short-term window
Illustrative source situation. A QC log shows short-term loudness during dialogue. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Short-term measurements describe a longer window than momentary readings but still not the full programme. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Writing ‘programme average’ for a short-term highlight misleads the recipient. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Short-term loudness for the specified interval, separate from integrated loudness. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Preserve time stamps and window length. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
9. Gating in integrated measurement
Illustrative source situation. A software tool reports gated integrated loudness. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. The standard’s gating method affects which portions influence the integrated result. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. A naive unweighted numerical average of readings does not reproduce the meter result. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Integrated loudness measured with the relevant standard gate and meter. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Identify the implementation rather than calculating averages from screenshots. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
Part II — Preserve boundaries, methods and conditions
10. EBU versus platform specification
Illustrative source situation. A podcast brief and a broadcaster’s R 128 brief differ. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Different distributors can impose different targets and measurement expectations. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Copying −23 LUFS into every streaming platform sheet creates a false universal rule. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Show each recipient’s explicit contracted loudness target and specification edition. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Check the current recipient sheet before normalisation. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
11. Ceiling is not target
Illustrative source situation. A specification says true peak shall not exceed −1 dBTP. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. This is an upper permitted bound, not an instruction to drive every programme exactly to the ceiling. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. A translation saying ‘adjust peak to −1 dBTP’ can push material unnecessarily close to a limit. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Maximum true peak must remain at or below the stated ceiling. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Distinguish maximum from preferred operating margin. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
12. Meter tolerance is not creative headroom
Illustrative source situation. A standard includes measurement tolerance language. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Permitted measurement uncertainty should not be sold as permission to exceed a hard deliverable target routinely. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. A loose rendering can turn a QC accommodation into a blanket production allowance. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. State the tolerance, applicability and measurement uncertainty in separate clauses. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Confirm whether tolerance concerns measurement, live operation or accepted delivery. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
13. Live versus prerecorded tolerance
Illustrative source situation. The document discusses practical limitations of live programmes. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Live workflows may have stated concessions that do not automatically apply to edited files. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Extending a live-only exception to prerecorded programmes changes contract meaning. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Indicate that the stated exception applies only where its conditions are met. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Verify live or file-based delivery class. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
14. Peak after transcoding
Illustrative source situation. A source WAV is encoded into a lossy format. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Encoding can alter reconstructed peak behaviour and trigger the destination platform’s checks. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Claiming a WAV’s true-peak reading guarantees every encoded derivative is unsound. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. State source-file measurement and separately verify encoded-delivery measurement. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Re-measure the actual delivered codec when required. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
15. Channel layout and loudness
Illustrative source situation. A project includes stereo and multichannel masters. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Channel configuration affects measurement context and must remain correctly identified. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Calling a 5.1 mix stereo or translating LFE labels incorrectly can corrupt delivery. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Specify channel layout and exact master version alongside loudness values. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Confirm channel map and measurement scope for each delivered file. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
16. Dialogue versus programme loudness
Illustrative source situation. A quality note separately discusses spoken dialogue. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Dialogue level can be a particular concern, but it is not automatically identical to overall integrated programme loudness. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. A translation that substitutes dialogue-only figures for whole-programme values confuses scopes. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Show dialogue measurements and integrated whole-programme measurements as separate items. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Check gating and measurement instructions in the contract. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
17. Silent leading sections
Illustrative source situation. A programme includes long silence and intermittent sound. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Meter gating and content distribution affect integrated loudness outcomes. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Adding silent samples does not reliably solve a loudness compliance problem. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Measure the entire intended programme under the specified method. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Review content edits as well as numerical readings. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
18. Short advertisement LRA
Illustrative source situation. A thirty-second advertisement is supplied. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. A brief duration can make loudness-range interpretation less useful or poorly supported. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Publishing a tiny LRA number as proof of attractive dynamics is unwarranted. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Treat LRA cautiously for short-form material and prioritise applicable delivery metrics. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Follow the relevant recipient’s short-form requirements. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
Part III — Produce a defensible reader-facing translation
19. Normalise versus measure
Illustrative source situation. The instruction says normalise to target rather than merely report. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Measuring a file does not by itself change the signal; normalisation requires processing or agreed metadata treatment. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. A translated checklist that marks measurement as completed normalisation can allow noncompliant delivery. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Separate ‘measured at’ from ‘processed to target’ in status language. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Verify export render and final QC report. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
20. Gain adjustment calculation
Illustrative source situation. A file measures −19 LUFS and target is −23 LUFS. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. A simple initial loudness correction is a reduction of about 4 LU, subject to metering and later processing. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. An instruction to add 4 dB would move the loudness in the wrong direction. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Reduce gain by roughly 4 dB as an initial correction, then remeasure. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Check final integrated level and true peaks after processing. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
21. Peak may require limiting
Illustrative source situation. A quiet file needs positive gain. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Boosting gain can raise true peaks, potentially violating a stated ceiling. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Translating the request as ‘increase level only’ omits a critical recheck. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Increase level toward the target, then verify true peak and apply appropriate limiting if required. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Do not assume compliance from integrated loudness alone. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
22. Negative numbers and decimal comma
Illustrative source situation. An overseas sheet prints −23,0 LUFS. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. The comma marks the decimal fraction in the source locale; the minus sign is essential. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. A careless locale conversion to 23.0 or −230 radically changes the requirement. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Render consistently as −23.0 LUFS in English-locale notation. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Double-check every sign and decimal separator visually. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
23. Loudness metadata
Illustrative source situation. A distribution file carries declared loudness metadata. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Metadata should reflect the actual programme loudness; a label alone is not proof of signal processing. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Changing metadata to the target while leaving a loud file unchanged is misleading. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Report actual measured loudness accurately and adjust programme audio where required. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Compare metadata values with independent QC measurement. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
24. Version of ITU-R method
Illustrative source situation. Two tools reference different standard revisions. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Algorithm versions and implementation settings can affect comparison details. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Silently upgrading a report’s cited method erases the basis of historical measurements. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Keep the stated ITU-R BS.1770 revision and instrument settings. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Record meter name, version and settings in handoff records. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
25. Revised mix and old QC
Illustrative source situation. A production team edits dialogue after QC. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. A new mix may have different integrated loudness and true peaks from the approved file. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. Reusing an old PDF as evidence of the revised export creates a traceability error. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. Identify the exact file revision whose measurements are reported. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Re-run QC on the final exported asset and compare checksums or IDs. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
26. Recipient-specific deliverables
Illustrative source situation. A distribution package contains an M&E mix and full mix. To translate this line reliably, start with the question the receiving reader must answer, not with a literal substitution for each noun. A code or unit is usually present because someone needs to calculate, compare, approve, reject, manufacture, deliver or verify something. Before rewriting it, identify whether the number is a measurement, a setting, an allowed limit or a statement about what did and did not happen.
What the expression means. Different deliverables can need separate loudness measurements and names. This distinction belongs in the translation even when the source is terse. A reader should not have to guess the physical quantity, the relevant object or the conditions that define the statement. When an explanation is needed, place it beside the preserved original code rather than pretending the explanation is itself the original evidence. A precise explanation can be conversational without becoming vague.
Where translations go wrong. A general ‘audio approved’ label hides which track passed which requirement. The damage often begins with an attractive simplification: a short phrase that appears easier to understand but changes an obligation, scope or reference. Look closely at qualifiers such as ‘tested’, ‘maximum’, ‘approximately’, ‘per’, ‘under’, ‘only’ and ‘subject to’. They are not decorative. If one disappears, the reader may act on a proposition that the source never supported.
Safer target-language rendering. State loudness results separately for each named delivered master. This is model explanatory wording, not an attempt to forge the issuer’s original certificate or to override a local regulator. Retain proper nouns, standard designations, identifiers and relevant units. Where target-language conventions reorder clauses, ensure that the qualification still modifies the correct claim. Then read the result aloud: does it tell an ordinary but careful reader exactly what they can infer, without giving them permission to infer more?
Verification before publication. Match filename, programme version, track layout and QC report. Also compare the source and target versions character by character for numerals, minus signs, decimal separators, inequality signs, superscripts and code punctuation. When circumstances call for an official or certified document translation, follow the relevant jurisdiction’s procedure. Technical interpretation is useful teaching, but authority belongs to the source documents and the accountable parties who issue, test or accept them.
Ten reader questions to answer before signing off
1. What is the reader searching for?
Usually an accurate interpretation of a particular value or identifier. Give that answer first, then show the narrower condition that makes it true. For broadcast, podcast and streaming audio loudness delivery sheets, this question should be resolved against the material that the translator actually possesses, not against a generic internet shorthand. Record any uncertainty so the next reader can see what was assumed and what remains to be checked.
2. Should a code be translated?
Generally preserve formal technical identifiers. Translate explanatory words around them and use an authorised equivalent only where it is explicitly documented. For broadcast, podcast and streaming audio loudness delivery sheets, this question should be resolved against the material that the translator actually possesses, not against a generic internet shorthand. Record any uncertainty so the next reader can see what was assumed and what remains to be checked.
3. Is a numerical conversion safe?
Only after identifying the original units and whether exact or approximate conversion is appropriate. Never manufacture precision. For broadcast, podcast and streaming audio loudness delivery sheets, this question should be resolved against the material that the translator actually possesses, not against a generic internet shorthand. Record any uncertainty so the next reader can see what was assumed and what remains to be checked.
4. What happens when the source omits a method?
Flag the missing method. An apparently familiar number may not support the same conclusion under another procedure. For broadcast, podcast and streaming audio loudness delivery sheets, this question should be resolved against the material that the translator actually possesses, not against a generic internet shorthand. Record any uncertainty so the next reader can see what was assumed and what remains to be checked.
5. Can a marketing summary replace a report?
No. It can help explain a result, but it does not extend the original test population, configuration or approval. For broadcast, podcast and streaming audio loudness delivery sheets, this question should be resolved against the material that the translator actually possesses, not against a generic internet shorthand. Record any uncertainty so the next reader can see what was assumed and what remains to be checked.
6. Does a higher figure always mean better performance?
No. Some scales have indirect numbering, ceilings, tolerances or non-comparable test methods. Interpret the defined quantity. For broadcast, podcast and streaming audio loudness delivery sheets, this question should be resolved against the material that the translator actually possesses, not against a generic internet shorthand. Record any uncertainty so the next reader can see what was assumed and what remains to be checked.
7. What if the translated sentence sounds awkward?
Improve its syntax while preserving every condition. Readability is valuable only when the underlying claim remains unchanged. For broadcast, podcast and streaming audio loudness delivery sheets, this question should be resolved against the material that the translator actually possesses, not against a generic internet shorthand. Record any uncertainty so the next reader can see what was assumed and what remains to be checked.
8. Can software produce a finished translation alone?
Software can help with drafting and consistency checks. Specialist review remains important when errors affect safety, finance or contractual compliance. For broadcast, podcast and streaming audio loudness delivery sheets, this question should be resolved against the material that the translator actually possesses, not against a generic internet shorthand. Record any uncertainty so the next reader can see what was assumed and what remains to be checked.
9. Which version should the reader trust?
Prefer the signed current source document for the exact transaction or project, with its report identifier and edition. For broadcast, podcast and streaming audio loudness delivery sheets, this question should be resolved against the material that the translator actually possesses, not against a generic internet shorthand. Record any uncertainty so the next reader can see what was assumed and what remains to be checked.
10. Where should broader vocabulary and language study continue?
Use the existing specialist pathways rather than allowing a narrowly focused technical guide to become a competing general translation hub. For broadcast, podcast and streaming audio loudness delivery sheets, this question should be resolved against the material that the translator actually possesses, not against a generic internet shorthand. Record any uncertainty so the next reader can see what was assumed and what remains to be checked.
A compact handoff checklist
A complete technical handoff should preserve the exact original phrase, the revised translation, a short meaning note, units, standards or recipient instructions, source document version, decision-relevant limits and a list of unresolved questions. Put examples in a visibly educational context. Do not quietly copy a teaching example into a commercial certificate, and do not let a plausible translation substitute for evidence that has not been supplied. Readers looking for a quick answer should be able to find it near the top; readers making expensive decisions should be able to follow the reasoning to its source.
Further reading and the existing language-learning ecosystem
This guide is one practical branch of the wider translation architecture. For general language comprehension, word meaning and precise English use, continue through eduKateSG Vocabulary and How English Works. Those existing resources remain the general owners; this article handles the specialised search question: how to translate LUFS, LKFS, true peak in dBTP, momentary loudness and loudness range without confusing loudness measurements with file formats or platform rules.
Technical and regulatory standards can be revised. The cited resources establish definitions and published context, not permission to ignore a current contractual specification. Check source dates, editions and local requirements before acting. This article is educational nonfiction and is not a certificate, approval, engineering assessment or substitute for professional review.