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

Dual Streamdeck Use #3004

Closed
2 tasks done
JarodShowstream opened this issue Aug 26, 2024 · 2 comments
Closed
2 tasks done

Dual Streamdeck Use #3004

JarodShowstream opened this issue Aug 26, 2024 · 2 comments
Labels
Question Further information is requested

Comments

@JarodShowstream
Copy link

Is this a feature relevant to companion itself, and not a module?

  • I believe this to be a feature for companion, not a module

Is there an existing issue for this?

  • I have searched the existing issues

Describe the feature

I understand you can use as many surfaces as you want with companion, but the use of page up and down arrows control all the surfaces. Without rebuilding every page to use custom page up and downs, will it ever be possible to run two streamdecks with independent control, currently i do this with a second laptop and port forwarding.

Usecases

This would allow multiple operators to work on the same PC and not potentially interfere with each others surfaces

@Julusian
Copy link
Member

The page up and down buttons only affect the current surface, unless you group the surfaces in the surfaces tab then all of that group are affected.

Additionally, the elgato plugin counts as one surface because the streamdeck software doesn't give any unique identifiers for us to use.

So it sounds like you are using the plugin, instead of connecting streamdecks directly? If so then this is expected behaviour and there isn't anything we can do about that

@Julusian Julusian added the Question Further information is requested label Aug 27, 2024
@Julusian
Copy link
Member

Im going to close this for now, as this sounds like it isn't a bug or missing feature. But if that changes it can be reopened

@Julusian Julusian closed this as not planned Won't fix, can't repro, duplicate, stale Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants