Thomas Martitz wrote:
I agree with all what pondlife said.
Paul, am I right? On the one had you want to "waste" 64K of RAM, and
on the other hand you want to reclaim binsize/ram by making the
pitchscreen a list? Some (work-in-progress) targets are already short
on RAM (the clip has only 300K for example).
Seriously, you can't be this mathematically challenged - if the feature
can be enabled at all on Clip, then we can afford to have it permanently
enabled. If we can't afford to have it permanently enabled, then there's
not enough RAM to optionally enable it either.
I rather think we should go away from lists, instead of turning things
into it. The pitchscreen is a nice example how settings can be
presented in a more appealing way. Sure, it needs some polishing after
the timestrech commit.
The on/off can be preserved while still going away from the list,
reclaiming RAM without spending any. And the pitchscreen is a perfect
example of how overcomplicating both the controls and UI can happen when
the information can be presented in a much more user-friendly way.
"Appealing" loses to "usable" and "intuitive" every day of the week -
the pitchscreen is difficult to use and very unintuitive on several targets.
