search

DVBProject / DVB-I-Reference-Client

DVB-I Reference Client being developed by Sofia Digital
MIT License
51 stars 20 forks source link

[Frontend] ContentAttributes support ? #53

Open bpeexc opened 2 years ago

bpeexc commented 2 years ago

Does the DVB-I reference client support DVB-I ContentAttributes , such as VideoConformancePoint element ?

Thanks in advance,

Benjamin

paulhiggs commented 2 years ago

No, the evaluation of specified ContentAttributes against device capabilities is not provided in the current release. Player capabilities need to be exposed to the application, but then it could become part of the service instance filtering algorithm.

juhajoki commented 1 year ago

We can add this to the backlog

paulhiggs commented 1 year ago

@bpeexc what would you expect from the DVB-I Reference Client if it were to example the ContentAttributes?

Should it disable any DASH delivered service instances that cannot be played in the <video> element?

How can the DVB-I application 'know' what the supported broadcast receiver codecs are?

jpiesing commented 1 year ago

Assuming we want the reference app to stick to standard HTML5 (and omit HbbTV extensions) then it might make sense to discard broadband service instances where MediaSource.isTypeSupported returns false.

paulhiggs commented 1 year ago

Yes, we would need to define a mapping between DVB classification scheme terms and type for isTypeSupported().

is there some equivalent of isTypeSupported for the video/broadcast object or would any 'unplayable broadcast services' be removed during channel scan?

jpiesing commented 1 year ago

is there some equivalent of isTypeSupported for the video/broadcast object or would any 'unplayable broadcast services' be removed during channel scan?

Normally the latter. Additionally, the broadcast codecs supported are listed in the XML capabilities as a list of elements whose value is one of those in either DVB VideoConformancePointsCS:2017 or a AudioConformancePointsCS:2017.

bpeexc commented 1 year ago

FYI, I implemented a lightweight version of ContentAttributes for the video/broadcast in my repository.

I use OIPF XML capabilities to determine the list of Audio and Video conformance points.

It works from many TVs, like Android TVs, Hisense or Panasonic.

However, it does not work on Samsung or LG devices because their XML capabilities seems to be incomplete (broadcast element is missing). Do you know if there are an other way to find the video/broadcast capacities ?

paulhiggs commented 1 year ago

I just stumbled upon the decodingInfo API which could be used in conjunction with <VideoAttributes> and <AudioAttributes> to determine if a service instance is playable.

jpiesing commented 1 year ago

I just stumbled upon the decodingInfo API which could be used in conjunction with <VideoAttributes> and <AudioAttributes> to determine if a service instance is playable.

It does look widely supported - https://caniuse.com/mdn-api_mediacapabilities_decodinginfo - although how accurate the answers are remains to be seen.