the constraints of a TUI force you to be creative (in a good way) how to represent/encode information to the user.
In a DJ TUI, how to represent the track waveform? Encoding waveform amplitude in ascii blocks or dots is a pretty low fidelity representation. Instead, you can encode waveform amplitude in single row of blocks with 256 color/intensity averaging the backing sample peaks.
And's if you ever do stems separation you have 4 such rows for each track - efficient and dense!
As the track is playing, or user is zooming or jogging, this representation would give more of the feel that the playhead is moving through the track smoothly.
In a DJ TUI, how to represent the track waveform? Encoding waveform amplitude in ascii blocks or dots is a pretty low fidelity representation. Instead, you can encode waveform amplitude in single row of blocks with 256 color/intensity averaging the backing sample peaks.
And's if you ever do stems separation you have 4 such rows for each track - efficient and dense!
As the track is playing, or user is zooming or jogging, this representation would give more of the feel that the playhead is moving through the track smoothly.