AI Music Sound Design & Production Craft Hub | Jack Righteous
Production starts when you can name what the sound is doing.
Prompting can establish direction. Production craft is what happens when you listen to the result as a system: which sound occupies which role, what masks what, where density changes, how space is used and whether the arrangement translates the creative brief into an intentional listening experience.
This is platform-independent training. Suno, Udio, Musicfy, ElevenLabs Music, stem tools and DAWs may expose different controls. The production decisions and evidence should remain understandable outside any one tool.
Where production belongs
Creative direction → reference evidence → genre requirements → generation → comparison → diagnosis → sound design → arrangement/production → mix/QC → documentation → delivery.
Prerequisite
Bring a selected generation, stem set or source you want to improve, plus the project job. If genre identity matters, have a Genre Control Brief or equivalent evidence of what must be protected.
Outcome
Diagnose one production problem, protect the strongest sonic decisions, run the smallest useful test and document the result.
Completion
Finish a Production Control Record v1. It becomes the bridge into deeper BUILD or CONTROL work when the project needs repeatability or systematic repair.
Success
You can explain which layer is failing and why the next action is a production change—not another random regeneration.
The JR Production Control Framework
Timbre
The character of individual sounds: bright, dull, rough, smooth, acoustic, synthetic, saturated, clean. Ask whether the source character fits its job.
Texture
How layers combine into a surface: sparse, dense, layered, dry, blurred, granular, open. Texture is a relationship, not an adjective pile.
Frequency roles
Which elements dominate low, low-mid, mid and high regions? Diagnose masking and role competition before simply boosting everything.
Rhythm section
How drums, percussion and bass create pulse, pocket and movement together. Genre identity often depends on their relationship more than their individual sounds.
Foreground
What owns attention: vocal, lead instrument, riff, sample, hook or texture? Support layers should clarify—not compete with—the foreground.
Space
Depth, width, dryness, ambience and silence. Space can separate roles, create intimacy or make a section feel larger without adding more notes.
Density
How much happens at once and how that changes by section. Arrangement density is one of the strongest controls for contrast.
Dynamics
Relative intensity and transient behavior over time. A louder section is not automatically a more effective section.
Transitions
How sections connect through fills, silence, filters, risers, drops, harmonic turns, pickups or changes in texture and density.
Energy
The perceived movement created by rhythm, register, density, dynamics, harmony and foreground—not a fake fixed percentage.
Mix translation
Whether priorities remain understandable across reasonable listening conditions. Check clarity, balance and foreground ownership rather than chasing one playback system.
Do not solve a writing problem with mixing. If the hook is weak, the lyric does not scan, the section has no job or the genre grammar is wrong, return to that layer. Production cannot make an unclear creative decision precise.
The production diagnosis loop
- Listen without editing. Name the audible symptom.
- Locate the layer. Timbre, frequency role, rhythm section, foreground, space, density, dynamics, transition, structure or mix?
- Protect three traits. Record what already works and should not drift.
- Write one hypothesis. Explain what relationship may be causing the symptom.
- Make the smallest useful change. Change one variable when the purpose is learning.
- Compare against the same brief. Listen for the intended improvement and side effects.
- Keep, revise, roll back or escalate. Do not keep a change merely because it is newer.
Common symptoms and first tests
| Symptom | Possible cause | First useful test |
|---|---|---|
| Hook disappears | Foreground competition or excessive density. | Reduce one competing layer before adding level or brightness. |
| Low end feels huge but weak | Bass and kick may occupy the same role without useful timing or frequency separation. | Change one relationship: rhythm, sustain, register or level. |
| Verse and chorus feel the same size | Density, register, space and dynamics may not change enough. | Change one contrast dimension while protecting the hook. |
| Vocal feels detached | Space, tone, level or arrangement may not support the foreground. | Test one support/space relationship before replacing the vocal. |
| Track feels muddy | Several elements may dominate the same mid/low-mid region. | Reduce or reposition one role rather than boosting highs everywhere. |
| Drop or transition feels weak | Insufficient withholding or no clear transition job. | Remove one element before the event or change the transition cue. |
| Everything is loud | No hierarchy or dynamic contrast. | Identify foreground and reduce one support layer. |
| Good song, one broken section | Local edit problem, not global prompting problem. | Protect the winner and repair only the failing region. |
Production Control Record v1
Complete before moving on:
Project job · reference evidence · genre/lane · desired sonic identity · low-end role · drum/percussion role · foreground role · harmonic/melodic density · texture · spatial character · dynamic arc · section density · transitions · three protected sonic traits · diagnosed production problem · hypothesis · one-variable test · evidence · side effects · winning version · next action.
Platform translation
Suno
If a strong song has a local problem, use the Suno Editing Implementation Guide rather than treating full regeneration as the default.
Udio and other music generators
Translate the same diagnosis into the editing, generation, source or arrangement controls available. Preserve the external Production Control Record so the reasoning survives the platform.
Musicfy / voice and source workflows
Keep source contribution, transformation goal and protected traits explicit when working with voice, stems or transformed material.
DAW / stem workflow
Use stems and timeline editing when precise balance, automation, spatial, arrangement or repair decisions require controls beyond the generator.
Supporting systems
Structure problem?
Use Song Structure Engineering before trying to mix your way out of a form problem.
Prompt problem?
Return to the AI Music Prompt Engineering Guide when the musical specification itself is unclear.
Genre problem?
Use the Genre Intelligence Hub and build Genre Control Brief v1.
Finishing problem?
Move into the site's mixing/mastering and release-readiness resources only after composition, arrangement and production priorities are stable.
When to move deeper
If this Production Control Record solves the problem, keep working at the free level. If you need to construct a sound reliably from a defined Sound Identity, move to Build Your Sound | BUILD DEVELOP Lab and produce a Sound Recipe v1 + Repeatability Record. If you already have a repeatable recipe but need systematic repair, source protection, stems, comping or version-control evidence, move to Control Your Sound | CONTROL DEVELOP Lab.
Production Intelligence navigation
AI-generated material may contain inconsistencies that require regeneration, editing, stem work or conventional production tools. No prompt or platform feature guarantees a professional result; the durable skill is diagnosis, controlled intervention and documented judgment.
