You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
Is this a feature relevant to companion itself, and not a module?
Is there an existing issue for this?
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
The text was updated successfully, but these errors were encountered: