Recommended workspace structure
Here is how I would design the 3 modes.
⸻
- Compose workspace
Purpose
Define the musical structure and asset set.
Primary focus
• sounds
• MIDI/event sources
• timeline
• song structure
• annotations
• light layout awareness
Main canvas
A large timeline/editor is the hero.
Supporting elements
• light sound browser
• imported MIDI sources panel
• section markers
• light grid reference, small and non-dominant
Left icon rail
• Sounds
• Events
• Presets
• Sources maybe deserves its own icon later
Right icon rail
• optional lightweight inspector
• perhaps event details, section details, or constraints
User actions
• import one or more MIDI files
• map MIDI tracks to sounds
• rename sounds
• create/merge event lanes
• add section markers
• add performance notes / FX notes
• pin certain sounds or clusters as “must stay together”
• create starter manual placements
Important note
In Compose mode, the user should be able to do manual seeding without fully entering optimization mode.
That is important for your drum placement idea.
⸻
- Optimize workspace
Purpose
Turn the authored material into playable layouts.
Primary focus
• active grid as hero
• candidate layouts
• metrics
• rationale
• debugger / optimization trace
Main canvas
A large central grid with optional overlays:
• hand regions
• finger paths
• movement arcs
• locked pads
• manually assigned sounds
• generated suggestions
Supporting regions
• candidate gallery, not cramped sidebar stack
• metrics inspector
• debugger / trace drawer
• minimized timeline strip or toggleable timeline
Left icon rail
• Sounds
• Events
• Presets
But these are secondary here.
Right icon rail
• Layouts
• Costs
• Debugger
You may eventually want Debugger as a separate right-side icon rather than burying it under costs.
Key behavior
This is where partial optimization becomes first-class.
Example workflow:
• user manually locks kick, snare, hats
• app optimizes remaining sounds only
• user sees locked vs free assignments visually
• candidate generation respects constraints
That is a big product win.
⸻
- Practice workspace
Purpose
Rehearse the chosen layout.
Primary focus
• large timeline
• synced active pads
• minimal clutter
• playback / wait mode / scoring
• performance feedback
Main canvas
Split emphasis:
• dominant scrolling timeline
• active pad visualization
• maybe a compact hero grid that lights up
• incoming note prompts / played note feedback
Minimal panels
Practice mode should be much cleaner.
Left and right panels should mostly stay collapsed unless summoned.
User actions
• play through
• wait mode
• score timing / accuracy
• compare performed note vs intended event
• show fingering cues optionally
• show section markers and performance notes
This mode should feel like a different product surface entirely.
⸻
Your sidebar idea, refined
I would structure it like this:
Left rail: authoring/navigation
• Sounds
• Events
• Presets
• maybe Sources later
Right rail: analysis/output
• Layouts
• Costs
• Debugger
• maybe Inspector depending on scope
Behavior
• icon click opens panel
• only one drawer open per side at a time
• drawers are resizable
• mode determines default panel
• panels can be pinned open on large screens
• Practice mode defaults to collapsed rails
That gives you flexibility without permanent clutter.
Recommended workspace structure
Here is how I would design the 3 modes.
⸻
Purpose
Define the musical structure and asset set.
Primary focus
• sounds
• MIDI/event sources
• timeline
• song structure
• annotations
• light layout awareness
Main canvas
A large timeline/editor is the hero.
Supporting elements
• light sound browser
• imported MIDI sources panel
• section markers
• light grid reference, small and non-dominant
Left icon rail
• Sounds
• Events
• Presets
• Sources maybe deserves its own icon later
Right icon rail
• optional lightweight inspector
• perhaps event details, section details, or constraints
User actions
• import one or more MIDI files
• map MIDI tracks to sounds
• rename sounds
• create/merge event lanes
• add section markers
• add performance notes / FX notes
• pin certain sounds or clusters as “must stay together”
• create starter manual placements
Important note
In Compose mode, the user should be able to do manual seeding without fully entering optimization mode.
That is important for your drum placement idea.
⸻
Purpose
Turn the authored material into playable layouts.
Primary focus
• active grid as hero
• candidate layouts
• metrics
• rationale
• debugger / optimization trace
Main canvas
A large central grid with optional overlays:
• hand regions
• finger paths
• movement arcs
• locked pads
• manually assigned sounds
• generated suggestions
Supporting regions
• candidate gallery, not cramped sidebar stack
• metrics inspector
• debugger / trace drawer
• minimized timeline strip or toggleable timeline
Left icon rail
• Sounds
• Events
• Presets
But these are secondary here.
Right icon rail
• Layouts
• Costs
• Debugger
You may eventually want Debugger as a separate right-side icon rather than burying it under costs.
Key behavior
This is where partial optimization becomes first-class.
Example workflow:
• user manually locks kick, snare, hats
• app optimizes remaining sounds only
• user sees locked vs free assignments visually
• candidate generation respects constraints
That is a big product win.
⸻
Purpose
Rehearse the chosen layout.
Primary focus
• large timeline
• synced active pads
• minimal clutter
• playback / wait mode / scoring
• performance feedback
Main canvas
Split emphasis:
• dominant scrolling timeline
• active pad visualization
• maybe a compact hero grid that lights up
• incoming note prompts / played note feedback
Minimal panels
Practice mode should be much cleaner.
Left and right panels should mostly stay collapsed unless summoned.
User actions
• play through
• wait mode
• score timing / accuracy
• compare performed note vs intended event
• show fingering cues optionally
• show section markers and performance notes
This mode should feel like a different product surface entirely.
⸻
Your sidebar idea, refined
I would structure it like this:
Left rail: authoring/navigation
• Sounds
• Events
• Presets
• maybe Sources later
Right rail: analysis/output
• Layouts
• Costs
• Debugger
• maybe Inspector depending on scope
Behavior
• icon click opens panel
• only one drawer open per side at a time
• drawers are resizable
• mode determines default panel
• panels can be pinned open on large screens
• Practice mode defaults to collapsed rails
That gives you flexibility without permanent clutter.