19 Mar
2010
19 Mar
'10
6:56 p.m.
rosea grammostola wrote:
On Fri, Mar 19, 2010 at 12:32 PM, Philipp <hollunder(a)lavabit.com
<mailto:hollunder@lavabit.com>> wrote:
Excerpts from alex stone's message of 2010-03-19 10:09:04 +0100:
:)
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.
Alex.
--
www.openoctave.org <http://www.openoctave.org>
Thanks for telling us about this app Alex, it sounds like it could
become an important piece in the puzzle if cv gets more popular.
On the topic:
I think once jack_session is established and we have a well working
session management for every app automation is one of the things that
will need more attention.
There are other areas as well that will become more relevant:
- proper syncing, in all its forms
I agree about the fact that proper syncing (Jack Transport), is likely
even more important then automation for the modular approach, it has
it's limitations right now...