Re: [tvcontrol-api] Why retrieve a list of tuners instead of just one tuner?

We probably need to keep some notion of "tuner" in the specification, 
even if from an application or API level we are not binding channels 
directly to it.
The "dynamic tuner model" was added primarily to support USB type 
tuner devices (which is something we need to continue to support). 
When a tuner is added, a channel scan may need to be performed 
depending on when that tuner was last used. 
Consider a STB with some built in tuner (s). The user would have 
initiated a channel scan at some times and have a channel list in NV 
memory. If a USB tuner that has never been used is connected, then 
there would be no change to the channel list. A scan could be 
initiated through a native menu/application, but that beaks the 
uniformity and consistency we look to solve.

I am not sure how other W3 specs handle dynamic hardware, such as the 
attachment and removal of peripherals. Perhaps we need some peripheral
 category (i.e. "broadcast-tuner") that triggers some capability 
change notification in our API.

-- 
GitHub Notification of comment by paulhiggs
Please view or discuss this issue at 
https://github.com/w3c/tvcontrol-api/issues/4#issuecomment-277267925 
using your GitHub account

Received on Friday, 3 February 2017 14:58:35 UTC