- Newest
- Most votes
- Most comments
Hi Björn,
Thanks for asking this question in the forum, The URL you are using to request the manifest appears to be correct, however the end date you have entered is in 2018, which is before the start date. Please correct this and try again. Also, the epoch dates 1529935200 and 1529935500 translate to GMT: Monday, June 25, 2018 2:00:00 PM and 02:05:00pm
Remembering that the maximum length of a manifest is 9 hours as outlined under https://docs.aws.amazon.com/mediapackage/latest/ug/limits-live.html
and there maximum content retention of 14 days.
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"
Thanks
Richard
Edited by: RichardB-AWS on Jun 13, 2019 7:22 AM
Hello Richard,
thanks for your reply!
You are absolutely right, the curl command was wrong.
but after correcting the parameters:
curl -vL --globoff "https://528dc4ef17d725ed.mediapackage.eu-central-1.amazonaws.com/out/v1/deca9a76c2e64835b43b79748c7a62bb/index.m3u8?start=2019-06-14T09:30:00_02:00&end=2019-06-14T09:50:00_02:00"
I still get a 404:
- Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 404
< date: Fri, 14 Jun 2019 08:55:46 GMT
< content-type: text/html; charset=iso-8859-1
< content-length: 18
< server: AWS Elemental MediaPackage
< x-mediapackage-request-id: 81de06bdedb79487ee5cc80b76cfb7dc
< - Connection #0 to host 528dc4ef17d725ed.mediapackage.eu-central-1.amazonaws.com left intact
In the MediaPackage configuration, Startover window is set to 36000, so the timeframe should fit into the window size.
Any ideas on what might be wrong?
Take care,
Björn
Hi Björn
The command you are using is correct, as is the documentation. When I try to use the same syntax I get a 403 error so I am assuming there is whitelist in use on your deployment.
Because of the nature of the problem can I please ask that you open a support ticket with AWS, that way we can track the progress while trouble shooting your issue, however looking briefly at the Database records the last segment was written
2019-06-14 04:32:39 (UTC) is the last endpoint segment time
so it looks like the endpoint has either been deleted or ingest has stopped.
Thanks
Richard
Edited by: RichardB-AWS on Jun 14, 2019 10:56 AM
Edited by: RichardB-AWS on Jun 14, 2019 10:58 AM
Hi Richard,
yes, you are right. I turned off the stream over the weekend. And for good measure, I recreated the Endpoint configuration from scratch, so the Endpoint URL changed.
Still, I get the 404:
- Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 404
< date: Mon, 17 Jun 2019 07:14:30 GMT
< content-type: text/html; charset=iso-8859-1
< content-length: 18
< server: AWS Elemental MediaPackage
< x-mediapackage-request-id: aaea8e7d5ef81564a7880dda36baa96d
So I will follow your advice and open up a support ticket.
Thank you very much for your help and take care,
Björn
We were able to solve the issue.
What was missing was the correct timecode configuration in MediaLive:
What we changed:
Channel general settings -> Timecode configuration: from „EMBEDDED“ to „SYSTEMCLOCK“
Channel -> Output groups -> Output Group -> Stream settings -> Codec Settings h264 -> Timecode: from „DISABLED“ to „PIC_TIMING_SEI“
With these configurations in place, time shifted viewing was functional.
Thanks again for the help here and all the best,
Björn
Relevant content
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago