Obtaining video duration is abnormal

[MrLizhiguang]

Personal guess is that the decoder reads the video duration (milliseconds) and decimals
Test address：https://ops-aiops.oss-cn-hongkong.aliyuncs.com/vod/311_620_Venom20184K_play.ts

[MrLizhiguang]

If the length is not available, all return -9223372036854775807

[ojw28]

Yes. This is clearly documented in the Javadoc:

Returns the duration of the current content window or ad in milliseconds, or C.TIME_UNSET if the duration is not known.

[MrLizhiguang]

Yes, I see that this suspicion is caused by this reason. Is there a way to solve this? Mediaplay is normal

[ojw28]

#5097 is tracking an improvement that would make ExoPlayer better at inferring the duration of MPEG-TS streams, so this issue is effectively a duplicate of that one.

That aside, if you have any control over the media itself, the best solution is to use a modern container format such as MP4 or MKV, which are better designed to support efficiently determining the duration and performing seek operations.

Closing as a duplicate of #5097.

[MrLizhiguang]

It is difficult to replace the container because the video is 4K, which is not conducive to network transmission

[ojw28]

I do not understand what this means. The higher the resolution, the worse MPEG-TS is as a choice of container (and the better MP4/MKV are, relative to MPEG-TS).

[MrLizhiguang]

Video needs to be sliced

[ojw28]

Sorry, I do not understand what that means. MP4 and MKV are well suited to streaming of 4K content.