Music and sound design

Music generation, scoring, Foley, ambience, stems and mixing

• articleHow do sound designers use point-of-view and off-screen sound to tell the story, with what concrete techniques, and where does it stop working?
  Thom's 2000 interview on What Lies Beneath is the densest account: POV sequences give sound its widest licence; keep dialogue sparse; use visual conditions (water, mist, darkness) as the door to subjective sound; filter real sounds (underwater muffle) rather than add many; keep ambiguity by making voices unintelligible; and do not call attention to the sound design. Rydstrom adds an unlocated-sound principle for horror, Weis a voice-before-image menace technique, Holman off-screen events written into scripts. These are practitioners' stated rules, not tested findings.
• articleWhat are the building blocks of a film soundtrack (dialogue/ADR, effects, backgrounds, Foley, walla, music) and what does each department actually produce before the mix?
  Two first-person-heavy sources (Weis 1995 with practitioner interviews; Thom 2000 interview) and two short glossary/textbook excerpts give a working vocabulary: dialogue and ADR are cleaned or re-performed production speech; effects tracks are built from scratch from library, new recordings or combinations; Foley is effects performed to picture (footsteps, cloth, props); walla is a prepared, improvised crowd murmur; a typical final mix groups these as separate elements. The term 'hard effects' does not occur in any page read, so this batch gives no source-based definition of hard effects versus backgrounds beyond the separate 'backgrounds' element in Weis's track layout.
• articleHow do the audio-capable world-model papers measure that sound stays in sync with actions, camera motion and events, and what do they leave unmeasured?
  Three different measurement designs exist. AVWM compares the audio-energy vs motion-energy cross-correlation lag and peak of generated audio with that of ground-truth audio against the true visual trajectory (simulator data, 0.15 s steps); HelixBench (1,015 clips) scores DeSync on an Event subset and a Grounding-DINO-based three-region stereo score for camera-aligned panning; MaineCoon reports an unexplained "AV-Al" column where it is behind Ovi. Each protocol scores windows or short rollouts; none of the texts read measures the delay from a user action to the sound onset.
• articleHow do I shorten or lengthen a music cue to fit picture and join it cleanly: which crossfade shape, which grid, and what do music editors say about re-cutting for picture changes?
  The open DAW documentation gives concrete crossfade and grid facts: Ardour's constant-power crossfade (-3 dB each at the midpoint) is the splice for uncorrelated material, linear (-6 dB each) for highly-correlated signals, symmetric for editing two entire music works together, default fades are short de-clickers; the musical grid (bar, beat divisions) scales with tempo while timecode grids do not. Music editors add that cues are repeatedly lengthened, shortened or reworked as picture changes. No inspected primary source states a rule that cuts should land at phrase boundaries or downbeats; that rule appears only as a synthesis (cut on bar lines of a tempo-mapped grid and crossfade across the join) and in secondary search results not fetched.
• articleWhat is a temp track, what is 'temp love', and what does a music editor actually do from temp dub to cue sheet?
  Two music editors describe the same sequence: a temp dub of existing music for previews (no licensing needed), a spotting session with director/editor/composer, cue-by-cue notes with IN/OUT points and director comments, scoring, stems for the final dub, and a music cue sheet listing every cue. Carlson (about forty years in the business) defines 'temp love' as the director or producer falling in love with what they first heard and not wanting it changed. The union page read only lists 'Music Editor' as a classification; the role descriptions come from the two practitioner interviews, one on a single film (The Greatest Showman) and one about a career.
• articleWhy does a compressor distort, and which attack, lookahead and release choices does a manual say reduce overshoot and distortion (and when should I use a limiter instead)?
  Audacity's development manual explains with reported test-tone measurements that compression is waveshape modification, so it distorts; zero smoothing hard-clips; attack lets the signal overshoot; distortion spreads to every component in the mix; and lookahead/release only help when longer than the period of the lowest-frequency component above threshold. Its examples (1 kHz tone with bursts, -20 dB threshold) show lookahead 10 ms / attack 1 ms / release 10 ms reducing overshoot, and limiter-like 1 ms lookahead / 0 attack / 25 ms release allowing 10 dB more level without clipping. The scope is synthetic tones, not speech.
