By using AWS re:Post, you agree to the Terms of Use
/AWS Elemental MediaPackage/

Questions tagged with AWS Elemental MediaPackage

Sort by most recent
  • 1
  • 90 / page

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Safari buffering/freezing — Related to MediaPackage adding "autoplay=1" sporadically?

I'm having some issues with a MediaLive/MediaPackage stream buffering/halting and jumping bitrates all the time on Safari (desktop & mobile), but not on Chrome. Both using video.js as a player, as well as a native video tag. I'm using Elemental Link devices to push to MediaLive. Using a configuration generated by the MediaLive Workflow Wizard, but modified slightly to add tagging and an additional bitrate. I also had to modify the CloudFront distribution a bit to get around CORS issues, allowing "Origin" as a caching key. I've run the MediaPackage stream through Apple's MediaStreamValidator tool. It's flagging as an error that MediaPackage is sometimes returning an "autoplay=1" to the individual manifests, and sometimes not. For example, some pulls of the manifest return chunk URIs like this: `index_1_16087.ts?m=1642705601` and other pulls return this: `index_1_16087.ts?autoplay=1&m=1642705601` Here's a sample MediaStreamValidator error: ``` Error: Media Entry URL not match previous playlist for MEDIA-SEQUENCE 16087: index_1_16087.ts?autoplay=1&m=1642705601 vs index_1_16087.ts?m=1642705601 ``` Could anyone please advise on how/why this autoplay query parameter is being added, what effect it's expected to have, and if this might be causing the problem with Apple devices? Would also love any other advice on getting a MediaLive/MediaPackage stream to play smoothly on Safari. Thanks!
0
answers
0
votes
2
views
asked 4 months ago

Webdav & webvtt

Hello, I am currently trying to update a webvtt segment file over webdav, on a live channel. When I request the .vtt file directly (from the endpoint), it is loaded just fine (it is loaded fine as well by my web player - jwplayer). Now, I can successfully write a full replacement via webdav onto the ingest channel - I get a response such as: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>201 Created</title> </head><body> <h1>Created</h1> <p>Resource /in/v2/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/index_3_0_225.vtt has been created.</p> <hr /> <address>AWS Elemental MediaPackage Server at xxxxxxxxxxxxxxxx.mediapackage.xx-xxxxx-x.amazonaws.com Port 80</address> </body></html> But when I reload the .vtt file on the endpoint, no change has occured, and I can't figure why. I also tried with a totally new filename such as "test.vtt" (to try and find if it had something to see with an overwriting issue on the existing .vtt file), to no avail, the "test.vtt" file does not exist on the endpoint (404). I must be missing something here. I double checked the format and it is OK (just a very simple caption example, keeping the proper WEBVTT first lines identical to the original file). How come I can't see any change on the output despite the successful Webdav PUT operation? Do I need to update another file as well to "trigger" the change (such as the manifest, the equivalent .ts segment, ...)? Many thanks in advance for your help! Cheers Jean-Marc Edited by: Jean-Marc on Jan 4, 2021 11:42 AM
5
answers
0
votes
2
views
asked a year ago

404 error for timeshift requests

Hi all, I'm hving problems while following the documentation under https://docs.aws.amazon.com/mediapackage/latest/ug/time-shifted.html. When I try to execute a test call via curl -vL --globoff "https://xxx.mediapackage.eu-central-1.amazonaws.com/out/v1/xxx/index.m3u8?start=1529935200&end=1529935500" or curl -vL --globoff "https://xxx.mediapackage.eu-central-1.amazonaws.com/out/v1/xxx/index.m3u8?start=2019-06-13T11:40:00_02:00&end=2018-06-13T11:50:00_02:00" Here is the verbose output of the curl request: * Trying 35.156.198.119... * TCP_NODELAY set * Connected to xxx.mediapackage.eu-central-1.amazonaws.com (35.156.198.119) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH * successfully set certificate verify locations: * CAfile: /etc/ssl/cert.pem CApath: none * TLSv1.2 (OUT), TLS handshake, Client hello (1): * TLSv1.2 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (IN), TLS handshake, Server key exchange (12): * TLSv1.2 (IN), TLS handshake, Server finished (14): * TLSv1.2 (OUT), TLS handshake, Client key exchange (16): * TLSv1.2 (OUT), TLS change cipher, Client hello (1): * TLSv1.2 (OUT), TLS handshake, Finished (20): * TLSv1.2 (IN), TLS change cipher, Client hello (1): * TLSv1.2 (IN), TLS handshake, Finished (20): * SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256 * ALPN, server accepted to use h2 * Server certificate: * subject: CN=xxx.mediapackage.eu-central-1.amazonaws.com * start date: Jan 15 00:00:00 2019 GMT * expire date: Feb 15 12:00:00 2020 GMT * subjectAltName: host "xxx.mediapackage.eu-central-1.amazonaws.com" matched cert's "xxx.mediapackage.eu-central-1.amazonaws.com" * issuer: C=US; O=Amazon; OU=Server CA 1B; CN=Amazon * SSL certificate verify ok. * Using HTTP2, server supports multi-use * Connection state changed (HTTP/2 confirmed) * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 * Using Stream ID: 1 (easy handle 0x7fc7b1806e00) > GET /out/v1/xxx/index.m3u8?start=1529935200&end=1529935500 HTTP/2 > Host: xxx.mediapackage.eu-central-1.amazonaws.com > User-Agent: curl/7.54.0 > Accept: **/** > * Connection state changed (MAX_CONCURRENT_STREAMS updated)! < HTTP/2 404 < date: Thu, 13 Jun 2019 12:07:30 GMT < content-type: text/html; charset=iso-8859-1 < content-length: 18 < server: AWS Elemental MediaPackage < x-mediapackage-request-id: 6039b18130b49d4568cd9f001bc94fec < * Connection #0 to host xxx.mediapackage.eu-central-1.amazonaws.com left intact A 404 error is returned. Am I doing something wrong or is the documentation outdated? Any input on this issue would be greatly appreciated! All the best, Björn Edited by: BjoernPuttmann on Jun 13, 2019 6:25 AM
5
answers
0
votes
4
views
asked 3 years ago
  • 1
  • 90 / page