Mattijs Kneppers
2011-12-19 12:05:26 UTC
Hi all,
I'm about to do some work on my LiveGrabber plugins, plugins for Ableton
Live that send Live parameter values to OSC destinations, for example to VJ
software.
Now I'm facing the following question and I'm curious about your ideas:
what is the best convention to present for address naming in these plugins?
Option 1:
The addresses I send represent the Live parameters they originate from (see
Loading Image...
). This results in messages like:
/MyLiveSet/Bass 0.45
/MyLiveSet/Presence 0.87
Option 2:
The addresses I send represent the parameters they are supposed to control
(see Loading Image...
). This results in messages like:
/RedOffset 0.45
/Brightness 0.87
I'm curious how you would apply the available ideas about address naming to
this practical issue.
The reason why I'm so concerned with this is that it will determine the
system I will promote in demo movies and the way interface choices might be
made in the future. For example when Live should be controlled with OSC,
the other way round. Or when adding support for various destinations that
may (VDMX) or may not (Resolume) support changing the addresses of their
parameters.
By the way I remember seeing a discussion or an article about this some
time ago on this list, but I can't seem to find it. If anyone knows what
I'm taking about, could you send me the link?
Thanks for any thoughts!
Mattijs
I'm about to do some work on my LiveGrabber plugins, plugins for Ableton
Live that send Live parameter values to OSC destinations, for example to VJ
software.
Now I'm facing the following question and I'm curious about your ideas:
what is the best convention to present for address naming in these plugins?
Option 1:
The addresses I send represent the Live parameters they originate from (see
Loading Image...
/MyLiveSet/Bass 0.45
/MyLiveSet/Presence 0.87
Option 2:
The addresses I send represent the parameters they are supposed to control
(see Loading Image...
/RedOffset 0.45
/Brightness 0.87
I'm curious how you would apply the available ideas about address naming to
this practical issue.
The reason why I'm so concerned with this is that it will determine the
system I will promote in demo movies and the way interface choices might be
made in the future. For example when Live should be controlled with OSC,
the other way round. Or when adding support for various destinations that
may (VDMX) or may not (Resolume) support changing the addresses of their
parameters.
By the way I remember seeing a discussion or an article about this some
time ago on this list, but I can't seem to find it. If anyone knows what
I'm taking about, could you send me the link?
Thanks for any thoughts!
Mattijs
--
arttech.nl | oscseq.com | smadsteck.nl
arttech.nl | oscseq.com | smadsteck.nl