Bug 202101 – Support for callbacks for manifest events

• Status: RESOLVED
• Resolution: FIXED
• Component: Media

Hi Team,

It would be good to have callbacks for manifest timed events (HLS).

E.g. EXT-X-DATERANGE.

This is required for Server Side Dynamic Ad Implementations. For example the Ad related metadata could be passed in this attribute. The App could listen for this metadata callback and take appropriate action based on this.

It's supported in the AV player in iOS, but there is no support on Safari.

[Radar WebKit Bug Importer]

<rdar://problem/55627676>

[Eric Carlson]

Created attachment 381314 [details]
Patch

[Jer Noble]

Comment on attachment 381314 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=381314&action=review

> Source/WebCore/platform/graphics/avfoundation/objc/MediaPlayerPrivateAVFoundationObjC.mm:3519
> +    UNUSED_PARAM(output);
> +    UNUSED_PARAM(track);
> +
> +    ensureOnMainThread([self, strongSelf = retainPtr(self), metadataGroups = retainPtr(groups)]() mutable {
> +        m_taskQueue.enqueueTask([player = m_player, metadataGroups = WTFMove(metadataGroups), currentTime = m_player->currentMediaTime()] {
> +            if (!player)
> +                return;
> +
> +            for (AVDateRangeMetadataGroup *group in metadataGroups.get())
> +                player->metadataDidArrive(retainPtr(group.items), currentTime);
> +        });
> +    });

Nit: why are we using a background queue if we're just going to dispatch to the main thread?

[Eric Carlson]

Created attachment 381350 [details]
Patch for landing

[Eric Carlson]

Created attachment 381943 [details]
Patch for landing.

[WebKit Commit Bot]

The commit-queue encountered the following flaky tests while processing attachment 381943 [details]:

imported/w3c/web-platform-tests/html/semantics/scripting-1/the-script-element/module/integrity.html bug 203394 (author: [e-mail])
The commit-queue is continuing to process your patch.

[WebKit Commit Bot]

Comment on attachment 381943 [details]
Patch for landing.

Clearing flags on attachment: 381943

Committed r251626: <https://trac.webkit.org/changeset/251626>

[WebKit Commit Bot]

All reviewed patches have been landed.  Closing bug.

Hi, could you please explain how to listen to this event (EXT-X-DATERANGE) from the html5 video element in Safari browser (on Mac)?

[Eric Carlson]

(In reply to shivaksk1 from comment #9)
> Hi, could you please explain how to listen to this event (EXT-X-DATERANGE)
> from the html5 video element in Safari browser (on Mac)?

EXT-X-DATERANGE metadata is exposed just like all timed metadata - as a text track with `kind=metadata`.

The scripts in this simple test page I wrote, which logs metadata cues as they are emitted, might be helpful: https://streaming-metadata.glitch.me

Hi Team, Thanks for the quick response.

May I know from which Safari browser version this feature is supported?

Also, I have a query:

#EXT-X-DATERANGE:ID="adbreak-100076-0",START-DATE="2021-09-06T12:05:34.000Z",DURATION=30,X-PRESENTATION-TIME=1630929934000,CLASS="com.xyz.dai.adbreak"

#EXT-X-DATERANGE:ID="tracking-100076-0-0",START-DATE="2021-09-06T12:05:34.000Z",DURATION=1,X-AD-URL="https://url_1",X-AD-ID="adbreak-100076-0",CLASS="com.xyz.dai.tracking"

In the above manifest, are we supposed to get two cues, one for each EXT-X-DATERANGE tag?

Cue 1: contains ID, DURATION, X-PRESENTATION-TIME, CLASS for cue 1
Cue 2: contains ID, DURATION, X-PRESENTATION-TIME, CLASS for cue 2


When I tried to run the sample script on the above manifest, I observed that:
- For the first EXT-X-DATERANGE tag, we get one cue, with key = X-PRESENTATION-TIME.
- For the second EXT-X-DATERANGE tag, we get 2 cues,
  - cue 1: {key: X-AD-ID, value: adbreak-100076-0}
  - cue 2: {key: X-AD-URL, value: https://url_1}

Could you please explain this behavior?