Coder Social home page Coder Social logo

Comments (6)

cconcolato avatar cconcolato commented on August 11, 2024

If you look at the AudioSampleEntry class, it defines:

  • channel count (mandatory)
  • sample rate (mandatory)
  • channel layout (optional)
  • DRC (optional)
  • Downmix (optional)

As discussed during the call, we could specify that the channel count is the maximum channel count. For sample rate, I would imagine that all substreams have the same sample rate, as otherwise time alignment would be a problem (except in some cases). For all optional information, we could say that they should not be present or as it was suggested that they would be overridden by similar IAC information?

from iamf.

sunghee-hwang avatar sunghee-hwang commented on August 11, 2024

We don't need the optional fields like OPUS-ISOBMFF.

from iamf.

tdaede avatar tdaede commented on August 11, 2024

We should investigate what downmixing options (if any) are representable with existing mappings and ISOBMFF boxes.

from iamf.

sunghee-hwang avatar sunghee-hwang commented on August 11, 2024
  • RFC 7845 (Ogg Opus, CMF = 1) and RFC 8486 (Ambisonics, CMF = 2 or 3) provides stereo downmix matrices as spec text (not delivered)
  • ISOBMFF defines 'dmix' box for downmix matricies as a child of Audio sample entry. Any M x N downmix matries and any coefficients can be delivered via this box, where, M = targetChannelCount and N = baseChannelCount. But N is not defined in this box but is defined in ChannelLayout box ('chnl'). As summarized, any M x N downmix matrices and any coefficients can be delivered by using two optional fields ChannelLayout('chnl') and DownMixInstructions('dmix') of Audio sample entry. However, my understanding is that M is limited to 8 because 'targetlayout' of 'dmix' is based on ISO/IEC 23091-3 which defines only up to 7.1ch. (not define height channels).

from iamf.

cconcolato avatar cconcolato commented on August 11, 2024

As discussed, we have an agreement to specify that only codec specific info is stored (no loop, no override). We might reconsider if new use cases are brought forward.

from iamf.

tdaede avatar tdaede commented on August 11, 2024

The no loop approach is in the spec.

from iamf.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.