Ableton Live + D::Light

Dear community,

I would like to share a MaxForLive patch that I have done in order to control Ableton Live with :Light.

I needed to fire a scene in Live Ableton when :Light received a Go instruction so that both Live and :Light would stay “synchronized” whatever I go forward or backward in the light sequence.

I first tried to use midi but I wasn’t so happy with it since it's not that flexible and required to setup each midi note/action (I may missed a point here?!). So I decided to design my own OSC/UDP patch using MaxMSP.

The present device will allow you to receive the firing information sent by :Light through UDP and OSC protocols. It can for example jump from step 2 to step 13 or from step 34 to step 5.

The device should be able to receive fire instructions from any other software. By default its listening port is 7001 but you can easily change it.

You can download it from here: www.maxforlive.com/library/device/2836/udpscenesfire

Suggestions are welcome.

Hi Leny,
Thanx for sharing your work!
I don't do MAX especially... so I won't give you feedback about that...

in the upcomming release, I've added 'StepID' to give steps an identification. It's requiring integer or float number as ID.
It intends to be useful (at least) when the same cue is present several times.

so maybe you can add this feature to your external...

++

Hi Sl1200mk2 !

In my external, I’m just waiting for the “seq/go x” instruction. I’m not using any Cue number. What would be the difference between “seq/go” and “stepID”? Is there any documentation I can read about that?

As I’m quite new to :Light I may not have a good overall view of the system. Is OSC more convenient that MIDI? Is my MaxForLive device really useful?

One last question: English or French language on the forum?

Thanks,

hey Leny,

In my external, I’m just waiting for the “seq/go x” instruction. I’m not using any Cue number. What would be the difference between “seq/go” and “stepID”?

in the setup of new versions you can choose what kind of message is mapped to /seq/go. either cues or step number.
I don't think that StepID are exported though... (at least not yet)

Is there any documentation I can read about that?

unfortunately not... I don't have time right now for that

As I’m quite new to :Light I may not have a good overall view of the system. Is OSC more convenient that MIDI? Is my MaxForLive device really useful?

OS is a killer!!

One last question: English or French language on the forum?

both and other language are welcome

++

Hi Leny
First of all
Thx and bravo for your work
It will be very useful to have a TRUE Synchro between DLIGHT and Live
Allowing you to go forward and back in the sequence and to be still synchronized.
So:
I downloaded your UDP Fire scenes Patch
I'm trying to make it work.
I set OSC reader in D light with the ip address of my live dedicated computer '192.168.1.41'
DLight computer IP is '192.168.1.40'
i see some message passing in your patch when i run the cues in Dlight, but i don't know what to do
Some Questions below:
a)Do i have to set a fire wall parameter in live to open the port 7001?
b)In your patch it's written
go/sec
and when i launch Osculator to read the UDP receive i see
go/seq
Is it a problem?
c)Can you give me some tricks to set your patch
-How do you set the trigger in your patch:
For example:
When i run the the cue 50 in Dlight, i would like to run scene 4 in Live
what should i do


Thx to keep time answering
best
x.