Can't play HLS link

[chillsweet]

ExoPlayer 2.6.0

Problem is when I play HLS link with HlsMediaSource, it can prepare source by show duration of audio but it won't play when ready.

I'm not quite sure that it's about codec of file that effect to this problem? or something else.

problem link:
"https://live-s2.cocodemy.com/content2/a1.mp3/playlist.m3u8?wmsAuthSign=c2VydmVyX3RpbWU9MTIvMjIvMjAxNyAwOToxNzoyOSBBTSZoYXNoX3ZhbHVlPUd6SnFQQkp0VnBia1FJcVlycGl4K3c9PSZ2YWxpZG1pbnV0ZXM9MTA="

playable link:
"https://live-s2.cocodemy.com/content2/p1.mp4/playlist.m3u8?wmsAuthSign=c2VydmVyX3RpbWU9MTIvMjIvMjAxNyAwNDo0MDowNyBBTSZoYXNoX3ZhbHVlPUJJTW5IaFU1VzhqSkNoa1JSMFVYZUE9PSZ2YWxpZG1pbnV0ZXM9MTA="

sorry for my bad english.

[erdemguven]

Tried on dev branch HEAD, player stays in buffering state, no error log. Link plays fine on QuickTime player.

[chillsweet]

It's happen only audio file convert to m3u8

there are other links that get this problem too

https://live-s2.cocodemy.com/content2/a2.m4a/playlist.m3u8?wmsAuthSign=c2VydmVyX3RpbWU9MDEvMDIvMjAxOCAwOTo0NTo1MSBBTSZoYXNoX3ZhbHVlPVU1eCtPZTYvN3hGVmhaMHlUeWNQeEE9PSZ2YWxpZG1pbnV0ZXM9MTA=

https://live-s2.cocodemy.com/content2/53.mp3/playlist.m3u8?wmsAuthSign=c2VydmVyX3RpbWU9MDEvMDIvMjAxOCAwOTozNToyNCBBTSZoYXNoX3ZhbHVlPVoxWHpTQ011TzRJWllQQWN0OUwxdHc9PSZ2YWxpZG1pbnV0ZXM9MTA=

[ojw28]

The issue is that the media segments are mp3 segments, but they're named with a .ts file extension.

• Changing the segment file extensions to .mp3 on the serving side (and updating the media playlist accordingly) will allow the content to be played successfully. If you control the serving side then this is by far the best way for you to resolve the issue, since the file extensions are incorrect.
• Using a custom HlsExtractorFactory that forces initialization of an Mp3Extractor would also allow the content to be played successfully, if you knew you were handling this type of content. You'd need to pass your custom factory when creating the HlsMediaSource.
• The fact we rely on the segment file extensions is considered a bug. This issue is tracked by Add support for container format sniffing in HLS #2025.

The only remaining thing here is that now we've made TsExtractor robust against malformed content, this case results in indefinite buffering rather than playback failure. It feels like we should fail eventually (e.g. If we've read a certain number of bytes without ever having encountered a valid TS packet. @AquilesCanta - Could we do something like that to ensure playback failure in this case?

[chillsweet]

@ojw28 thank you for your solution
I think choice 2 is the best solution now
but I can't find any example code for implement HlsExtractorFactory.

Could you please give me an example about HlsExtractorFactory, so I can use it to finish my HlsMediaSource.

[tonihei]

Did you have a look at the interface here: HlsExtractorFactory
And our default implementation: DefaultHlsExtractorFactory.

You can provide your own implementation that forces the initialization of an Mp3Extractor as @ojw28 explained. To use this custom extractor factory, you'll also need to enable it by calling .setExtractorFactroy on the HlsMediaSource.Factory which creates your media source.

[chillsweet]

@tonihei
I follow your suggestion and now I can play the mp3 link
Thank you so much 👍

[ojw28]

Issue needs to remain open to track this:

The only remaining thing here is that now we've made TsExtractor robust against malformed content, this case results in indefinite buffering rather than playback failure. It feels like we should fail eventually (e.g. If we've read a certain number of bytes without ever having encountered a valid TS packet. @AquilesCanta - Could we do something like that to ensure playback failure in this case?

[AquilesCanta]

We can count the number of bytes read since the last successful sync, and throw if larger than a given threshold. A fix along these lines will be pushed soon. Thanks for your patience!

[ojw28]

Please file a new issue, rather than tacking something onto a possibly unrelated issue from months ago. Deleting posts so this issue remains easy to read. Thanks!