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

Differentiate between devices #35

Open
jasonmf opened this issue Jun 14, 2024 · 2 comments
Open

Differentiate between devices #35

jasonmf opened this issue Jun 14, 2024 · 2 comments

Comments

@jasonmf
Copy link
Contributor

jasonmf commented Jun 14, 2024

Is there a way to differentiate between devices?

I'm developing an OBS overlay to display the currently playing track in each channel. On the Prime 4(+) I get messages with state names /Engine/Deck[1-4]/.*. so from that device I can easily differentiate the four channels. From a pair of SC5000 I get messages from them both and they're each sending /Engine/Deck[12]/.*, so purely parsing the state name isn't enough.

For a given session, I can differentiate between devices by IP address, but between sessions the devices may get different addresses via DHCP. I'd like to get some durable identifier that I can combine with the Deck. portion of the name to keep the channel ordering consistent in the overlay. I can potentially use ARP to get the MAC address associated with the device's IP and use that, but it would be nice if there were something directly in StagelinQ.

@icedream
Copy link
Owner

icedream commented Jul 11, 2024

I assume since they're all SC5000 devices they also transmit with the same device name, so that's not something that could be used. Really, the only thing that would technically be different (that the library has access to right now) is probably the connection the data is coming from and the device token that was presented before building said connection - and I'm not even sure if that device token changes every now and then as well.

Might need a bit more of a think about that.

@honusz
Copy link

honusz commented Jan 23, 2025

I believe the GUID (aka token) is unique to the device and permanent. IIRC it's actually printed on the label on the device itself. It's absolutely the best way to perpetually identify a specific device

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

3 participants