-
Notifications
You must be signed in to change notification settings - Fork 80
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
IS-08 - device channel mapping API endpoint #318
Comments
The API "selector" that IS-08 allows could help, but have you considered whether you would be able to use Output Routing Constraints to describe these routing restrictions even within one API instance? https://specs.amwa.tv/is-08/releases/v1.0.1/docs/4.0._Behaviour.html#output-routing-constraints |
Hi @garethsb , Thanks for the quick response. Yes we did that, and functionally I believe that with doing so it's all set, a controller can figure out what is and isn't allowed. With the request we are more considering the burden you would put on a controller to figure out the relations between inputs/outputs and their respective device (which requires iterating for each device towards senders / receivers and so on). |
Do you have feedback from any Controller vendors on this? Note that there's a hint of how this would be implemented here: nmos-cpp/Development/nmos/channelmapping_api.cpp Lines 44 to 49 in a0ff5f3
|
First of all thanks for the NMOS library, it is great work!
We are implementing NMOS for a node with many device(s), where each device can only route in/outputs within it's own device.
When looking in IS-08, there seems to be a perfect solution for this (IS-08 instance per device), however this isn't part of the library.
Would this be a feature which can be put on the backlog of implementation?
Thanks in advance.
The text was updated successfully, but these errors were encountered: