- Newest
- Most votes
- Most comments
Amazon Interactive Video Service (IVS) is designed for quickly creating channels, without the need to configure encoder settings. IVS does not offer the ability to modify encoder parameters. It will use the IDR values from the input source and propagate them through the system. You can test by using a controlled RTMP source to IVS. Set the IDR on the source to 2s. Then record the stream from IVS to Amazon S3. When reviewing the captured media, drill down to an HLS rendition. You will see a byte-range-variant manifest. This should detail segments corresponding to the IDR set in the source.
If you are looking to minimize IVS system latency, then please incorporate the use of the IVS Player SDK into the player. https://docs.aws.amazon.com/ivs/latest/userguide/player.html You can expect to achieve a 2-3s latency if used properly. Without it, a 5-7s latency would be expected.
You may also consider using the IVS Broadcast SDK for improved delivery into IVS. https://docs.aws.amazon.com/ivs/latest/userguide/broadcast.html
Ok, I've understand everything and I've done every test on my console but listen to this: On the live stream page of the AWS channel I've got 2 seconds of latency and this is great but When I copy the https playback url in VNC the latency go to 20 seconds so this are my questions: Is it possibile to have an RTMP string instead of the HTTPS? If not, how can I diminish the latency on HTTPS? Do you think that HTTPS protocol could be the problem? Thank you.
Relevant content
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a month ago
Ok, I've understand everything and I've done every test on my console but listen to this:
but
so this are my questions:
Thank you.