You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I like the styling in btop https://github.com/aristocratos/btop#screenshots
I think it would be best to not make it so expansive, but tidy and small..
Imagine each output had a single line similar to btop's C0-C15 lines. You get a buffer of time where you see the note hits of each track in realtime.
This is a screenshot in btop of cpu usage (each line scrolls to the left as time passes), but just imagine these are notes hitting in glicol timeline:
I like the styling in btop https://github.com/aristocratos/btop#screenshots I think it would be best to not make it so expansive, but tidy and small.. Imagine each output had a single line similar to btop's C0-C15 lines. You get a buffer of time where you see the note hits of each track in realtime.
This is a screenshot in btop of cpu usage (each line scrolls to the left as time passes), but just imagine these are notes hitting in glicol timeline:
I just built a simple visualiser, but I am also considering Oscilloscope using Canvas from tui-rs.
The sequencer looks cool but I am not sure if it will fit rhythms that are not 4 or 8 grids. But it's always good to have an option there.
Another good point is to provide some information for the audio rendering capacity, which just came to my mind by looking at this example.
chaosprint
changed the title
Do we need TUI for oscilloscope or spectrogram?
TUI to show information
Mar 18, 2023
chaosprint
changed the title
TUI to show information
Improve TUI to show more information: console, tutorial, etc.
Mar 19, 2023
The text was updated successfully, but these errors were encountered: