Report post You have 30 minutes to complete this form before the CAPTCHA will expire. Security image * Required field JavaScript is required to view this page. Either you do not have JavaScript enabled in your web browser, you do not have cookies enabled in your web browser, or this website is misconfigured such that cookies do not save correctly. This is a reported post for a post in the topic <input class="cms_keep_ui_controlled" size="45" title="[post param="HLS Streaming Server with NGINX"]417[/post]" type="button" value="post Comcode tag (dbl-click to edit/delete)" />, by jacobgkau<br /><br /><comcode-quote param="2">Hi there!<br /><comcode-quote param="marpensa">now that I buy a decoder to see the transmission<input class="cms_keep_ui_controlled" size="45" title="[snapback]415[/snapback]" type="button" value="snapback Comcode tag (dbl-click to edit/delete)" /></comcode-quote><br />Why do you need to buy a decoder? ffmpeg is the encoder, NGINX is the transcoder, the web browser is the decoder. All major web browsers are currently able to play HLS, and even the ones that can't natively can do so through a video player like VideoJS.<br /><comcode-quote param="marpensa">example: transmission link: rtmp: //rtmp.mine.com.cn/live/0315<br />reproductor link: rtmp: //pay.mine.com.cn/live/0315<br /><input class="cms_keep_ui_controlled" size="45" title="[snapback]415[/snapback]" type="button" value="snapback Comcode tag (dbl-click to edit/delete)" /></comcode-quote><br />"Reproductor" is not an English word, but I get the idea. However, your playback URL is not going to start with rtmp:, it's going to start with http: or https: (hence, why it's called HTTP Live Streaming) and it's going to end with .m3u8. You can play back the RTMP URL using a player that can decode RTMP, but the point of this video and the setup I demonstrated was to have NGINX decode it into HLS so clients can watch directly. Does that make sense? If not, then I'd need some more clarification on what you're trying to accomplish.<br /></comcode-quote><br />//// PUT YOUR REPORT BELOW \\\\<br /><br /> Add: Add: Font Size Color [Font] Arial Courier Georgia Impact Times Trebuchet Verdana Tahoma Geneva Helvetica [Size] 0.8 1 1.5 2 2.5 3 4 [Color] Black Blue Gray Green Orange Purple Red White Yellow This is a reported post for a post in the topic [post param="HLS Streaming Server with NGINX"]417[/post], by jacobgkau [quote="2"] Hi there! [quote="marpensa"]now that I buy a decoder to see the transmission[snapback]415[/snapback][/quote] Why do you need to buy a decoder? ffmpeg is the encoder, NGINX is the transcoder, the web browser is the decoder. All major web browsers are currently able to play HLS, and even the ones that can't natively can do so through a video player like VideoJS. [quote="marpensa"] example: transmission link: rtmp: //rtmp.mine.com.cn/live/0315 reproductor link: rtmp: //pay.mine.com.cn/live/0315 [snapback]415[/snapback][/quote] "Reproductor" is not an English word, but I get the idea. However, your playback URL is not going to start with rtmp:, it's going to start with http: or https: (hence, why it's called HTTP Live Streaming) and it's going to end with .m3u8. You can play back the RTMP URL using a player that can decode RTMP, but the point of this video and the setup I demonstrated was to have NGINX decode it into HLS so clients can watch directly. Does that make sense? If not, then I'd need some more clarification on what you're trying to accomplish. [/quote] //// PUT YOUR REPORT BELOW \\\\ View all Use of this website implies that you agree to the website rules and privacy policy. Statistics Forum statistics: 141 topics, 610 posts, 603 members Our newest member is Sophiathebest178 Birthdays: casper1955 (70)