theodab b9eabe5441 fix(DASH): Change fallback presentation delay (#7918) ...

Previously, if the presentation delay was not specified either by the
manifest or by configuration, we defaulted to 1.5 * minBufferTime. That
approach worked for most content, but in some cases it could cause live
streams to start out with a seekRangeEnd that was before the live edge.
This would lead to a brief pause in the beginning of the presentation,
while the live edge caught up.

This changes the DASH parser to use the segmentAvailabilityDuration if
it is lower than 1.5 * minBufferTime, which fixes that issue.

It also changes how that part of the code to be formatted, in order to
hopefully make the increasingly-complex logic for determining the
presentation delay more clear.

2025-01-22 10:43:08 +01:00

..

content_protection.js

build: Forbid using dot in generic types (#7904)

2025-01-20 09:39:51 +01:00

dash_parser.js

fix(DASH): Change fallback presentation delay (#7918)

2025-01-22 10:43:08 +01:00

mpd_utils.js

build: Forbid using dot in generic types (#7904)

2025-01-20 09:39:51 +01:00

segment_base.js

build: Forbid using dot in generic types (#7904)

2025-01-20 09:39:51 +01:00

segment_list.js

build: Forbid using dot in generic types (#7904)

2025-01-20 09:39:51 +01:00

segment_template.js

fix(DASH): Notify time range with the fitted timeline (#7911)

2025-01-21 10:12:18 +01:00