19 Mar
2010
19 Mar
'10
6:56 a.m.
On Fri, Mar 19, 2010 at 12:47 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
On Fri, Mar 19, 2010 at 10:09 AM, alex stone <compose59(a)gmail.com> wrote:
Rosea, go to your jm2cv dir, and look for example.cfg. It's a text
config file, and will give you an idea of how to build your own config
file. (Let's call it rosea.cfg)
Then simply start jm2cv with:
$ jm2cv /where/you/put/the/config/called/rosea.cfg
--
www.openoctave.org
midi-subscribe(a)openoctave.org
development-subscribe(a)openoctave.org
Incidentally, there is an excellent app called jm2cv that does a good
job of "converting" cv data to jackmidi (and vice versa) written by
Peter Nelson. (See the non-mixer webpage for details)
So if your particular app of choice has midi out for automation, you
can direct it to a CV in port for, as an example, fader control in
non-mixer.
Just start jm2cv, and ports in and out of it in your favourite patchbay.
Simple stuff.
When I start jm2cv I got
Usage: jm2cv <config>
so the question is, how to start and use it exactly.
Regards,
\r