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

Add some Peer infos #14

Open
TonyVie opened this issue Sep 28, 2016 · 5 comments
Open

Add some Peer infos #14

TonyVie opened this issue Sep 28, 2016 · 5 comments

Comments

@TonyVie
Copy link

TonyVie commented Sep 28, 2016

Is it planned to add some more info about connected peers ?
(like their name, IP, ... whatever info they want to expose)

I would like to broadcast some more info between our mac and iOS app. It should be great to use link discovery to do that.

@fgo-ableton
Copy link
Collaborator

Thanks for the request. We have heard this before but there is no concrete plan yet.
To get a better understanding of what you would want:
What kind of information would you want to broadcast? Would that be usable by your apps only?
What would be a use case were you would want to know the name of an app?

@TonyVie
Copy link
Author

TonyVie commented Oct 9, 2016

I would like to broadcast some kind of key/value pair dictionary.
With standardized keys like: peer name, peer ip, peer bundleID, peer version, peer session/project name. Developers could also broadcast custom key/values.

I would like these informations to display a more friendly jam session status.

And bundleID/IP more specificly to use link's discovery. Then open a second network line to exchange custom messages between our apps.

@jbloit
Copy link

jbloit commented Jan 10, 2018

Hi,
I'm reviving this post as I'm also interested in this request.

Here's my use case: I have is an education orchestra app that has 2 modes, either player or "conductor". The players' start times are synced through Link. The "conductor" is a monitoring mode that allows to display some of the players' parameters sent through OSC.
Currently, the conductor can't keep a record of which players are part of the Link session. It has to maintain its own session state through an additional OSC protocol, which kind of looks like un-necessary duplicate traffic, given that some kind of session object is likely being setup and updated within Link. It would be very handy if I could access at least the hostnames of the devices in the current session.
And as @TonyVie mentioned, if we additionally can broadcast custom key/values, that's even better.

Cheers

@luzpaz
Copy link

luzpaz commented Jul 27, 2023

Any traction on this ?

@fgo-ableton
Copy link
Collaborator

This is still out of scope.

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

No branches or pull requests

4 participants