Open bquinn opened 4 months ago
@bquinn @himslm01 discussed on today's session. Brings up the in the URL or in the attributes (or both) conversation again and Mark's kindly going to ask if the URL is acceptable for the technical parameters above or if there's a value in them being broken out into attributes of the rendition.
The feedback I got was that some of the properties naturally fit in the url, such as the stream id, but some don’t naturally fit.
For example from the feedback, max bitrate and min latency are more meta. They calibrate the SRT process.
It was suggested that a good process flow should enable a process to lift a URL as is without any processing and drop in to a SRT application.
The thoughts we that max bitrate and latency need to be provided outside of the URL. And an SRT application could assume some default values for these and/or validate values.
From the feedback, we can imagine a world where max bitrate forms part of a negotiation between a sender and receiver to manage network capacity. Or is calculated with properties of the renditions intended to be passed around.
Word doc shared by @amitesharqiva :
DPP LPX Flow Parameters v1.docx
Quick summary of parameters needed (highlighted fields from word doc):