ybai001

BTW, the ffprobe command I used is `ffprobe.exe -i gapless-sweep_part1_iis.m4a -show_packets > out.txt`

Thanks for quick feedback. Yes, I see ExoPlayer handles 'elst' box well. I think Android AOSP also handles gapless metadata, see this code: https://cs.android.com/android/platform/superproject/+/master:frameworks/av/media/libstagefright/SkipCutBuffer.cpp;drc=0766ead67694809c3cb12dc6ddb81a2eb7b475ad;l=59 As long as AOSP MPEG4Extractor finds...

> @ybai001 - If this is Dolby defined, is it something you'd be able to send a pull request to address? @ojw28 - This is actually Dolby defined. I need...

@ojw28 The internal discussion is still on-going.

@ojw28 , @RicFlinn We have some updates for you today. 1. For the provided example in original question, ``, this schemeIdUri "tag:dolby.com,2015:dash:audio_channel_configuration:2015" is used for AC-4 content. We (Dolby) will...

> > Considering current ExoPlayer/Android devices don't support object-based audio, we plan to simply set audioChannels = Format.NO_VALUE; Does it make sense for you? > > I'm not entirely sure...

@tonihei , the patch (to support this schemeIdUri) is in internal review phase. After that, we will submit it as pull request.

Hi, @christosts, Could you help to check whether this update is suitable for contribution? Feel free to let us know if you have any question. Thanks for your time in...

Dolby will discuss with Google team about this topic based on Google's suggestion directly. Close this pull request.

> I got around to investigate this a bit with a FireTV Stick 4K Ultra HD. It has the same decoders available I believe and it also fails to play...