• articleWhat does a music editor deliver to the dub stage (track grouping, cue sheet, sync check), and what happens to the music there?
  The same TV music editor (S5, S6) integrates the recorded cues into the editing session, checks sync, sends the session to the dub stage and prepares a hand-drawn-style dubbing cue sheet "road map". Cues are grouped onto MUSIC-A to MUSIC-D track groups so overlapping cues sit on separate faders (34 music faders in his example). At the dub, dialogue is described as king, music is fitted around it, producers take notes in a final playback and the editors make fixes; mixers then make the 5.1 and stereo masters, an M&E and a DME master. Music-editor deliverables and dub practice here are from one US animated series in 2011.
• articleWhat must be prepared for the recording session itself: click and count-off choices, recording order, tempo notation, and what composers hand to orchestrators?
  A music editor (S4, S5) checks that fixed elements sit at the right timecode in a Pro Tools template and records cues in an order driven by player count under a three-hour union minimum. A studio conductor (S9, S11) decides free-click counts (four below 85 bpm, eight above), asks for eighth-note clicks at slow tempos with motor rhythms, marks tempo changes as relative bpm and treats the printed tempo as a guide because the Pro Tools tempo map and timecode are the official references. An orchestrator (S10) lists composer deliverables as MIDI file, full mix and stems, and sends back a new tempo map if tempos are retimed.
• articleWhen do modern scoring sessions record to a click, when do they free-time with streamers and punches, and what does each choice cost?
  A Los Angeles studio conductor (S8, blog posted 2013, modified 2025) says about 99 percent of his work is on click, that free timing with streamers and punches is rare and impractical for most modern film scores (mixed pre-records, spread-out orchestra, hard to edit takes together), and that he often just follows the Pro Tools counter. A Phaedrus Audio web page (S12) describes the click as indispensable for long fast cues with many hits but mechanical for rubato, and streamers and punches as a way to keep sync on a hit while leaving tempo to the conductor. A TV music editor (S5) says most cues are scored to a click.
• articleWhich scoring/DAW tools have a documented way to map picture hit points to tempo, how do their mechanisms differ, and at which dated versions was this observed?
  Vendor documentation observed on 2026-10-22 describes three different mechanisms. Dorico 2.2 (Nov 2018 version history) lets you flag "important" timecode-locked markers and searches one tempo for the flow so those markers fall near beats, and dragging a marker alters the preceding tempo. Logic Pro for Mac 12.3 (page metadata) adjusts the selected tempo points leading up to a hit point so audio aligns. Sibelius 2018.4 stores named hit points that move with the score and leaves tempo adjustment to a Fit Selection to Time plug-in. A 2024 practitioner article (Dorico 5.1.21, Sibelius 2024.3 era) and a 2017 composer account (Digital Performer) confirm the same ideas from use.
• articleHow do I turn a hit point (a timecode I must land on) into a tempo and a click, and how close does the landing need to be?
  Tempo times beats equals seconds: the editor (S3) and the Phaedrus Audio page (S12) both reduce hit placement to arithmetic, and S12 gives a worked click-book example in which 80 BPM misses a hit at 34 s by a quarter or half second but 81.13 BPM (17-6 frames per beat at 24 fps) lands it. S12 states a sync tolerance of two film frames (about 41 ms) with a rule of thumb of 0.1 s. A composer (S7) finds a rough tempo by tapping, then uses a software Find Tempo search over a tempo range. The arithmetic in S12 was re-checked by a batch-local script (consistent within rounding).
• articleWhat is a spotting session in film/TV scoring, who attends, and what written output (cue list with timecodes and reasons) should it produce?
  Two first-person practitioner accounts (a long-serving TV music editor, 2011; a film composer, 2017) describe spotting as a viewing-and-discussion step that decides where each cue starts, where it ends and why it exists, then produces timecoded notes for the composer. The music editor logs exact start/stop timecodes against a locked-length picture; the composer places start, end, hit and descriptive markers in the DAW. Both accounts come from one US animation-TV pipeline and one composer-teacher, so attendance and tooling differ in features and for other territories.
