ReasonTouch Technical Companion
Version: Draft 1.0


10. Future Evolution Roadmap


10.1 Philosophy

ReasonTouch has deliberately been designed as a long-term musical platform rather than a fixed application.

The architecture separates:

  • musical knowledge
  • musical analysis
  • musical planning
  • user interaction
  • playback
  • rendering

This separation means the application can continue growing for many years without major redesign.

The current release represents only the first generation of the system.


10.2 Short-Term Development

Following completion of the current refactoring, the next development stage focuses on completing the musical workflow.

Primary objectives include:

  • Completion of Progression Planning
  • Phrase continuation
  • Harmonic destination planning
  • Better borrowed chord usage
  • Improved cadence recognition
  • User-editable generation settings

This stage completes the original vision of intelligent progression generation.


10.3 Phase Two — Intelligent Musical Assistant

Once progression generation becomes stable, ReasonTouch evolves into an active musical assistant.

Instead of merely responding to user input, the software begins making musical observations.

Examples include:

“This progression feels unresolved.”

“Would you like a stronger cadence?”

“This chorus could benefit from more harmonic contrast.”

“Your verse and chorus are extremely similar.”

Rather than suggesting random chords, the assistant begins discussing musical structure.


10.4 Musical Intent Detection

Future versions should infer the user’s intentions.

For example:

Current progression:

I — vi — IV — V

The system might infer:

  • pop ballad
  • emotional
  • uplifting
  • unresolved ending

Rather than offering generic suggestions it may instead ask:

Do you want to:

  • resolve?
  • build tension?
  • surprise the listener?
  • repeat?
  • prepare a bridge?

Generation therefore becomes intent-driven rather than algorithm-driven.


10.5 Progression Pairing Engine

One of the most significant planned additions is the Progression Pairing Engine.

Instead of generating isolated progressions, the system evaluates relationships between sections.

Examples include:

Verse

Pre-Chorus

Chorus

Bridge

Final Chorus

Each section gains a defined musical role.


Planned Pairing Analysis

Possible measurements include:

  • tonal distance
  • emotional contrast
  • cadence compatibility
  • shared harmonic DNA
  • melodic compatibility
  • energy transition
  • listener expectation

This transforms songwriting from isolated chord creation into complete song architecture.


10.6 Song-Level Planning

Eventually the planner operates across an entire composition.

Instead of suggesting four chords it begins suggesting:

  • section ordering
  • modulation points
  • key changes
  • chorus placement
  • bridge timing
  • outro strategy

For example:

Verse

↓

Verse

↓

Pre-Chorus

↓

Chorus

↓

Verse 2

↓

Bridge

↓

Final Chorus

↓

Outro

Each recommendation is justified using musical reasoning.


10.7 Advanced Harmonic Intelligence

Future analysis layers may include:

Secondary Dominants

Detect:

V/V

V/ii

V/vi

and recommend appropriate resolutions.


Automatic recognition of:

  • bVII
  • bVI
  • iv minor
  • Neapolitan relationships

with explanations for emotional impact.


Chromatic Harmony

Support for:

  • chromatic mediants
  • augmented sixth chords
  • diminished passing harmony
  • common-tone modulation

Functional Ambiguity

Instead of assigning a single function, future analysis may produce probabilities.

Example:

Chord:

D

Possible functions:

65%
V/V

25%
II

10%
Modal Borrowing

This reflects genuine music theory ambiguity.


10.8 Voice-Leading Engine

Chord suggestions currently focus on harmonic progression.

Future versions should optimise:

  • voice leading
  • inversion choice
  • common tones
  • stepwise movement

rather than merely selecting the next harmonic function.

The planner therefore produces:

Harmony

+

Voicing

+

Movement

simultaneously.


10.9 Melody-Aware Harmony

Eventually ReasonTouch should analyse melody alongside chords.

Possible capabilities include:

  • avoid clashes
  • recommend passing chords
  • harmonise melodies
  • identify implied harmony
  • suggest substitutions

This significantly increases musical sophistication.


