cristian-recoseanu

There is a precedent for this in the BCP-004-01 whereby it links directly to the NMOS Parameter Registers https://specs.amwa.tv/bcp-004-01/releases/v1.0.0/docs/1.0._Receiver_Capabilities.html#defining-parameter-constraints

Here is a link to at least one python MQTT broker library [https://hbmqtt.readthedocs.io/en/latest/references/broker.html](url)

@brucardoso2 You can prevent the AppArmor policy from affecting your container in this case by running it with --privileged modifier. I'm stuck one step further than you. I successfully mount...

Is the change as simple as merging the two sentences: > Clients performing requests using these methods SHOULD correctly handle a 301 (Moved Permanently) response by following the redirect in...

Previous discussion offered some options regarding possible values: https://github.com/AMWA-TV/is-04/issues/173#issuecomment-873097737. Also, as previously mentioned https://github.com/AMWA-TV/nmos-testing no longer performs checks on grain_rate for audio Flows.