• articleWhat do Google's Gemini API pages say about ownership, marking and limits of Lyria 3.5 music output?
  For Lyria 3.5 via the Gemini API, the docs say all generated audio carries a SynthID watermark and that prompts requesting specific artist voices or copyrighted lyrics are blocked. The Gemini API Additional Terms (effective March 23, 2026) say Google won't claim ownership of generated content and may generate similar content for others. The pages read give no training-data statement for Lyria and no music-specific commercial-use tiers; the DeepMind page lists artist partnerships but no licensing detail.
• articleWhat do Udio's current terms allow for music made on the service, and what did it publicly report about label deals?
  At the Terms page observed 2026-10-22 (labelled Last Revised Nov 12, 2025), Udio forbids downloading Output, limits Output use to personal non-commercial purposes, and states that the company or its licensors own Output. Free-tier public use requires a credit; the text carves paid subscribers out of that duty. Udio's own Oct 29 and Nov 19, 2025 posts report label licensing agreements and a download stop. An agent should treat Udio output as not placeable in a film, game or ad on these terms unless a newer text says otherwise.
• articleCan I put a Suno-generated song in a film, game or ad, and what do Suno's terms say about ownership, plan tier and downloads?
  At the Terms version effective Sept 3, 2026, Suno assigns its rights in Output to Pro and Premier subscribers but warrants no copyright will vest; Free/Basic Output is limited to personal non-commercial use. Commercial exploitation additionally depends on a permitted Download within the tier's monthly allocation, and Suno's fingerprint, watermark or metadata may not be stripped. Training other models on Output is prohibited. The Terms and the help page describe ownership in different words, so an agent should record which text and date it relied on.
• articleWhen I name a sound-effects file under UCS, which of CatID, FXName, CreatorID, SourceID, UserCategory, VendorCategory and UserData must I provide, and which are optional?
  The only secondary text found that reproduces the operative filename wording is a vendor page (JamSoft SampleSort support), which says two things: the basic structure 'requires at least four blocks' (CatID_FXName_CreatorID_SourceID), and in its conclusion that the only requirement is a valid CatID at the head with the rest 'completely optional'. UserCategory, VendorCategory and UserData are the three optional blocks. The official document itself could not be retrieved (candidate -01), so this answer is a secondary reading and carries an unresolved internal tension.
• articleHow do pansori jangdan (rhythmic cycles) and jo (modes) correspond to mood and scene function, how reliable is that mapping, and what pacing technique can an audio or screen storyteller take from it without pretending to have a pansori drummer?
  Sources describe a toolkit of rhythmic cycles from very slow (jinyang, 24 beats) to urgent and agitated (jajinmori) and cheerful (jungjungmori), chosen to follow mood and context, plus modes (ujo, pyeongjo, gyemyeonjo) defined by sentiment and ornament rather than by pitch set alone. The translated music-theory article shows the mapping from cycle to mode is conventional but contested: the same scene has been labelled ujo or pyeongjo depending on the theorist, and slow and medium cycles mix ujo and pyeongjo features. A screen or audio storyteller can borrow the idea of a deliberate tempo-and-mood plan per scene while treating the specific mappings as one tradition's conventions.
