Member lesson
Dub Genre Control Lab | BUILD
Prove that you can control Dub—not just recognize it.
This lab begins after the free Dub foundation. You are not rebuilding the basics. You are testing whether Dub identity survives deliberate changes to version architecture, spatial routing and fragment/return behavior.
Required before starting: Dub Genre Control Brief v1 + Protect 3 + scored protected baseline + dropout-density A/B + one correction rule.
Review the free prerequisiteDub Control Record v1
Your record must capture the source/riddim, protected relationships, exact mutation, evidence, boundary result, correction rule and platform translation. The purpose is repeatability: can you make another intentional Dub version without depending on one lucky generation?
1 · Lock the protected baseline
Re-score your winner for bass/drum ownership, subtraction logic, effects purpose, fragment placement, return/contrast, groove identity and Dub recognition. Write the Protect 3 at the top of the record. Every mutation below must preserve them unless the exercise is explicitly testing a boundary.
2 · Mutation A — version architecture
A1 · Restrained version
Keep more of the source visible. Use fewer dropouts and shorter empty windows.
A2 · Aggressive version
Remove more non-core material, extend selected gaps and make returns more dramatic while protecting bass/drum authority.
Evidence: save the last version where subtraction strengthens Dub and the first version where groove/source recognition breaks.
3 · Mutation B — spatial routing
Keep arrangement and core instrumentation stable. Change the job of delay/reverb/filtering rather than simply increasing wetness.
- Route one selected fragment or accent into delay instead of treating the whole mix.
- Use reverb to create a temporary depth event, then return to a clearer field.
- Use filter/EQ movement to redirect attention while the bass foundation remains protected.
Document which intervention increased spatial drama without weakening rhythmic ownership.
4 · Mutation C — fragment and return choreography
Choose one foreground source: vocal phrase, horn, guitar/skank, percussion accent, melodica-like lead or another reference-supported element. Test how its disappearance, echo tail and later return change expectation.
Do not change everything at once. Hold the rhythm section and overall spatial family stable so the fragment/return decision can be judged.
5 · Boundary stress
| Boundary | Push until… | Save |
|---|---|---|
| Reggae | the intact song/arrangement matters more than the version process | last Dub-owned / first Reggae-owned |
| Ambient | space and atmosphere override rhythmic/versioning identity | last Dub-owned / first Ambient-owned |
| Dub Techno | Techno pulse/repetition becomes the primary organizing grammar | last Dub-owned / first hybrid/system-owned |
| Generic effects-heavy electronic | FX are present but subtraction, source and return logic stop carrying meaning | last intentional / first decorative |
6 · Build one intentional hybrid
Write ownership before generation. Example: Dub owns version architecture, bass/drum focus and spatial fragments; Techno owns four-on-the-floor pulse and repetitive chord behavior. If you cannot say what each system owns, the hybrid is not yet directed.
After generation, score whether the advertised ownership is actually audible.
7 · Translate to a second platform or workflow
Move the same Dub Control Record into a different capable environment: another AI music generator, a stem/transformation tool plus DAW, or a conventional DAW workflow. Translate functions, not button names.
Platform/workflow A: ________
Platform/workflow B: ________
Protected musical intent: ________
Control that translated directly: ________
Control that required editing/mixing instead: ________
Did the same Dub identity survive? ________
8 · Source, stem and version documentation
Dub’s transformation logic makes provenance especially important. Record where the rhythm/source came from, what you had permission to transform, which stems or generated outputs were used, and what changes you made. If a sample, recording or third-party source requires separate permission, do not treat the AI tool’s commercial terms as a substitute for those rights.
9 · Diagnose before revising
Sounds like Reggae with effects
Reduce global wetness. Make one mute/return sequence structurally meaningful and protect the low-end center.
Effects swallow the groove
Shorten or isolate sends; protect bass/drum transients and use silence between events.
Too empty to remain compelling
Restore one rhythmic or fragment relationship instead of filling every gap.
Feels like Ambient
Reassert rhythmic source ownership and make the spatial moves respond to the version architecture.
Dub Control Record v1 is complete when you have:
- one scored protected baseline;
- one version-architecture mutation;
- one spatial-routing mutation;
- one fragment/return mutation;
- at least one last-in / first-out boundary pair;
- one intentional hybrid with explicit ownership;
- one second-platform/workflow translation;
- source/stem/version documentation; and
- at least three reusable correction rules.
Success criterion: another creator could read your record and understand what musical relationships you were preserving, what you changed, why you rejected alternatives and how you would reproduce the approach without copying one prompt.
Create What You Love | Love What You Create.
Discussion