10.10 Rhythm Intelligence

Harmony alone does not create convincing music.

Future rhythm modules may analyse:

  • harmonic rhythm
  • syncopation
  • phrase length
  • bar weighting
  • anticipation
  • suspension

Chord placement therefore becomes as important as chord selection.


10.11 Bass Planning

A future Bass Planning Engine could generate:

  • root movement
  • walking bass
  • pedal tones
  • counter-motion
  • slash chords
  • inversion planning

Bass becomes an independent compositional layer rather than a by-product of harmony.


10.12 Arrangement Intelligence

Beyond chords, the planner could recommend arrangement changes.

Examples:

  • reduce instrumentation
  • increase density
  • introduce counter-melody
  • double the chorus
  • add suspended pad
  • remove drums before chorus

This shifts ReasonTouch towards production assistance.


10.13 MIDI Performance Generation

Current MIDI export focuses primarily on chord playback.

Future systems could generate:

  • realistic piano performance
  • guitar strumming
  • fingerstyle guitar
  • orchestral voicings
  • synth pads
  • rhythmic comping

Humanisation parameters would include:

  • timing
  • dynamics
  • articulation
  • swing
  • velocity curves

10.14 Adaptive Learning

ReasonTouch may eventually learn user preferences.

Examples:

The user frequently chooses:

  • vi
  • IV
  • add9
  • sus2
  • slash chords

The planner gradually increases the probability of similar suggestions while preserving musical correctness.

This creates personalised musical assistance without compromising theory.


10.15 Educational Mode

Future releases may expose internal reasoning.

Example:

Suggestion:

Em

Explanation:

Acts as iii.

Shares two tones with G.

Softens movement towards vi.

Maintains low harmonic tension.

Every recommendation becomes a music theory lesson.


10.16 AI Integration

Generative AI should enhance—not replace—the rule-based harmonic engine.

Potential uses include:

  • explaining theory
  • lyric brainstorming
  • arrangement suggestions
  • educational guidance
  • natural-language interaction

The deterministic planner remains the authority for harmonic correctness, while AI provides conversational support and creative inspiration.


10.17 Cross-Workspace Integration

The long-term vision is a fully connected composition environment.

Current workspaces:

  • Chords
  • Piano Roll
  • MIDI

Future additions may include:

  • Lyrics
  • Melody
  • Arrangement
  • Performance
  • Mixing
  • Mastering

Each workspace shares a common musical understanding rather than operating independently.


10.18 Cloud Collaboration

Possible future collaboration features include:

  • shared projects
  • version history
  • musical comments
  • progression sharing
  • cloud libraries
  • collaborative composition

The underlying harmonic model remains consistent across collaborators.


10.19 Plugin Architecture

Future extensibility may be provided through plugins.

Potential plugin categories:

  • scale libraries
  • jazz harmony packs
  • orchestration modules
  • educational packages
  • MIDI generators
  • alternate notation systems

Plugins interact with published interfaces rather than modifying the core engine.


10.20 Long-Term Vision

The ultimate goal is not merely to generate chord progressions, but to create a comprehensive compositional partner.

ReasonTouch is intended to evolve into a system capable of understanding:

  • harmonic structure
  • musical intention
  • emotional direction
  • compositional architecture
  • stylistic context
  • educational explanation

Its purpose is not to replace the composer, but to augment creativity through informed musical reasoning.


Chapter Summary

Future development of ReasonTouch extends far beyond chord generation. Planned capabilities include progression pairing, whole-song planning, advanced harmonic analysis, melody-aware harmony, rhythm and bass intelligence, educational reasoning, adaptive learning, and collaborative workflows. The architectural decisions made during the current refactoring establish a scalable foundation for these ambitions, ensuring that future features can be integrated without compromising maintainability or theoretical consistency. The long-term vision is a modular, explainable, and extensible musical composition platform that supports composers from initial ideas through complete song development.


<
Previous Post
Chapter 6 – Harmonic Intelligence and Musical Decision Making
>
Next Post
Chapter 13 — Conclusion & Architectural Retrospective