• articleWhat is the difference between a synchronisation (sync) right and a master-use right, and who do public sources say you ask for each when a film, TV programme or online video uses an existing recording?
  Four public sources (PRS for Music, the UK IPO, CBC's producer handbook, the US Copyright Office) describe two layers for an existing recording: the composition (sync, usually publishers) and the specific recording (master, usually the label or recording owner). PRS and CBC both say you may need both and that the exact recording matters. The sources differ in jurisdiction and purpose, and none gives a legal conclusion for a particular cut.
• articleWho is expected to file the cue sheet, to whom, and by when, according to ASCAP, SOCAN, MCPS/PRS and a broadcaster's delivery guide?
  All four pages put the main filing duty on the production company (producer). They differ on routes: ASCAP accepts sheets from production companies or networks and treats member submissions as acceptable only if substantiated; SOCAN calls the producer's sheet authoritative but, in a 2023 FAQ, actively encourages members to submit too; MCPS asks producers using its TV licences to send the sheet to PRS for Music's TV licensing team, with broadcaster forms possible; CBC's series guide makes the producer file with SOCAN and confirm to CBC. ASCAP gives dated quarterly submission deadlines and a three-months-after-broadcast recommendation.
• articleWhat do open sources say about sound in horror (silence before a stinger, loud sudden sound) and how strong is that evidence?
  The open evidence is thin and mostly qualitative: a 2022 Edinburgh PhD thesis (self-watching plus three focus groups, 22 participants) reports that a loud sound after silence can trigger a brief fear reaction, and participants say they feared sudden silence because genre experience taught them a shock follows. A 2026 opinion article stresses that lab startle research uses probe tones, so it says little about film stingers. A 2023 BU student thesis reports music as a large tension contributor, but only its abstract was read.
• articleWhat do practitioners say a sound editor must do to prepare tracks before the mix (separation, premixes, scratch mixes, M&E), and what goes wrong when they do not?
  Craft-side preparation, as distinct from delivery specs: split dialogue by mic angle; keep families on separate tracks and premix them into manageable elements; have the major effects and clean-ups ready by the first scratch mix; record the full soundscape under dialogue so an M&E exists; decide with the composer, scene by scene, whether music or effects leads. Documented failures include sketches frozen by a director's liking for the scratch mix, a composer/effects logjam in the final mix, and a live-performance compromise (Philadelphia) that left dialogue and aria on one track.
• articleHow do I duck music under dialogue (sidechain or automatic ducking), what parameter values do open manuals state, and what do practitioners do instead of lowering all the music?
  Three mechanisms are documented: an offline effect keyed from a control track (Audacity Auto Duck: -12 dB, 0.5 s fades, 1 s maximum pause, -30 dB RMS threshold), a sidechained compressor (ReaComp auxiliary detector, Ardour a-Compressor sidechain; OBS gives 32:1, -36 dB, 100 ms attack, 600 ms release as a starting point for streaming), and an inverted sidechained gate (ReaGate). A feature-film practitioner account adds a third strategy: deliver music as stems and nudge only the competing stem (a loud horn) down a few dB at the dub so the whole score is not dipped. No inspected source validates specific ducking values for film dialogue.
• articleWhat techniques and failure modes for thematic association (leitmotif) follow from Wagner's writings and Wolzogen's thematic guide, does the 'one motif per character' rule hold, and how might it be used for film, games or series?
  Wagner's texts do not state 'one motif per character'. He describes themes tied to dominant moods and to the 'weightiest motives' of the drama, kept few and recurring: a fresh motive for each recurrence of the same mood would be the opera-composer's habit he rejects; motives are re-modelled to fit the passing situation (Lohengrin versus the more literal reminiscences of the Flying Dutchman); a motive's first presentation must be justified by the scene; harsh combinations should be softened by tempo and dynamic. Wolzogen's guide names motives after objects, relations and states (Ring, Compact, Renunciation, Walhalla, Captivating Love, Wondrous Power of the golden apples) as well as persons, and notes Alberich acquires his motive only later. A 1920 photoplay manual (Lang & West) shows the same technique in film: a main love theme reused in minor mode, quickened, fragmented, agitated.
• articleHow does the ARSC Guide to Audio Preservation separate a preservation transfer from restoration, and what does it say about disc speed and equalisation?
  The ARSC Guide to Audio Preservation (CLIR 2015, CC BY-NC-SA 4.0, credited photos excluded) separates preservation from restoration. A preservation transfer reproduces the carrier accurately with aligned machines, the correct stylus and equalization or other decoding as needed. Subjective clean-up is restoration, done only after a preservation copy exists. It defines a preservation master, an access master (which may be restored, e.g. de-noised) and an access copy, and names BWF .wav the de facto archival format. Many '78 rpm' discs should really be played at slightly different speeds (e.g. 76 or 79 rpm), so turntables need incremental speed control.
• articleWhat do EBU R 128 s1, s2, s3, s4, Tech 3343, Tech 3344 and (if available) AES TD1004 add beyond R 128 for production and streaming distribution?
  The EBU R 128 family as read in October 2026: R 128 V5 (November 2023) is the base. Supplement s1 (August 2020) sets short-form content (ads, promos) at -23.0 LUFS with short-term loudness no higher than -18.0 LUFS and true peak no higher than -1 dBTP, and says loudness range isn't useful for short-form. Supplement s2 (November 2023) keeps streams at -23.0 LUFS, or an interim distribution level of -20 to -16 LUFS when the broadcaster does the dynamic treatment, citing AES 71 and AES 77. Tech 3343 V4 (November 2023) folds in the streaming, radio and cinematic supplements, and Tech 3344 v2.1 (July 2016) covers distribution and reproduction.
• articleWhat is the EBU SQAM test material, what does it contain, and what use does the EBU allow?
  The EBU SQAM CD (handbook Tech 3253, September 2008) is a set of recordings for subjective sound-quality tests, grouped from alignment and artificial signals through single instruments, voice, speech, orchestra and pop (70 tracks). The handbook states no licence. The EBU's generic test-sequence terms forbid commercial use and redistribution, and the producer's reading of the SQAM download page says downloading means agreeing to R&D-only use.
• articleFrom which date must a provider of an AI audio system mark its outputs under AI Act Article 50(2), what does Article 113 now say after the Digital Omnibus, and where is the official text?
  Under the EU AI Act as amended by the Digital Omnibus on AI (Regulation (EU) 2026/1744, OJ 24 July 2026), the Act applies from 2 August 2026, and a new Article 111(4) gives existing systems a grace period. Providers of systems generating synthetic audio, image, video or text that were on the market before 2 August 2026 must comply with the Article 50(2) machine-readable marking duty by 2 December 2026. Article 50 paragraphs 1-6 are unchanged; paragraph 7 (codes of practice) was replaced. How the dates apply to a given system is a legal question this record does not answer.
• articleWhat room-acoustic and listening-level numbers do EBU Tech 3276 and ITU-R BS.1116-3 state for a reference listening room, and what are they scoped for?
  EBU Tech 3276 (2nd ed., 1998) and ITU-R BS.1116-3 (2015) set the same room targets. Average reverberation time is Tm = 0.25 x (V / 100 m3)^(1/3) seconds (BS.1116-3 measures it over 200 Hz-4 kHz). Early reflections in the first 15 ms should be at least 10 dB below the direct sound between 1 and 8 kHz. Background noise should preferably stay at NR 10 and never exceed NR 15, with -18 dBFS alignment. They differ on listening level: Tech 3276 uses 85 - 10 log(n) dB(A) for n channels, BS.1116-3 uses 78 +/- 0.25 dBA. Both are for assessment and reference listening rooms, not mix-room certification.
• articleWhat do the REW help pages say about what room measurements and EQ can and cannot fix, and what RT60 target they give for a small mixing room?
  REW's help says room EQ is valid only at the measured position. EQ can tame response peaks, especially low ones, but not deep narrow dips, which are position-sensitive and need headroom EQ doesn't have. A 1/3-octave RTA is too coarse to see those dips. In domestic-size rooms RT60 isn't meaningful below a few hundred Hz (modal behaviour, no diffuse field). Recommended RT60 is about 0.3 s under 50 m3 and 0.4-0.6 s up to 200 m3. C50 indicates speech clarity and C80 music clarity. REW's room simulator treats every source as omnidirectional.
• articleBeyond first order, what do the ambix converter, Spatial_Audio_Framework (SPARTA) and IEM Plug-in Suite code define for FuMa support, N3D/SN3D gains and channel order?
  Tools disagree on how far FuMa goes, so a higher-order FuMa file converts differently depending on the tool. The ambix converter has real FuMa-to-SN3D gains through 3rd order (W x sqrt 2; 2nd-order 0.866 except the centre 1.0; 3rd-order 0.791/0.745/0.843/1.0). Its table continues to 10th order, but every entry above 3rd order is 1.0 (placeholders, not FuMa definitions). The Spatial Audio Framework (used by SPARTA) supports FuMa at first order only and zeroes higher channels. IEM's plug-in header has only SN3D<->N3D factors (sqrt 3, sqrt 5, ... per order) and no FuMa. ambix converters older than v0.2.6 (April 2016) used a different FuMa W scaling.
• articleWhat fields does the CISAC AVR+ cue-sheet schema (Global Cue Sheet Standard 2.0 implementation) define for productions, cues, works, recordings and shares?
  CISAC's AVR+ (announced 18 June 2026) is a JSON Schema (draft 2020-12, schema version 1.0) for audiovisual music cue sheets, implementing the Global Cue Sheet Standard 2.0. A sheet needs production, cue and cue-sheet sections. Each cue needs a title (or an 'unknown title' flag), duration, usage code and type code. A cue may also carry in/out times, a work block (ISWC, society work codes, per-territory shares by interested party, role and right type) and a recording block (ISRC, artists, label, product codes, master owner). Usage codes are B Background, U Bumper, C Closing Theme, F Featured/Visual, L Logo, O Opening Theme and S Segment Theme; type codes are I Instrumental and V Vocal. The documentation prose mentions 'Jingle' and 'Source', which are not enum values, so the schema enums govern.
• articleWhat does Netflix's 'Dolby Atmos Home Mix Archive Specs' say about archive files, naming and metadata for an Atmos home mix?
  The Atmos requirements page specifies the archive print master as a Dolby Atmos BWAV ADM file (any bed configuration), with DME separation and group labelling deferred to Netflix's BWAV ADM Creation Guidelines. It gives no Atmos-specific filename pattern or ADM metadata table, so naming must come from the asset-naming page and those guidelines.
• articleWhat do LUFS, LKFS, LU, dBFS and dBTP mean, and how do they relate?
  LKFS (ITU-R BS.1770) and LUFS (EBU R 128) are the same absolute unit, K-weighted loudness relative to full scale, and track level dB for dB. LU is the relative form (1 LU = 1 dB), used for differences such as distance from target or loudness range. dBFS is level relative to digital full scale. dBTP is a true-peak level estimated by oversampling (at least 192 kHz) to catch peaks between samples; R 128 caps production true peak at -1 dBTP. Loudness describes average perceived level, true peak describes clipping risk.
• articleWhat public documentation exists for Dolby Atmos ADM BWF masters (container, limits, pairing rules), and who publishes it?
  The only Dolby Atmos master rules readable here are a distributor's: Prime Video requires ADM BWF in a BWF-RF64 .wav (codec DOLBY-ATMOS-ADMBWF), 24-bit 48 kHz LPCM, at most 128 tracks, 118 objects and 10 beds, a matching-locale non-Atmos source with a 5.1 mix, and no M&E, MOS, silent or commentary tracks in the Atmos source. Dolby's own ADM profile PDF could not be reached by producer or curator.
• articleOverview: from the set recorder to the delivered package, which carrier holds which kind of information at each audio handoff, and where does the timing or metadata thin out?
  Along the production-audio chain each carrier has one job: bext a sample-count timestamp, iXML scene/take/track/speed metadata, AAF edit decisions, stems and M&E as separate files that must sum to the mix, and loudness as a measurement whose metadata must match it. Foley handoff had no primary document in the producer's sources (gap).
• articleWhat does Ogg Opus (RFC 7845) preserve about sample rate, start offset, loudness and channel order compared with WAV or FLAC?
  In Ogg Opus (RFC 7845) the stored input sample rate is informational only (decode at 48 kHz), playback position subtracts pre-skip, the header carries an output gain, mapping family 1 uses Vorbis channel order that differs from WAVE and FLAC (permute channels), and loudness normalisation uses R128_TRACK_GAIN/R128_ALBUM_GAIN tags rather than REPLAYGAIN tags.
• articleHow do the engines' docs and source treat sample rate conversion, mix rate and frame-rate divisibility when recording or exporting cinematic audio?
  Godot's docs say the Movie Maker mix rate must divide by the FPS, but the code only warns and sizes each frame's audio block with integer division. At 44.1 kHz and 24 fps that is 1837 instead of 1837.5 samples per frame: 12 samples (about 0.27 ms) lost per second, about 16 ms per minute (curator arithmetic). The 48 kHz default divides evenly at 24/25/30/60 fps. FPS is an integer, so 23.976/29.97 need external retiming.
• articleWhat do Godot, Unity and Unreal audio docs say about keeping an in-engine mix from clipping and about loudness targets?
  Engine docs cover peak safety, not loudness: Godot's hard limiter defaults to a -0.3 dB ceiling and the (soft-clip) limiter to -0.1 dB, so 'add a limiter to Master' does not fix which behaviour you get; no engine page read gives a loudness target or meter, so delivery to a LUFS spec needs external measurement of the exported file.
• articleHow do I get the audio of an in-engine cinematic out as a file in Godot and Unreal, and what format and sample rate will it be?
  Godot Movie Maker records audio non-real-time at a 48 kHz default; the PNG writer writes a stereo WAV whose header declares format code 1 (integer PCM) at 32 bits per sample, while OGV/AVI embed audio. Unreal MRQ WAV parameters are not stated in the pages the producer read.
• articleWhat does the enrolled Tennessee Public Chapter 588 (ELVIS Act) say about voice, simulated voice, tools and the fair-use list?
  The enrolled ELVIS Act (effective 2024-07-01) contains the narrowed tool clause ('a particular, identifiable individual's ... voice, or likeness, with knowledge'), the voice-includes-simulation definition, the First Amendment fair-use list and the 'reasonably should have known' standard; it confirms that the House amendment wording read in CA-B194 is the enacted text.
• articleWhich Apple Music delivery page states a loudness or true-peak limit, and which audio does it apply to?
  For music deliverables, the Asset Guide 5.3.19 gives numeric limits only for immersive audio (Dolby Atmos BWF ADM and 5.1/7.1 LPCM .mov: integrated loudness not above -18 LKFS and true peak not above -1 dB TP per BS.1770-4); stereo and Apple Digital Masters sections give no numeric peak/loudness limit, only an encode-clipping audition rule tied to the Apple Digital Master badge. Applying the immersive numbers to stereo masters is not supported by the guide.
• articleWhat do the MEI Board stylesheets and MEI MIDI module document about converting between MusicXML and MEI, and which data do the stylesheet defaults discard?
  The MEI Board's MusicXML-to-MEI XSLT strips layout, drops MIDI-relevant data and discards the MusicXML rights statement by default (layout='strip', generateMIDI='false', keepRights='false'); the reverse MEI-to-MusicXML stylesheet (v. 0.2) writes the old MusicXML 2.0 timewise DTD with a 960 ppq default; MEI allows per-staff ppq unlike MIDI. The tools are under the Educational Community License. Code reading; no loss table exists.
• articleWhat does a public studio delivery specification say about handing off Foley (cue sheets, track naming/layout, stems)?
  Netflix's nonfiction M&E guide treats Foley as an optional, often unbudgeted pass cued at the sound or post supervisor's discretion (cloth and props first, footsteps rarely), with married music, effects and separate dialogue stems when there is no Foley; its sound-mix spec v1.6 lists Foley as a labelled object/bed group and expects Foley fill in the 5.1 M&E. No public Netflix text read gives a Foley cue-sheet format or track layout.
• articleWhat does AES TD1008 say about true-peak limiting, codec overshoot and sample-rate conversion when preparing masters for lossy streaming?
  AES TD1008 (2021, superseding TD1004) recommends at most -1 dBTP at the input of lossy codecs (high-rate coders around 256 kbps may tolerate -0.5 dBTP), a true-peak limiter as the last element before the codec, and notes downward SRC can create overshoots a limiter placed before it cannot catch; its distribution table targets speech at -18 LUFS (+1 LU), track-normalised music at -16 LUFS and album-loudest tracks at -14 LUFS (+0.2 LU).
• articleWhat does Apple Digital Masters (formerly Mastered for iTunes) ask a mastering engineer to deliver and check for AAC streaming: bit depth, sample rate, headroom, SRC and clipping?
  Apple's Digital Masters brief asks for 24-bit sources at the highest native rate (no upsampling or bit-padding), describes mastering-quality SRC to a floating-point intermediate before AAC encoding, recommends at least 1 dB headroom because playback oversampling and encoding can clip material that shows no PCM overs (checked with afclip), and says one master feeds both AAC and ALAC. It gives no dBTP or LUFS target.
• articleHow does the MusicBrainz schema relate recordings, works, ISRC, ISWC and credits, under what data licences, and what minimal field set would an agent need to attribute a music cue correctly?
  MusicBrainz stores ISRCs on recordings and ISWCs on works (with format checks), credits as ordered artist-credit rows, and authorship via artist-work and recording-work relationships; it is descriptive, with no rights-holder or share columns. Core data is CC0 and supplementary data CC BY-NC-SA. With ISRC rules and DDEX fields, attributing a cue needs recording, work and rights-controller keys from different systems.
• articleWhich DDEX ERN 4.3.x elements carry credits, rights controllers, territory/use scope and AI-contribution flags for a sound recording, what did ERN 4.3 lack, and under what licence is the standard offered?
  DDEX ERN 4.3.2 models recording credits and rights with Contributor (role, credited flag, AiContribution All/None/Partly, defaulting to All for a GenerativeAI special contributor), DisplayArtist, WorkId and ResourceRightsController (share, delegated use, territory, period); these AI fields are absent from the ERN 4.3 schema read, and the value sets add a UseType for GenerativeAI training. DDEX guidance says rights belong in RightsController, not Deals, yet tells recipients to follow ReleaseDeal when both state ownership (tension kept).
• articleWhat do the ISRC Handbook and CISAC say each identifier identifies, and when does an edit, remix, stem, remaster or clip of a music recording need its own ISRC?
  The ISRC Handbook (2021, CC BY-ND 4.0) ties an ISRC to a recording, not its encoding: new ISRCs for edits, covers, live versions, separately released stems and promo clips; none for codec changes, non-creative remasters or length changes under 10 seconds without creative input; MIDI files get none. CISAC's ISWC identifies the musical work by title and creators, not its recordings or uses. They are different keys for the same cue.
• articleHow do DCMP, Netflix English (USA) and BBC guides handle music descriptions and song lyrics in captions?
  Lyrics marking differs: Netflix ♪ at start and end of each subtitle plus italics; BBC # at the start of lyric subtitles (centred), mood music labelled only when required; DCMP marks nonessential background music with a ♪ icon top right and never at the expense of dialogue. Only Netflix requires italic lyrics.
• articleHow did Netflix's published M&E true-peak wording change across archived versions of the Sound Mix Specifications, and where does a 2.0 stereo M&E rule live now?
  Across archived Netflix Sound Mix Specifications (v1.1 2019, v1.4 2022, v1.5 2023, v1.6 2026), every stated M&E ceiling is -2 dB true peak (+18 dBu / -2 dBFS over a -20 dBFS reference); the 5.1 M&E section stated it in 2019 but not in v1.4 onward (by reference via the Atmos rerender rule), the 2.0 stereo M&E section persists in v1.4 although its change log says it was removed in 2020, v1.5 records its removal in 2023, and v1.6 removed Atmos true-peak language.

More