Half-baked ideas 🥧 🧑‍🍳

[nathanleiby]

Dumping these here.. for eventual triage / clarity.

• UX v2: Design
  • commit UI prototypes (tauri, iced) to Github (optionally, migrate into macroix repo if reasonable to centralize)
  • Make UI look nice-ish
    • do a pass in Figma -> trying here
    • better font
    • funklet inspired colors and look
    • show/hide noisy stuff
  • prototype in Figma: core interactions, colors, layout, etc
    • might we show music as sheet music notation (e.g. https://github.com/jaredforth/lilypond-rs or various others)
    • https://github.com/staff-rs/staff/
  • Explore similar existing offerings
    • Drum specific..
      • https://www.mutedrums.com/ / https://www.playdrumsonline.com/ (https://www.playdrumsonline.com/songs/create)
      • Melodics
      • Clone Hero
    • Rhythm games
      • Rhythm Doctor
      • Stepmania
      • Osu
  • Theming
    • UI: try out theme colors from rerun https://github.com/rerun-io/rerun/blob/4636188996038f4be913f813fb263a3751c1d469/crates/re_ui/src/design_tokens.rs#L207
      • see other inspiration: Showcase gallery: share your egui screenshots here! emilk/egui#996
  • UI: consider dark-mode switcher widget https://tau.garden/egui-theme-switch/
• NEED UX DESIGN WORK
  • redo the "calibrate latency offset" UX. Look at other models like Rhythm Doctor
  • Capture progress over time (graph it, etc)
    • The full details of the gold mode chart.
    • Personal bests.
  • Quick start + gets you into flow.
    • how to reduce barrier to entry?
      • resume previous state?
      • daily challenge?
      • suggested activities?
      • warm up drill? (with option to skip)
      • remind user of last session's work. progress and
  • Midi re-mapping interface
  • Gold mode UX
    • how to make it easy to see an act from, but not too distracting
    • try colored emojis via https://crates.io/crates/egui-twemoji for gold mode status
• More nuanced Accuracy scoring
  • Possible approach: Use more Accuracy levels instead of just CORRECT , EARLY/LATE , MISSED. For example, in DDR a note can be "marvelous", "perfect", "great, "good", ... these are finer gradations of early/late
• accuracy
  • figure out how to allow first beat to get measured correct. since space starts clock right away... need a click in or empty space before the notes
  • Allow tuning margin for correctness in FE, until it feels dialied in. (see score.rs)
  • visualize correctness across multiple attempts of the loop
    • idea: box and whisker for each note
    • idea: color for each note (e.g. red for bad, green for good .. could also have a color to indicate early/late/miss trends)
  • since you started (press a button to reset)
  • all time
• visualize beat as sheet music
  • stretch: highlight the active note
  • stretch: moving bar
• support other meters
  • Implied 4/4 now.. What about 6/8?
  • Also, could relate to ability to fine tune note positions
• improve "save loop" UX
  • Make sure it's clear when you save! I hit "s" a few times thinking I saved things, but I didn't. Maybe add a save button to UI?
  • Alow editing name of loop. I often want to keep track of a real beat.
  • Allow grouping/tagging
    • folder system, tags, etc...
    • ex: all beats related to a single song.
    • ex: all beats building up to a more complex beat .. a practice sequence
    • ex: by genre, artist, etc
• sync saved loops across devices - I'm using 2 devices for dev + practice flow today.
  • How?
    • read from remote DB? Firebase, Dexie, etc
    • Simplest CRUD possible
    • consider abstract DB backend for opensource flexibility
• Extract drums from a song (ML), then translate to a loop to practice
• Handle wrong/extra hits (ignored right now)
• layer on complexity
  • for example: https://photos.app.goo.gl/ALXpmdq2ztNAwWY6A
  • Could generate increasingly complex exercises, potentially incorporating skills you need.
    New drums to hit
    New displacement
    Flams
    Whatever

---

• building for android or ios
  • https://macroquad.rs/articles/android/
  • https://macroquad.rs/articles/ios/
• midi - how does it work?
  • https://computermusicresource.com/MIDI.Commands.html
• get better at using rust (+VSCode), e.g. debugger, cargo fix, etc https://code.visualstudio.com/docs/languages/rust
• Explore macroquad featureset, including experimental like state machine and scenes
  • Also explore community extension https://github.com/ozkriff/awesome-quads
• Make "voices" data model more generic.
  • support different numbers of voices (not just 4, as today)
  • capture loop config like tempo, length, etc. (++ for tempo ASAP)

  name:
  bpm:
  beats_total:
  beats_per_measure: # optional, will draw lines if so
  voices: # TODO: instruments?
    [
        sound: required
        override_name: # optional:
        notes: [] # a series of numbers, 0 indexes, corresponding to the beats to play on.
    ]
  

• explore improving Kira's interface around the clock and looping to support my sequencer like use-case
  • idea: editing clock while it's playing
• should use kira's built-in Metronome concept? https://github.com/tesselode/kira/blob/main/changelog.md#multiple-metronomes
• try rust tracing lib for better logs