Here we use the x264 codec to have a h264 output format. HLS can dynamically switch between different qualities based on the available bandwidth of the client. Later it should be extended to support also lower resolutions. In the first step, I just want to have a full HD video feed. Now our server receives the stream so it’s time to start encoding our video. Link to documentation of the RTMP source: Video Encoding usename and password login or defining a different port. There are a lot of other useful options for the rtmp protocol e.g. In our case it’s a rtmp source defined with our domain and a stream name. listen 1 tells FFmpeg to use the RTMP protocol as a server and wait for incoming connections So we’re starting with our fist parameters of the FFmpeg command: -listen 1 -i rtmp:///stream01 RTMP is a common used protocol for this and it’s supported by most of the streaming clients. h264, aac, mp3) and to know, how to use a command line. To be a able to follow my this article with using FFmpeg you should have basic knowledge about audio and video, the difference between container format (e.g. So be sure, that you use a fresh release. During the next steps I will use features that are only available since version 4.0. Requirementsįirst of all a new version of FFmpeg is required. Some things might have changed and might not be up to date. This article contains all my personal experience with HLS in FFmpeg. The data is delivered over a HTTP/HTTPS connection, so it can be also perfectly cached on server side or used in combination with an CDN. You can split audio and video into separate files, multiple audio and video streams for different formats and qualities are possible, easy to read and built in support on Apple devices (iOS, MacOS and tvOS). HLS itself is very awesome protocol for live streams. My goal was to setup my own streaming server that provides a video livestream using the HLS protocol ( Apple HTTP Live Streaming).
Follow the link here to get an overview over all articles.
0 kommentar(er)
