Open TheAndi opened 1 year ago
, I hope it shouldn't be much work to allow them to have different ports?
Hyperion Instances are to be read as Hyperion LED-Device instances, i.e. you can currently have multiple output instances. Currently, you can have only one screen-grabber, one USB-grabber, one flat-/probuffer source as input to LED (output) instances. Only for Bob-light, you could have one port per instance.
Due to this design limitation, you cannot setup a mapping matrix between multiple grabbers/input of the same type (besides Boblight) today. Your requirement is understood and reasonable, but it is much work, as it would require a redesign of input sources and is not planned currently.
Thanks for the reply! I feared that it's not that separate after all. If you need a Beta-Tester in the future, let me know ;) Still glad to see Hyperion evolving today since I first started using it in 2014!
Feature request
I opened a similar issue back in 2020 (#747) about the JSON port, but the issue also applies for all the other interfaces. As this does not seem to be solved/addressed by #809 I'll give it another try, as I am current working on some new LED projects.
What problem does this feature solve?
Being able to control multiple instances separately by having dedicated ports for them. This would allow using all the companion apps (Android App, any SreenCap, Kodi, ...) to be setup for their specific instance, which is unfortunately still not possible. E.g. using HyperionScreenCap to stream to the second instance only (correct me if there's a way around).
How should this be implemented in your opinion?
Allowing to specify the instance (like in "Remote Control" or "LED Setup" menus) before setting the Port for JSON, PROTO, Flatbuffers. This could be done in the same dropdown way as in the other menus, which are instance specific. So this "instance dropdown" could be added to the "Network Services" menu.
Regarding "Token Management" and the API "Network" section: I don't know how independent the separate instances really are and if they allow different settings per instance. If not, they could just stay there with the text saying that they apply for all instances no matter the dropdown setting or the "Network" menu could be split in two subsections: general or API and (instance specific) Port-Settings. What do you think?
Are you willing to work on this yourself?
Unfortunately, I am not familiar with the internals of Hyperion to be able to quickly fix/edit this, but I gladly test some new implementations. If these hyperion instances really are running quite independant , I hope it shouldn't be much work to allow them to have different ports?
In the end I just want to stream a network grabber to a second instance only (let me know if there's an easy way exept swapping the instances), but I keept the issue more general, so that this could enhance more applications e.g. using the non-official android app to controll instances separatly.
Thanks a lot in advance! Feel free to respond in german if that speeds things up.