Overconstrained tracks

Currently, the settings proposal includes a mechanisms where settings
changes and external events that cause a track to become
"overconstrained" also cause the track to be muted.

As we discussed at the meeting, I think that the track should continue
to flow in these cases.  In the case that new settings were not
successfully applied, there should be no change to the constraints on
the track and the event will indicate which of the settings caused the
problem.  In other cases, where external factors trigger the event,
the characteristics of the track might change, (not discussed) and the
event might indicate which of the existing constraints are no longer
being met.

If the application cares about having constraints being absolutely
mandatory, then it can listen for the overconstrained event and stop
using the stream.

--Martin

Received on Wednesday, 6 February 2013 16:41:03 UTC