Chunks are not being refreshed with new Manifest response's SegmentTemplates.

[baturays]

Have you read the Tutorials?

Have you read the FAQ and checked for duplicate open issues?

If the question is related to FairPlay, have you read the tutorial?

What version of Shaka Player are you using?
2.5.23

What browser and OS are you using?
MacOs, Firefox

Please ask your question

Hello,

I am currently playing a live channel using DASH and for additional security, I am adding some search parameters to the new manifest requests. As a response to the manifest request, I receive new segments and a new token parameter within the media object. However, while the ts chunks are being downloaded, the token parameter appended to the media chunks from the initial manifest request is still being used.

In short:

1. I am using Shaka Player to play a live DASH stream.
2. I add some search parameters (e.g., st, ts, e) to new manifest requests.
3. The server returns a new manifest with updated st tokens within the SegmentTemplate elements.
   However, Shaka Player continues to use the old st tokens from the initial manifest request when downloading segment chunks.
   How can I ensure that Shaka Player uses the new st tokens for segment chunks after a new manifest is loaded? What would be the best approach to solve this issue?

[avelad]

You are using an unsupported and very old version. I'm sure this has been resolved in newer versions, can you try 4.10.2? Thanks!

[baturays]

Hello, I upgraded the Shaka version to 4.10.2 as you suggested, but the problem is still not fixed. Even though a new MPD request is made, it continues to read the old manifest file.

[avelad]

Can you send your manifest url to test it?

[baturays]

Hello, this manifest URL is closed to the outside due to company policy and cannot be accessed externally.

Maybe if you can provide me with a sample content, I can test it on my end to see if the transition works correctly.

[avelad]

We do not have content with these characteristics. Since you can't provide an example to help you, we'd be happy to review your PR in case you want to contribute to fixing this. I'm sorry!

[baturays]

Hello, as you mentioned, I updated the Shaka version and continued testing. After MPD refreshes, it continues to download chunks from the old mode, and after a while, it switches to the new MPD after receiving a 410 error from the existing mode and continues downloading chunks. However, after a while, it encounters issues during these transitions and fails to switch to the new mode. Is there a configuration we can use to force the player to switch to the new MPD after receiving it?

[baturays]

Hi @avelad , i am waiting for your response. Thanks.

[baturays]

@shaka-bot reopen

[baturays]

Here i am sharing my registerRequestFilter function , to update header parameters with new ones .

MTC.registerRequestFilterFunction = (type, request) => {
const requestType = playerMethods.getRequestTypes();
if (type === requestType.MANIFEST) {
request.uris.forEach((uri, index) => {
if (isMpdRequest(uri)) {

            let tokenParams = {};
            try {
                tokenParams = prepareTokenParams();
            } catch (error) {
                console.warn("Token creation error on registerRequestFilter: ", error);
                return;
            }

            const { sample } = tokenParams;
            const urlObj = new URL(uri);
            
            const paramsToDelete = ["sample"];
            paramsToDelete.forEach(param => {
                if (urlObj.searchParams.has(param)) {
                    urlObj.searchParams.delete(param);
                }
                delete request.headers[param];
            });

            request.headers["sample"] =  sample;
            request.uris[index] = urlObj.href;
        }
    });
}

}

I observe that request.uris is growing in size after each call, even if i have only 1 uri in the beginning.

[avelad]

So I understand that you have solved the problem with your filter. The growth of the uris size is expected if you frequently change the final url of the mpd (including tokens)

[shaka-bot]

Closing due to inactivity. If this is still an issue for you or if you have further questions, the OP can ask shaka-bot to reopen it by including @shaka-bot reopen in a comment.

[baturays]

@shaka-bot reopen

[baturays]

I reopened the topic because I want to ask something. I upgraded my Shaka Player version to 4.10.2. What I want to ask is: In dynamic manifest requests, after each manifest request, shouldn't it continue with the updated data from the manifest (segment templates)? What I see is that even though manifest requests are made, the new segments from the updated manifest are not immediately used. I also noticed that sometimes, when a 410 is received from the server, it automatically switches to one of the next manifests, but this is not stable. I couldn't understand how it decides which manifest to switch to. In short, my question is, after each manifest request, can we ensure that Shaka continues with the latest manifest? Or, based on which tags or properties does Shaka make decisions during these transitions in the response?