16 Jan
2004
16 Jan
'04
4:31 a.m.
--- Iain Duncan <iainduncan(a)telus.net> wrote:
This is what AMS, SSM, gAlan, PD etc let you do right now - MIDI is converted
to a 'voltage' signal (by various means) and then routed to plugins in the
graph. Ditto JACK - you can connect a JACK port to anything you like in these
apps.
I don't think this kind of I/O is best implemented internally as a plugin
either (definitely not if plugin == LADSPA). It's better if it's provided by
the host as a bus or other metaphor.
-
Myk
________________________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping"
your friends today! Download Messenger Now
http://uk.messenger.yahoo.com/download/index.html
That would be
possible, but using JACK between *every* plugin in the
graph would be overkill. JACK support is definitely a requirement
though.
Well, it might be, but on the other hand making that possible would allow
the truely open ended flexibility possible with a hardware modular. If the
project is limited to midi control, the resolution of control signals is
forced into being very low. Being able to use use either a Jack/CV input or
a midi CC to control a paramater would be pretty cool. Plug ins wouldn't
have to be able to do everything, they could be used to do only one or two
things really well, and one could freely mix oscillators, filters, and other
processors to make complex patches.