28 Oct
2008
28 Oct
'08
11:36 a.m.
Hello all,
Would there be a simple way to import plugin
automation data into an Ardour session ?
'Simple' may include writing some software, but
not any major project :-)
The situation I want to handle is this:
We have a Csound, SC3, PD, program generating
a number of audio signals, and also simple
OSC commands that would control external
processing of these signals, e.g. surround
panning or movement implemented by an
external system.
The signals each become a mono track in Ardour,
while the OSC controlled parameters are stored
as automation data for a LADSPA plugin in each
track. On playback, the plugin just sends this
data to the external application.
The whole point is to combine a number of such
compositions into a single Ardour session that
can be looped without any user intervention.
Ciao,
--
FA
Laboratorio di Acustica ed Elettroacustica
Parma, Italia
Lascia la spina, cogli la rosa.
28 Oct
28 Oct
12:32 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Fons Adriaensen wrote:
Hello all,
Would there be a simple way to import plugin
automation data into an Ardour session ?
'Simple' may include writing some software, but
not any major project :-)
both ardour track and plugin automation data is stored in text files,
named after 'projectname-plugin-trackid.automation'. The First line is
"version <num>" each line thereafter
<type> <timestamp(in samples)> <value>
The only valid type is 'g' corresponding to gain_automation_curve() see
libs/ardour/io.cc:1715 - it seems like plugin-automation use LADSPA-port
numbers as type; but I have not verified that in the source.
http://code.google.com/p/noisesmith-linux-audio/downloads/detail?name=lados…
offers both an OSC input and output as LADSPA plugin.
The situation I want to handle is this:
We have a Csound, SC3, PD, program generating
a number of audio signals, and also simple
OSC commands that would control external
processing of these signals, e.g. surround
panning or movement implemented by an
external system.
Last June I set up a system like this;
http://mir.dnsalias.com/oss/panjack/ is a small JACK c-program that
processes external input (either MIDI or OSC) to pan audio sources. I
had 6 audio-inputs to 10 speakers and up to 12 parameters for panning
(either angle and width or X/Y coordinates) - PD did not manage to run
that in realtime but I'm sure I could have optimized the sqrt()s. Since
we had live audio sources and not only playback, I eventually ended up
mixing it live (with a BCF2000 and panjack) rather than automating it
with ardour.
The signals each become a mono track in Ardour,
while the OSC controlled parameters are stored
as automation data for a LADSPA plugin in each
track. On playback, the plugin just sends this
data to the external application.
yes, works like a charm with a little random latency due to UDP.
There are a few minor issues to consider: when moving the playhead in
ardour you can skip over OSC commands and a badly designed receiving
application may end up in a wrong state.
The whole point is to combine a number of such
compositions into a single Ardour session that
can be looped without any user intervention.
so you're looking for an OSC-sequencer with jack-transport control.
maybe turn it around: have PD control ardour ?!
2c,
robin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkkHMHwACgkQeVUk8U+VK0KMSwCfepXCsT0CfOqN6Q+Pe+OHT3Qy
y5YAnjaotL4xTfR3LIOuJndufNK3yo9f
=lzXg
-----END PGP SIGNATURE-----
1:06 p.m.
On Tue, Oct 28, 2008 at 04:32:15PM +0100, Robin Gareus wrote:
both ardour track and plugin automation data is stored
in text files,
named after 'projectname-plugin-trackid.automation'. The First line is
"version <num>" each line thereafter
<type> <timestamp(in samples)> <value>
The only valid type is 'g' corresponding to gain_automation_curve() see
libs/ardour/io.cc:1715 - it seems like plugin-automation use LADSPA-port
numbers as type; but I have not verified that in the source.
Interesting, I'll start experimenting with that.
http://code.google.com/p/noisesmith-linux-audio/downloads/detail?name=lados…
offers both an OSC input and output as LADSPA plugin.
The problem here is that whatever the plugin
inputs is not seen or recorded by Ardour
(or I must be missing some very clever trick).
yes, works like a charm with a little random latency
due to UDP.
In this case there's no delay - the plugins have a shared
memory interface to the application they are controlling.
OSC could be used as input (i.e. recording automation), if
I can make Ardour use this instead of the GUI elements it
creates for the plugins.
Thanks for the ideas !
--
FA
Laboratorio di Acustica ed Elettroacustica
Parma, Italia
Lascia la spina, cogli la rosa.
1:14 p.m.
On Tue, 2008-10-28 at 16:58 +0100, Fons Adriaensen wrote:
On Tue, Oct 28, 2008 at 04:32:15PM +0100, Robin Gareus
wrote:
its also not true anymore.
all automation is inlined inside the session XML file these days.
simplest thing is to create a super-simple test session, add 1 plugin
with 2 params, record some automation for both, inspect session file.
--p
both ardour track and plugin automation data is
stored in text files,
named after 'projectname-plugin-trackid.automation'. The First line is
"version <num>" each line thereafter
<type> <timestamp(in samples)> <value>
The only valid type is 'g' corresponding to gain_automation_curve() see
libs/ardour/io.cc:1715 - it seems like plugin-automation use LADSPA-port
numbers as type; but I have not verified that in the source.
Interesting, I'll start experimenting with that. 
5:28 p.m.
On Tue, 2008-10-28 at 15:29 +0100, Fons Adriaensen wrote:
Hello all,
Would there be a simple way to import plugin
automation data into an Ardour session ?
You could assign a midi CC to the automated parameter. Then feed the
parameter changes through midi and use write mode automation to record
in the movements into ardour.
Sampo
5865
days inactive
5865
days old
linux-audio-dev@lists.linuxaudio.org
4 comments
4 participants
participants (4)
-
Fons Adriaensen -
Paul Davis -
Robin Gareus -
Sampo Savolainen