I really like how you simply have it as an option in the “track palette”. Making it optional is a great idea IMO.
Sometimes (like in that other topic about finding the “hit point” of a sample) it would be a great thing to guide and assist you, and at other times I would rather be without all this “visual noise”.
Also, I like that you’re not talking about traditional audio-tracks but rather, simply adding a visualization layer.
there is probably a whole bunch of discussion and visuals around this, but I couldn’t find it!
Yes, going back a loooong time.Here are a few of the discussions that I’ve collectedover the years
- 20130-brainstorming-audio-tracks/
- 33842-what-would-you-like-to-see-in-a-renoise-30/?p=271976
- 34416-waveform-over-pattern/
- 40049-sample-waveform-view-in-tracks/
I wonder how taxing it would be on the CPU to have to re-render the waveforms when something changes, I guess no different from the tape-style DAWs
No idea exactly how taxing, but definitely more complex than a traditional DAW.
I mean, enter a few 0Bxx and Uxx and you should see the change in playback direction or tempo being reflected in the waveform.
Another thing to consider is whether a track more than a single note column should be visualized per column, or as a whole track?
I would say per-column, simply because a fully expanded track (12 note columns) hardly can fit on a small monitor anyway. Where would you want it to go then? Streeeeeeeetching across the whole track would make it very hard to “read”.