Browse through the questions and answers listed below or filter and sort to narrow down your results.
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
Accepted AnswerAWS Elemental MediaPackage
5
answers
0
votes
2
views
asked a year ago
Startover Window not working as hoped
Hi there,
We are attempting to stream Elemental Link -> MediaLive -> MediaPackage -> Cloudfront -> Theo Player
This works fine on a link like this: https://xxxx.cloudfront.net/out/v1/xxxx/index.m3u8
However when we add the start time we get a 404 error: https://xxxx.cloudfront.net/out/v1/xxxx/index.m3u8?start=2020-08-20T12:40:00+00:00
The startover window in Mediapackage is set to 7200 (2 hours) as the client would like viewers to be able to scroll back to the beginning of the stream for a limited time after the broadcast is finished.
Any help much appreciated!
Accepted AnswerAWS Elemental MediaPackage
3
answers
0
votes
5
views
asked 2 years ago
How to use AWS Elemental MediaPackage with Custom CDN
Customer runs their own CDN. They want to connect their CDN to AWS Elemental MediaPackage. Should they need AWS Direct Connect connection? Can a custom CDN pull from MediaPackage as origin?
Accepted AnswerAWS Elemental MediaPackage
1
answers
0
votes
7
views
asked 2 years ago
When are the VOD mediapackage streams ready ?
Hello,
with VOD MediaPackage, after creating a new asset, we obtain the urls for the packaging configuration urls.
usually it takes a few minutes for the streams to be downloadable (meaning not to return a 404 error).
But today I have a longer 2hours videos and it tooks 10+ minutes for the playlist file to be available.
Is there a notification event that we could track to be aware when the packaging outputs are ready to be published ?
Joel
Accepted AnswerAWS Elemental MediaPackage
1
answers
0
votes
1
views
asked 2 years ago
MediaPackage corrupts input when passing in Tags
aws-sdk javascript 2.419.0
When I create a MediaPackage Channel in the Console, I get the correct inputs showing on MediaPackage, which are two inputs with an ID, URL, Username, and Password fields all filled out.
When I use the SDK and use MediaPackage, the channel builds, but the MediaPackage channel has two inputs but the first one has no ID and the URL is has /None/channel in it (eg. https://555555ca212fa91fb.mediapackage.us-east-1.amazonaws.com/in/v2/zzzzza44a01634ee6bfa5af15cc13zzzzz/None/channel ).
input data is normal:
```
var params = {
Id: 'testchannel6',
Description: 'standard description',
Tags: {
'OrgID': 'testorg'
}
}
```
This is exactly how it shows in the documentation:
https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/MediaPackage.html#createChannel-property
Also, the tag is added... its just that when I add Tags to the params I get the /None/channel issue.
to clarify. If I remove the "Tags" it works as expected - just without the tags obviously.
I suppose this is a bug?
Edited by: rbalhorn on Mar 22, 2019 2:58 PM
Accepted AnswerAWS Elemental MediaPackage
3
answers
0
votes
0
views
asked 3 years ago
4
answers
0
votes
3
views
asked 3 years ago