- Newest
- Most votes
- Most comments
Hi Jorge,
As you suggested, you can configure an UDP/RTP output of MediaLive (https://docs.aws.amazon.com/medialive/latest/ug/creating-udp-output-group.html) and use the ingest IP of the MediaConnect flow as the destination. Then you can create an SRT output (listener or caller) from that MediaConnect flow (https://docs.aws.amazon.com/mediaconnect/latest/ug/outputs-add-standard.html).
Step by step :
- Create MediaConnect flow, take note of the input IP
- Create a MediaLive channel with an UDP output group in which the destination is the previous IP
- Create a MediaConnect SRT output
- Start both the MediaConnect flow and the MediaLive channel
I recommend using FEC for the MediaLive output as a means of protection against packed drop (https://docs.aws.amazon.com/medialive/latest/ug/downstream-system-udp.html).
Thanks
Thanks for your question, Jorge:
I consulted the documentation for MediaLive and unfortunately, SRT is not one of the supported outputs, so we are not able to transcode your video inputs from HLS to SRT.
The only path forward I can see is to install FFMPEG on an EC2 instance and use that to transcode your video from HLS to SRT. Then it would be easy to distribute your video via a MediaConnect flow, as SRT is able to be used as an input and output.
Thanks for your response, BCole. I did consider the option of standing up FFMPEG in EC2 as a work-around if there was no other alternative. Looks like Pedro may have provided a path, but will keep this option in mind.
I was able to get this working, but through a standard single pipeline source traversing the public internet.
I haven't been able to get it working via VPC, but as soon as I changed to standard source, it came right up.
UDP output group outputting RTP-FEC out of MediaLive into MediaConnect.
If this goes beyond PoC, it would be a 24x7 channel with at least 5 SRT output destinations to start.
On further testing, whenever I configure the MediaLive channel as VPC output delivery, MediaLive starts throwing out alerts that it can't reach the input source. However, when I reconfig to public output delivery, it works as inte
Update: VPC now working correctly. EIP wasn't associated.
Relevant content
- asked a year ago
- asked 2 years ago
- asked 3 months ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 5 months ago
Thanks Pedro, this is exactly what I was thinking but couldn't yet validate fully against documentation or testing.
I'll bring in the HLS into MediaLive, output to a UDP/RTP-FEC group and bring it into MediaConnect as RTP-FEC and output SRT from there.
They'll be in the same availability zone. Would I be able to hand-off between MediaLive and MediaConnect through VPC to avoid going out to public internet?
You should be able to use MediaLive VPC outputs and MediaConnect VPC inputs :
Please be aware that they would need to be in the same Availability Zone.
Also if your channel is 24/7 consider using MediaLive Reservations (https://docs.aws.amazon.com/medialive/latest/ug/reservations.html), where the price per MediaLive channel is heavily discounted (https://aws.amazon.com/medialive/pricing/).
On MediaConnect, if you are distributing your channels out to the internet, please consider Bandwidth Reservations in MediaConnect (https://docs.aws.amazon.com/mediaconnect/latest/ug/reservations.html)
These two types of reservations will reduce your overall costs and keep in mind that they have a 12 month commitment.