Live thumbnails with Time+SegmentTimeline return 404s

[nicoweilelemental]

Environment

• The MPD passes the DASH-IF Conformance Tool on https://conformance.dashif.org/
• The stream has correct Access-Control-Allow-Origin headers (CORS)
• There are no network errors such as 404s in the browser console when trying to play the stream
• The issue observed is not mentioned on https://github.com/Dash-Industry-Forum/dash.js/wiki/FAQ
• [x]x The issue occurs in the latest reference client on http://reference.dashif.org/dash.js/ and not just on my page

• Link to playable MPD file:
• https://d24rwxnt7vw9qb.cloudfront.net/out/v1/91d37b0389de47e0b5266736d3633077/index.mpd (compact manifest)
• https://d24rwxnt7vw9qb.cloudfront.net/out/v1/6ba06d17f65b4e1cbd1238eaa05c02c1/index.mpd (full manifest)
• Dash.js version: 3.2.2 / 4.0.0
• Browser name/version: Chrome
• OS name/version: Windows

Steps to reproduce

1. Please provide clear steps to reproduce your problem
   Simple playback of the stream + mouseover on the seekbar.
2. If the bug is intermittent, give a rough frequency if possible
   Permanent problem.

Observed behavior

Player calculated image urls return 404.

Console output

GET https://d24rwxnt7vw9qb.cloudfront.net/out/v1/6ba06d17f65b4e1cbd1238eaa05c02c1/index_image_28_0_3382942055999.9995.jpg?m=1601056091 404

Expected behavior

Player is expected to calculate correct urls, as in other cases.

Examples of working streams:
Number+SegmentTimeline: https://d24rwxnt7vw9qb.cloudfront.net/out/v1/4577dca5f8a44756875ab5cc913cd1f1/index.mpd
Number+Duration: https://d10gktn8v7end7.cloudfront.net/out/v1/6ee19df3afa24fe190a8ae16c2c88560/index.mpd

[dsilhavy]

• 404s should be fixed in 4.0 alpha: https://reference.dashif.org/dash.js/v4.0.0-alpha/samples/dash-if-reference-player/index.html?mpd=https://d24rwxnt7vw9qb.cloudfront.net/out/v1/91d37b0389de47e0b5266736d3633077/index.mpd
• Thumbnails are currently limited to periods which have been activated (meaning the period is playing or has been played). Caused by ThumbnailController being initialized once stream is about to be activated. We should consider finding a better solution for this.

[nicoweilelemental]

Thanks, I see it working now. The current activation behavior is probably acceptable when playing streams with a very limited DVR window, but it's true that it's hard to understand from an end-user perspective. We'll soon have thumbnails on the ad periods too, so it will be a good occasion to take another look at it.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. However, it might still be relevant so please leave a short comment if it should remain open. Otherwise the issue will be closed automatically after two weeks. Thank you for your contributions.

[dsilhavy]

unstall

[stale]

This issue has been automatically marked as stale because it has not had recent activity. However, it might still be relevant so please leave a short comment if it should remain open. Otherwise the issue will be closed automatically after two weeks. Thank you for your contributions.

[dsilhavy]

unstall

[stale]

This issue has been automatically marked as stale because it has not had recent activity. However, it might still be relevant so please leave a short comment if it should remain open. Otherwise the issue will be closed automatically after two weeks. Thank you for your contributions.

[nicoweilelemental]

unstale

[stale]

This issue has been automatically closed because no further activity occurred. If you think this issue is still relevant please reopen it or contact @dsilhavy. Thank you for your contributions.

[stale]

This issue has been automatically closed because no further activity occurred. If you think this issue is still relevant please reopen it or contact @dsilhavy. Thank you for your contributions.

[dsilhavy]

Duplicate of #3795