lemur OSC - baby steps - triggering clips, how to?

Bro, does your rig even lift?
Post Reply
muchachotron
Posts: 4
Joined: Wed Jun 23, 2010 21:32

lemur OSC - baby steps - triggering clips, how to?

Post by muchachotron »

i feel pretty dumb that i cannot figure this out, but i am totally green to programming osc and i humbly beg for assistance.

trying to build up my own custom resolume 3 controller with a lemur and osc, and though i've read the resolume docs many times, i am unable to grasp how to have a lemur pad or switch trigger a clip to start playing in resolume. i'm leaning toward a row of switches for each corresponding resolume row (arbitrary row lengths, but likely maxed out at 10 per row), as each would remain lit after triggering, which seems useful even though it isn't true feedback from resolume.

can anyone give me a hand with the correct parameter/script syntax for assigning a row of lemur pads or (preferably) a switches to trigger resolume clips? while i could resort to using the daemon to transmit via midi instead of osc, i'm thinking this is a good time to catch up on osc as it is becoming more relevant to the masses. i'd like to build the controller purely in osc if possible.

trying to wring out as much usefulness in the lemur as i can before it is completely abandoned.

muchachotron
Posts: 4
Joined: Wed Jun 23, 2010 21:32

Re: lemur OSC - baby steps - triggering clips, how to?

Post by muchachotron »

i wanted to clarify that i am able to successfully connect and communicate via osc from lemur to resolume, i just don't understand how to map lemur buttons to resolume clips using osc.

i can, for example, map a lemur fader to the opacity of a layer or a clip and have it respond nicely, using (on a fader):

/layer3/clip1/video/opacity/values

but the proper way for a row of pads/switches to trigger clips in resolume eludes me...

muchachotron
Posts: 4
Joined: Wed Jun 23, 2010 21:32

Re: lemur OSC - baby steps - triggering clips, how to?

Post by muchachotron »

update

i found this post:
http://www.resolume.com/forum/viewtopic.php?f=13&t=7919

in which edwin noted:
To find out the address of an ui element, enable mapping (midi or key) and click on a highlighted element.
If you enabled OSC in the preferences you will see a label at the bottom of the mapping panel that shows the address of the highlighted element.
this helped me understand the paths better, so i was able to map a lemur button to:
/layer3/clip1/connect

sending a 1, it triggers the resolume clip! weee!

on to mapping rows of these to corresponding cells now. i've just been using the lemur osc mapping field thus far for targeting, looks like i'll need to do some scripting now to handle multiple button/switch presses within a group, yeah?

premiermalvado
Posts: 18
Joined: Sat Oct 17, 2009 16:06

Re: lemur OSC - baby steps - triggering clips, how to?

Post by premiermalvado »

SORRY ABOUT using this thread, hoping more people will see it from the beginning.


I've managed to successfully connect my iPad and resolute via wireless lemur.

so far i have been able to assign everything to mi template but im stuck now. perhaps someone can help me with my syntax.

im trying to assign individual buttons to global direction.

I've tried so far the following routes with no success. being X 0,1,2 or 3

/composition/directionX
/composition/direction/X
/composition/direction/valuesX
/composition/direction/values/X

should i be using () or [] for the values????
im wondering it could be lemur editor problem because it converts /composition/direction X to /composition/directionX (removing any spaces) ......

any ideas.


im working on a template similar to resolumes gui and will be posting it happily after completion


thanks in advance

HerrNieDa
Posts: 467
Joined: Thu Oct 02, 2008 09:30

Re: lemur OSC - baby steps - triggering clips, how to?

Post by HerrNieDa »

i postet my interface here... so the work should be almost done ;)
viewtopic.php?f=5&t=9345

hope it helps....
MainSys: Z77 UP5,3570K,32GB Ram,GTX 285, M3 128GB,4x3TB R5@LSI9750
VJSys 1: 990FX UD5,X6 1045T,16GB Ram,GTX970+610+610,M3 128GB,3x1TB R0
MBP 3.1; Schenker A102 (650m) & P702 (675m)

Post Reply