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

As I said, I am diving back into this after years not looking at content distribution but more content production.

There might something we could identify as being common to IP and broadcast: the MPEG transport stream.

Jean-pierre 

-----Original Message-----
From: François Daoust via GitHub [mailto:sysbot+gh@w3.org] 
Sent: lundi 14 novembre 2016 09:47
To: public-tvcontrol@w3.org
Subject: Re: [tvcontrol-api] Why retrieve a list of tuners instead of just one tuner?

Capturing the feedback  from @JPEvain [sent by
email](https://lists.w3.org/Archives/Public/public-tvcontrol/2016Nov/0037.html)
 (replies to notification emails are not automatically converted to GitHub comments):

[[
Thanks for updating the definitions.

1.  Introducing the notion of IP multicast may lead to different APIs to resolve the list of TVChannels available from these different types  of sources?

2. I would keep the definitions as generic as possible. The penultimate sentence looks like a repeat of what's being said in the second sentence.  I would keep the last sentence of the definition of TVSource out.

  - **TVSource**: a logical source of TV/Radio channels. This may represent a physical tuner or a "virtual" tuner for IP multicast. The TVSource exposes the list of TVChannel objects available through that source. For devices with more than one type of tuner (e.g. cable and terrestrial), each tuner type may be represented by a different TVSource. 

  - TBD: if associated to TVTuner: DVB Network and Multiplex, ATSC?? 

3. The definition of TVChannel -> DVB Service, ATSC??

  - **TVChannel**: represents a single TV or radio channel and provides metadata about it. A TVChannel objectis one among possibly several channels  available through one TVSource. If the same channel (e.g. VH1)  is available through two different sources (e.g. over cable and
terrestrial) then each TVSource will return a different TVChannel object.

4. Mediastream (if we want to reuse definitions)

  A TVChannel is consumed as **TVMediaStream** composed of one or more  MediaStreamTracks (audio, video, data, etc. -> DVB Components,
ATSC??) This can be passed to an HTML5 media  element to play the channel. A TVMediaStream is obtained from a TVSource, and when a TVMediaStream object is created it means that all  of the resources needed to receive and present that channel have been  successfully allocated. 

  To be rediscussed when we have progressed on the API?
 [[[[A TVMediaStream object may be re-used when selecting a different channel, to indicate that tuning and decoding resources currently used to present that TVMediaStream may be re-used for the new channel.]]]] 

5. TVProgram -> DVB Event -> ATSC??
A TVProgram is an editorial object available at a given time on a given TVChannel ]]

--
GitHub Notification of comment by tidoust Please view or discuss this issue at
https://github.com/w3c/tvcontrol-api/issues/4#issuecomment-260278959

using your GitHub account

------------------------------------------------------------------------------

**************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error, please notify the system manager. This footnote also confirms that this email message has been swept by the mailgateway
**************************************************

Received on Monday, 14 November 2016 09:00:38 UTC