How do I plan music to picture: hit points, tempo choice and frames per beat?
Problem: AI or library music has to end on the cut and land accents on picture events. Conditions: a locked or near-locked cut with timecode. Method (Music Technology, Jan 1988, a composer's workflow): the picture dictates to the music; first fix the cue's exact length and list hit points (action points to accent) as timecode hours:minutes:seconds:frames, often with a one-hour offset (01:00:00:00 start); then choose a tempo that suits the mood, and check where hit points fall on bars and beats; you will not get all on downbeats, so pick the most important hits, change tempo, insert a 3/4 or 5/4 bar, or use ritardando/accelerando; there is no rule that every hit lands on a downbeat. The article notes the old frames-per-click notation and that software of the time calculated the layout. Frame maths (my arithmetic, not from the article): frames per beat = fps x 60 / BPM, so at 24 fps, 120 BPM is 12 frames per beat and 48 frames per 4/4 bar; 90 BPM is 16 frames per beat; at 25 fps, 120 ...
Structured fields
{
"citations": [
{
"url": "https://www.muzines.co.uk/articles/picture-scoring/2220",
"note": "Picture scoring text; Hit points; Hitting the Mark"
}
]
}Evidence claims
- [sourced_fact] Problem: AI or library music has to end on the cut and land accents on picture events. Conditions: a locked or near-locked cut with timecode. Method (Music Technology, Jan 1988, a composer's workflow): the picture dictates to the music; first fix the cue's exact length and list hit points (action points to accent) as timecode hours:minutes:seconds:frames, often with a one-hour offset (01:00:00:00 start); then choose a tempo that suits the mood, and check where hit points fall on bars and beats; you will not get all on downbeats, so pick the most important hits, change tempo, insert a 3/4 or 5/4 bar, or use ritardando/accelerando; there is no rule that every hit lands on a downbeat. The article notes the old frames-per-click notation and that software of the time calculated the layout. Frame maths (my arithmetic, not from the article): frames per beat = fps x 60 / BPM, so at 24 fps, 120 BPM is 12 frames per beat and 48 frames per 4/4 bar; 90 BPM is 16 frames per beat; at 25 fps, 120 BPM is 12.5 frames per beat, so beats fall between frames on alternate beats; to make a click land on frames pick tempos where fps x 60 / BPM is an integer (e.g. 24 fps: 144, 120, 96, 80, 72, 60 BPM). Also remember 23.976 vs 24 fps and 29.97 drop-frame differences shift timecode by about 0.1 percent, enough to drift by a couple of frames per minute. For AI music (inference): choose or request a tempo that fits the hit-point grid, then use extend/crop/replace-section style edits or a DAW tempo map to end exactly on the out point. Failure modes: starting timecode offset forgotten; mixing 24 and 23.976 clocks. Limitations: 1988 article, dated tools; mood-tempo advice is subjective. · locator: Picture scoring text; Hit points; Hitting the Mark source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |