-
-
Notifications
You must be signed in to change notification settings - Fork 514
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
Streamdeck neo: utilise lcd strip #2854
Comments
I guess it still is the single screen of the original Streamdeck under it. So what is the resolution of the strip? Half a button height? |
Its 248x58, and does not support presses or any interaction. I am tempted to do similarly to the plus, and scale and draw the 2 buttons it spans. but of course that won't give the best look, it will be using less than half of the width. But yes long term something from #2387 can be done, but I guess we arent in a place to do that yet |
It would be great to have an OSC address you could send a text string to to be rendered out (Countdown clock from a media server), or just have a way to make it a clock or assign a name or station name to it (text block) . Beyond that, I'm not sure If I could use it for anything else. |
This was explained on slack, this is specifically referring to when those buttons contain a page up/down button, as they always have a black background resulting in the buttons being left dark. This is a separate thing to look into.
The challenge here becomes whether that will be enough or will it need to be able to vary depending on which page is being viewed. And what about users who have multiple streamdecks, they will likely want each one to show something different. There is also the question of how that should work when connected through satellite. And looking forward, how would we fix things up for users once this is fed from the grid? We would have to leave this special osc address, but then what should it be doing to affect the display as intended. This doesn't mean we shouldn't do this, but there is a large question of whether it is a good idea to do something quick and easy, which would either result in a lot more effort to link up to the full solution, or will break users workflows when the full solution is done (breaking it may not be that bad considering the alternative is to not do anything until the full solution) |
Is this a feature relevant to companion itself, and not a module?
Is there an existing issue for this?
Describe the feature
The first implementation of support for the neo does not make use of the lcd strip.
It needs some thought on how the two companion buttons it spans should be drawn to it
Usecases
No response
The text was updated successfully, but these errors were encountered: