Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cummunicate with other RemoteScripts #22

Open
juschu opened this issue Jan 24, 2015 · 2 comments
Open

Cummunicate with other RemoteScripts #22

juschu opened this issue Jan 24, 2015 · 2 comments

Comments

@juschu
Copy link

juschu commented Jan 24, 2015

Does someone know a way to communicate with other RemoteScripts?'
Lets say I have one script for my Launchpad and one script for my Behringer BCR. When I move the session rectangle on the Launchpad, I want the BCR to know which channels it should control.

I'm not sure, but I think when I worked with the Live API in Live 8, there was an API function like "Live.Application.get_other_remote_scripts()" which returned a list of all the registere remote scripts.
But now I don't find anything like that.
The last, but not my favorite solution would be to communicate over TCP to localhost.

@alandrees
Copy link

https://github.com/alandrees/RemoteScripts

That repository has some of the code you're looking for. I built a bit of an event callback system to faciliate inter-script code (the ableton plus stuff).

That code was supposed to do exactly what you're looking to do. The only thing I didn't get to was writing in the functionality to encode parameters to be automatically bound on channel select (so I could pre-define a set of 32 parameters to control with grouped encoders on the top of the BCR2000).

The code is old, and only tested with Live 8, but the AbletonPlus stuff should work (I wrote it to be a generalized callback/event system).

@juschu
Copy link
Author

juschu commented Jan 26, 2015

Thanks, that really pointed me into the right direction: Static members in a custom base class.
Now I'm feeling a bit stupid, because static members are not really a new concept to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants