search

Dash-Industry-Forum / DASH-IF-IOP

DASH-IF Interoperability Points issue tracker and document source code
32 stars 7 forks source link

Updates for E-AC-3 and AC-4 for v5 #268

Open rdoherty0 opened 5 years ago

rdoherty0 commented 5 years ago

Minor updates to E-AC-3 and AC-4 codecs for v5:

  1. Additional descriptors for JOC elements (pointing to Section D.2.2 of ETSI TS 103 420)
  2. Updates to ChannelConfiguration schemes to align with MPEG published scheme
  3. Updated references for E-AC-3 and AC-4 documentation to latest versions
rdoherty0 commented 5 years ago

Proposed redline text sent to editor (Thomas)

technogeek00 commented 5 years ago

Document available on Groupspaces: DASHIF-IOP-Updates-ec-3-issue-v4

Submit comments by June 4th, 2019 call.

ihofmann-iis commented 5 years ago

I believe the addition of JOC (redline section 9.2.1.2.) introduces a new codec and should follow the established process for new formats and codecs ("Criteria for inclusion of codecs and formats in DASH-IF Interop Points").

rdoherty0 commented 5 years ago

I believe the addition of JOC (redline section 9.2.1.2.) introduces a new codec...

I believe it does not: the "@codec" string is unchanged, there is no new dashif interop point. This functionality is already supported by ec-3 codec, and is in wide use today. The newly documented parameters, which are already available in the existing interop point, are merely copies from the existing published specs to make it easier for implementers by request of partner companies, there is no new functionality introduced.

But of course we are happy to discuss on the next call.

ihofmann-iis commented 5 years ago

I believe the addition of JOC (redline section 9.2.1.2.) introduces a new codec...

I believe it does not: the "@codec" string is unchanged, there is no new dashif interop point. This functionality is already supported by ec-3 codec, and is in wide use today.

Maybe this is just my lack of understanding what JOC means then - do you think you can give a brief introduction on Tuesday? I agree, this is better discussed verbally than via github.

haudiobe commented 5 years ago

(IOP 19/06/04) Supplemental descriptor to signal that inband information for object based consumption. This does not break any backward-compatibility. Update shall to make reference to ETSI spec and avoid duplication of shalls across specs. Richard will update.

rdoherty0 commented 5 years ago

Changes to address the last comment are uploaded to v5 of the submission: DASHIF-IOP-Updates-ec-3-issue-v5

rdoherty0 commented 4 years ago

Editorial corrections to the latest version: https://members.dashif.org/wg/DASH/document/4396

pmaness commented 4 years ago

A single publication will be prepared that covers this issue, and issues #141, #149 and #398 as an amendment and corrigendum to the DASH-IF IOP Version 4.3 specification as agreed in DASH-IF IOP June 8, 2020