Twinned from https://github.com/cfsh/ninefold/issues/261 by tools/beads/import_github.py's reconcile pass.
https://github.com/cfsh/ninefold/discussions/258
"You've invested in juice (glide, playhead glow) but it's all navigation juice. The screen should move because of what you hear: cells flashing on their hits, the row LED pulsing on the beat, roll notes lighting as the playhead crosses them. The events all exist in the sequencer already — this is mostly wiring, and it's the difference between watching a cursor and watching your song be alive. Right now the most audio-reactive thing on screen is the playhead line. "
This one I 100% agree with,
related a bit to https://github.com/cfsh/ninefold/issues/257 Where would we put such grooving.
I agree with cells flashing on hits in patterns, roll notes lighting up as the playhead hits them, and row LEDs pulsing on hits.
Maybe also in the header bar if we are going to make that pinned, we could squeeze in a small 'visualizer' in the middle horizontal space - that expands outwards horizontally as like a waveformy fuzzy thing.
In general I love visualizers and something we could also add for a 'fun' feature too, and the ability to mess with visualizer parameters - but don't want to distract yet from core focus.
None.
No comments.