Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shaka doesn't work with Azure Media Services Smooth Streaming Manifests #7483

Closed
pvelm001 opened this issue Oct 24, 2024 · 0 comments · Fixed by #7484
Closed

Shaka doesn't work with Azure Media Services Smooth Streaming Manifests #7483

pvelm001 opened this issue Oct 24, 2024 · 0 comments · Fixed by #7484
Assignees
Labels
component: MSS The issue involves Microsoft Smooth Streaming manifest format priority: P1 Big impact or workaround impractical; resolve before feature release type: bug Something isn't working correctly
Milestone

Comments

@pvelm001
Copy link

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

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

N/A

What version of Shaka Player are you using?

4.11.9

Can you reproduce the issue with our latest release version?
Yes

Can you reproduce the issue with the latest code from main?
Yes

Are you using the demo app or your own custom app?
I have tried in both. I can reproduce the issue in both implementations

If custom app, can you reproduce the issue using our demo app?
Yes

What browser and OS are you using?
Microsoft Edge Dev (131.0.2903.5), Windows 11 (24H2 26100.2033)

For embedded devices (smart TVs, etc.), what model and firmware version are you using?
N/A

What are the manifest and license server URIs?

https://universalstore.streaming.mediaservices.windows.net/30fb1348-fa2b-4749-a7ab-f472194e0d7e/fb6cddcf-d52c-4a6c-ac63-4d104d58.ism/manifest
https://universalstore.streaming.mediaservices.windows.net/ef30bfa6-c6e0-4007-b9d9-b8b4616af3b8/10c70f71-17f5-46ec-aa1b-b3023ce3.ism/manifest
https://universalstore.streaming.mediaservices.windows.net/8b1ee0d1-3da9-449d-a3a9-37cb5f4d7bd6/5fa62a62-a291-436f-b3eb-5d959d05.ism/manifest

What configuration are you using? What is the output of player.getNonDefaultConfiguration()?

{}

What did you do?

Using Demo app:

(or)

Using code:

import ISOBoxer from 'codem-isoboxer';
window['ISOBoxer'] = ISOBoxer;

const player = new shaka.Player();
const url =  'https://universalstore.streaming.mediaservices.windows.net/30fb1348-fa2b-4749-a7ab-f472194e0d7e/fb6cddcf-d52c-4a6c-ac63-4d104d58.ism/manifest';

await player.attach(videoElement);
await player.load(url, null, 'application/vnd.ms-sstr+xml');

What did you expect to happen?
The player should play the whole video

What actually happened?

Smooth Streaming Manifest Fails with 404: Network Calls Drop After Initial Seconds:

The video starts normally, however after couple of seconds it starts failing with network call to the server. The fragment API calls are failing with 404 errors.
image

Same error is happening in Demo App:
image

I have tested the same manifest in other platforms like dash.js - MSS, and VLC where it is working fine.
image

Are you planning send a PR to fix it?
No

@pvelm001 pvelm001 added the type: bug Something isn't working correctly label Oct 24, 2024
@shaka-bot shaka-bot added this to the v4.12 milestone Oct 24, 2024
@avelad avelad added priority: P1 Big impact or workaround impractical; resolve before feature release component: MSS The issue involves Microsoft Smooth Streaming manifest format labels Oct 24, 2024
@avelad avelad self-assigned this Oct 24, 2024
@avelad avelad closed this as completed in b1d3a3a Oct 24, 2024
avelad added a commit that referenced this issue Oct 24, 2024
avelad added a commit that referenced this issue Oct 24, 2024
avelad added a commit that referenced this issue Oct 24, 2024
joeyparrish pushed a commit that referenced this issue Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: MSS The issue involves Microsoft Smooth Streaming manifest format priority: P1 Big impact or workaround impractical; resolve before feature release type: bug Something isn't working correctly
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants