Knowledge hub / AFG Music / production
Arrangement & Role Reference: Five Forces, Eleven Views
Music knowledge / Guides and practical tools
About this reference
From the music-learning collection, adapted for Philojain Music Muse. Referenced sources remain credited in the article.
Recording & Production · Reference
Set a primary, secondary and up to three supporting forces — Time, Rhythm, Pitch, Timbre, Energy — against one of five genre states, then shape the force-cycle core, a negative-force silence, an optional force collision, the music theory underneath and the techniques on top. What comes out is an arrangement spec — a written brief a player takes into a room — and the same spec reads differently depending on which of eleven chairs you are sitting in: full spec, force report, melody, practice, bass, drums, producer, keys, arrangement, live or session. Nothing here is written on the fly; every view is a fixed lookup against the choices above it.
Every preset's reference track was independently checked before publishing — one album attribution was corrected in the process. See the FAQ and Sources.
01 — Force Declaration
Which forces are driving?
Every arrangement is read as one primary force, one secondary force, up to three supporting forces, and the genre state they all operate inside. Nothing below this point changes what these five mean — only how loudly each one speaks.
02 — 32 Checked Presets
Or start from a reference.
Twelve style categories, thirty-two presets, each carrying one real reference track independently checked against Wikipedia and official discography sources before publishing. Using a preset sets the force declaration and the tempo/riff defaults below — everything else stays yours to shape.
03 — The Force-Cycle Core
Every force, three ways.
Each of the five forces below carries three fields and eight options apiece — 120 choices in total. Time is character, phrase and tempo; Rhythm is groove, accent and drum-riff; Pitch is scale, harmony and melodic logic; Timbre is guitar, space and mix; Energy is state, curve and reaction.
04 — Negative Force
What the arrangement withholds.
Silence is material, not absence. Set what kind of silence, where it lands, and how it decays — a hard cutoff reads nothing like a ringing tail or a palm-muted choke.
05 — Force Collision
Borrow on purpose.
Optionally borrow a trait from one genre state and apply it inside another, with a stated intent — so it reads as a deliberate move, not a mistake. Leave “borrow from” and “apply to” matched to skip a collision entirely.
06 — Music Theory
The logic underneath.
Five structural questions that sit below any one force: how wide the register runs, how density behaves, how sections hand off, how tension is built, and which general feel the choices above are biased toward.
07 — Techniques
What the hands do.
Four technique families — guitar, rhythmic, timbral, expressive — each a multi-select: pick as many as apply. These feed the Melody and Practice views directly, and the Live view's stamina and feedback-risk notes.
08 — Space, Tempo & Architecture
How it’s built.
Arrangement density and difficulty, a concrete tempo band and time signature, how the riff is architected, whether the piece loops or arcs, and what to deliberately avoid. Presets set sensible tempo and riff defaults here automatically — see the note below.
Most presets above only set the force declaration and leave tempo and riff architecture on their shared defaults rather than repeating them on every preset — the fallback is intentional and explicit (see DEFAULT_TEMPO_CONFIG / DEFAULT_RIFF_CONFIG in this page's own code). A handful of presets override one or both where the reference track genuinely needs a different tempo band.
09 — The Point Of The Tool
One set of choices. Eleven chairs.
The same declaration, force-cycle core, negative force, collision, theory, techniques and architecture above — read for a different person in the room each time. The Producer view carries frequency allocation and bus processing nobody else needs; the Live view carries stage setup, stamina notes and feedback risk; the Session view carries tracking order and mic position. Switch views below; nothing above needs to change.
Deeper — Auditory Masking
The psychoacoustic reason a “frequency collision” is audible at all
Section 10’s own FAQ above lists the sub-bass-through-air frequency bands this page’s Producer and Session views work from, but it stops at naming the bands — it doesn’t say why two instruments sharing one band actually causes an audible problem rather than just an aesthetic one. The mechanism is called auditory masking, and it’s a property of hearing itself, not of any particular instrument or genre. Per the University of Minnesota’s own course materials on sensation and perception, “masking is the process by which the presence of one sound makes another sound more difficult to hear” — specifically, “a more intense sound will mask a less intense sound, assuming that the frequency content of the sounds overlap.”
That’s the actual physical event underneath what Section 05’s Force Collision and Section 06’s density field are managing in different language — two parts sharing a frequency band aren’t just competing for a listener’s attention in the abstract; the louder one is measurably reducing how audible the quieter one is, inside the ear itself.
Deeper — Why The Low End Claims First
Why the low end gets first claim on arrangement decisions, not just loudest claim
The masking relationship isn’t symmetric, which matters directly for a tool built around force declarations and frequency bands. The same UMN source states it plainly: “low-frequency sounds are more likely to mask high frequencies than vice versa, particularly at high sound intensities.” A dense, loud bass or kick part doesn’t just compete evenly with a busy mid-range guitar or vocal line sharing its energy at high intensity — it has a structural advantage in burying what’s above it that a busy high part pushed just as loud does not have in reverse.
That asymmetry is a real, mechanical reason Section 03’s Timbre field and Section 08’s density controls above are worth setting deliberately for the low end first, before worrying about competing parts higher up — not a stylistic preference, but a direct consequence of which direction masking actually runs. It also gives Section 05’s Force Collision a sharper edge: borrowing a dense, low-register trait from one genre state into another isn’t a neutral swap the way borrowing a high, sparse one is — the low-register borrow is the one more likely to bury whatever else is already occupying the arrangement, purely because of which way masking runs, independent of which two genre states are being combined.
10 — Common Questions
Asked before the first rehearsal.
Is the spec written fresh each time, or fixed content?
It’s fixed content, recombined. Every force option, technique, theory field and preset on this page was written for the dashboard ahead of time. Selecting items composes them into an arrangement spec using a fixed set of if/then rules defined in this page’s own code — every line the spec shows traces back to a specific control above it. Nothing is written on the fly.
Why does the same selection read differently in each of the eleven views?
Because each view is a separate lookup function reading different fields from the same underlying choices, for a different person in the room. The Producer view pulls timbre, frequency allocation and bus-processing fields the Bass view never touches; the Live view pulls energy, stamina and feedback-risk fields the Session view never touches. Same source data, eleven different jobs.
Were the reference tracks on this page checked?
Yes. Every band/song pairing attached to the 32 presets was independently checked against Wikipedia and official discography sources before publishing. One pairing was corrected during that check — Korpiklaani’s “Wooden Pints” is the opening track of their 2003 debut Spirit of the Forest, not the 2006 album Tales Along This Road it was first drafted against — and now shows correctly. Every other pairing checked out as drafted. See Sources.
What is a “force collision”, in plain terms?
Deliberately borrowing a trait from one genre state and applying it inside another — a funk ghost-note pocket under a metal riff, a djent subdivision under a punk tempo — stated with an explicit intent (textural contrast, rhythmic surprise and so on) so it reads as a choice, not an accident.
Why do Time, Rhythm, Pitch, Timbre and Energy use different border styles instead of colour?
So the five forces stay tellable apart in black and white, in print, and to a colour-blind reader — not just on a colour screen. Time is a solid heavy border, Rhythm is dashed, Pitch is dotted, Timbre is a double rule, and Energy is filled solid black rather than outlined; each also carries its own glyph. This follows the same method the estate’s RERA developer index established first for a four-state badge carried entirely by stroke style, fill and glyph.
What’s a “negative force”?
Silence, treated as material rather than absence: what kind of silence (a full-band cutout, a single instrument dropping out, a held gap), where it lands, and how it decays (a hard cutoff, a ringing tail, a palm-muted choke). Arrangements are built from what plays and from what deliberately does not.
Are the frequency ranges and mic-placement notes in the Producer and Session views exact?
They are general, widely-used conventions — sub-bass roughly 20–60 Hz, bass 60–250 Hz, low-mid 250–500 Hz, mid 500 Hz–2 kHz, upper-mid 2–4 kHz, presence 4–6 kHz, air 6–20 kHz — not a claim about any specific recording. Mic-placement guidance (on-axis vs off-axis, centre vs cone edge) follows the same general, sourced convention. See Sources.
11 — Sources
Where these facts come from
- Mastering The Mix — “Audio Frequency Ranges Explained” (sub-bass through brilliance band conventions)masteringthemix.com · accessed 29 Jul 2026
- MixAcademia — “Frequency Range: Sub-bass, Bass, Midrange, High and Treble”mixacademia.com · accessed 29 Jul 2026
- Sweetwater InSync — “How to Mic a Guitar Amplifier” (on-axis/off-axis, centre-vs-edge mic placement)sweetwater.com · accessed 29 Jul 2026
- LANDR Blog — “How To Mix Kick and Bass: Sidechain Compression Mix Tips”blog.landr.com · accessed 29 Jul 2026
- Sound on Sound — “What’s the best order for recording a band?” (rhythm section first, vocals/leads last is the common convention, not the only method)soundonsound.com · accessed 29 Jul 2026
- Wikipedia — “Blast beat” (typical working tempo range for the extreme-metal drumming figure)en.wikipedia.org · accessed 29 Jul 2026
- Wikipedia — corrected preset attribution: Korpiklaani’s “Wooden Pints” opens Spirit of the Forest (2003)en.wikipedia.org · accessed 29 Jul 2026
- Wikipedia — confirms “Wooden Pints” is not on Tales Along This Road (2006), the album first drafted against iten.wikipedia.org · accessed 29 Jul 2026
- University of Minnesota Pressbooks, Sensation and Perception — “Critical Bands and Masking”pressbooks.umn.edu · accessed 11 Aug 2026
Method: every one of the 32 preset reference tracks was checked individually against Wikipedia and/or the artist’s official discography before publishing, confirming the song exists, is by the credited artist, and is on the credited album in the credited year. One attribution was corrected in that process (sources 7–8); every other pairing checked out as originally drafted. A claim this build considered and chose not to publish: an early draft wanted to cite Meshuggah’s exact 8-string tuning history against a general encyclopedia source, but the specific wording couldn’t be confirmed against that source’s current text, so the claim was cut rather than published unverified. General technical claims — frequency bands, mic placement, sidechain routing, session tracking order — are sourced above (1–6) rather than attached to any single preset, since they describe common practice, not one recording.
Related
Keep going
Keep exploring