On Fri, Nov 1, 2019 at 7:24 AM Yuki Tsuchiya <yuki.tsuch...@sony.com> wrote: > > Implemented according to the specification at > https://www.iso.org/standard/69561.html > The "mhm1" sample entry is registered with MP4RA, which is defined as MHAS > encapsulated single stream MPEG-H 3D Audio. > "MHAS" stands for MPEG-H audio stream, which contains encoded audio data and > corresponds metadata for decoding. > This patch enables extracting the MHAS bitstream from MP4. > > Signed-off-by: Yuki Tsuchiya <yuki.tsuch...@sony.com> > ---
Sorry for the late response, there have been various things recently :) . All of the samples I've seen in the wild (well, on the DASH-IF test vector list, which is the only place I've seen both AC-4 and MPEG-H Audio at until now) seem to utilize mha1, such as https://dash.akamaized.net/dash264/TestCasesMCA/fraunhofer/MPEGH_714_lc_mha1/1/Sintel/Sintel.2010_1080p_incl_Credits_new_cicp19_16bit-eng-893s-12-mpegh-256000bps_seg.mp4 . Thus my initial question is if there is any reason why 'mha1' is not added as well? Was that removed from the MP4 container specification afterwards? Additionally, are there any MPEG-H Audio specific configuration/etc boxes required to be read/written for valid decoding or to create a valid mux according to the spec which should be handled? Best regards, Jan _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
