[LAU] Editing zynadsuxfx/yoshimi patches?

[S. Massy]

On Tue, Apr 19, 2011 at 08:24:55PM -0400, Paul Davis wrote:
> On Tue, Apr 19, 2011 at 7:37 PM, S. Massy <lists at wolfdream.ca> wrote:
> > On Wed, Apr 20, 2011 at 12:34:24AM +0200, Julien Claassen wrote:
> >> Hello!
> >>   OK, then I think I'd prefer it the Bristol way. Basically that
> >> kind of Vi-interface and an optional commandline. I suppose this
> >> kind of interface is so handy, one should endevour to write a small
> >> library for it. Something C++ based perhaps, that can easily be
> > Yes, we've agreed on this point before: it's a wonderfully flexible
> > compromise, allowing what needs to be commands to be so, and what needs
> > to be key-stroke controled to be so as well with minimal waste of time.
> 
> i tackled a version of this problem nearly 10 years ago when i did the
> KSI (key stroke interface) front end for ardour, which used a purely
> text-based interface to control an early version of ardour (including
> plugins). at the prompting of frank carmickle, who was paying for the
I remember, I tested it briefly, but it must have been at its inception
or soon after, because it was too unstable to really do anything with,
so I stuck with ecasound.

> work, we adopted a heirarchical structure that also involved
> scrolling, with 10 items per page at any time. so for example to get
> to the 21st parameter of a given plugin, you'd navigate *down* a tree
> (from the mixer to the Nth track to its plugins to the Nth plugins and
> then scroll twice, and then use the control for the 1st item on that
> "page". it worked extremely well, and i regret that we never adopted
> the model for the GUI version of ardour in some deeper way.
Yes, tree structures, especially with coherent numbers can be very
efficient. By the way, I believe this kind of interface design is not
just useful for blind people, I'm sure a lot of users need to manipulate
data as quickly as possible and don't necessarily want to muck about
with the mouse. 

I just had this wonderful idea: what if parameters were searchable? For
example, suppose one wants to change the envelope release time, one
could hit "/" to bring up a search prompt and type "envel release" and
hit enter, then the cursor would already be on the first matching
parameter, if there were several matches, one could hit "n", just like
in vi to go to the next match. This could significantly speed up the
editing process.

Cheers,
S.M.


--