On Tue, August 9, 2011 08:53, Aurelien wrote: > Hi all! > > Just to precise, Jeremy and I are working together in Sebkha-Chott, the > setup he's talking about below, is the one we use on stage with that > band. > > On Mon, Aug 08, 2011 at 10:07:14PM +0200, [email protected] wrote : >> On Mon, August 8, 2011 12:59, jeremy AMMD wrote: >> > Hi! >> > I use OSC instead of midi to send clips and effects. It's pretty cool! >> > But I don't know how to enable/disable the effect parameter for the >> Flippo >> > effect. >> > What is the OSC command to activate the parameters of this effect? >> > Thanks. >> > >> >> >> See here: >> http://openmediacontrol.wetpaint.com/page/LiVES+commands >> >> /effect_key/nparameter/value/set,<int key>,<int nparam>,<value> > > Yes, OK, that's what we're using to write our OSC syntax. > >> >> This will only work for numerical (n)parameters (either float or int >> type). >> <key> is the effect key which the effect is bound to, it must be the >> currently active mode. nparam is the index of the parameter (starting >> from >> zero) of simple (i.e single valued) numerical parameters. >> >> >> >> /effect_key/parameter/value/set,<int key>,<int param>,<value> >> >> The same as above, except that the index is of all parameter values, >> though currently only int, float and color types are supported. > > > Hmmm. There was some point not so clear for me. We finally didn't use > "nparameter" at all, so that we might write some generic bindings and > OSC-generating rules. It's not a problem to use "parameter" only? > What is the focus/advantage of using "nparameter"? >
that's a good question - nparameters includes only those parameters which take a single value and which have a type of int or float (so any parameters with a type color, string or boolean are skipped, as well as any parameters which take an array of values). In addition I think it will skip any parameters which require resetting the plugin when the value changes. >> >> >> The next version of LiVES (1.4.6) will support setting of string and >> boolean types too, as well as querying the current value(s) and >> parameter >> name and type. > > OK, I've installed on a dev machine, I'll try this very soon. > Well, its still in development as we speak. There are also various complications with these types - string has a maximum length (either 1024 or 4096, i forget which) and needs to be in utf8 format; colour can either be type int (0 - 255) or float (0. - 1.) so you need to check the max, it can also have 3 values (RGB) or 4 (RGBA), so you need to count the number of elements in the default; and boolean can be part of a group (like radio buttons) so if you set a boolean, it may reset other booleans as a side effect (you need to check this). Also some parameters require the plugin to be reset when the value changes (for example a mode parameter), and you can only change the value of these when the effect is inactive. > >> >> Right now for numerical paremeters you can also get the min, max and >> default values. > > OK, this is very useful, combined with mididings, one can write very > automatic rules, that's very nice! > Yes that was the idea. Once you can also get the type, name and current value it should be even more useful. > > One question, and one kinda bug report: > > - As OSC don't seem to be completely finished on LiVES, I suppose you > (Gabriel) aren't using it to control LiVES as a VJ. IIRC, when I first > contact you to use midi, you told me you were not using MIDI at all. > So, my question: what kind of interface are you using to control > LiVES? > (computer) keyboard mainly, although since then I bought a Korg nano which I use for experimenting with. > > Bug Report (speaking about Lives 1.4.5 here): > > When both selecting and retriggering several clips through OSC[1], the > retriggered one is not triggered. This occurs when using > '/clip/retrigger', or with '/clip/select' + '/clip/goto', 1. > If I trigger the clip once it's been selected for a quite a time, it > works better (the retrigger action occurs something like 3 times on 4). > When all clips are retriggered, everything seems to work fine (100%). > > > [1] Let 0, 1 and 2 be 3 video clips. > send_osc 9999 '/clip/select' ,i 0 > send_osc 9999 '/clip/select' ,i 1 > send_osc 9999 '/clip/retrigger' ,i 2 > I'm not sure, I will have to check it out. Please can you log this as a bug at http://sourceforge.net/tracker/?group_id=64341&atid=507139 Gabriel. ------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Lives-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lives-users
