Re: [yoshimi-user] 0.062-pre0

  • From: alex stone <compose59@xxxxxxxxx>
  • To: cal <cal@xxxxxxxxxxxx>
  • Date: Sat, 16 Oct 2010 19:24:29 +0400

On Sat, Oct 16, 2010 at 7:20 PM, cal <cal@xxxxxxxxxxxx> wrote:

On 17/10/10 02:07, alex stone wrote:
[ ... ]
I think the question i'd be asking is:

"All those who use nrpn regularly, put your hands up."

Then you'll get an idea if it's worth even bothering with it.

Not quite ... I've totally dropped nrpn. The question is, would it be
useful to expose various control functions by other means? If so,
which ones, and how best to go about exposing them?

One suggestion on LAU long ago was to be able to right click on any
given control and assign a midi controller to it. A real nice idea
perhaps, but if anyone even imagines that I might be coding that one
up, they are seriously deluded.

A simpler approach might be to assign and document a static table of
the mappings of enabled synth controls to their assigned midi control
messages?

Somewhere in between those two might also be good.

cheers.

------------------------------------------------------------------------------
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
_______________________________________________
yoshimi-user mailing list
yoshimi-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/yoshimi-user


So, playing to your strengths, a list, something like the MIDICC
equivalent of a keybinding shortcuts editor might be worth thinking
about? List all the CC's and let the user decide.

Alex.

--
www.openoctave.org

midi-subscribe@xxxxxxxxxxxxxx
development-subscribe@xxxxxxxxxxxxxx


Other related posts: