因此,我在mac上的usr/local/nginx位置安装了NGINX和RTMP模块。RTMP流工作得很好,只是不是HLS版本。下面是我的配置文件:
events {
worker_connections 1024;
}
rtmp {
server {
listen 1936;
chunk_size 4000;
application small {
live on;
# Video with reduced resolution comes here from ffmpeg
}
# video on demand
application vod {
play /var/flvs;
}
application vod2 {
play /var/mp4s;
}
# Many publishers, many subscribers
# no checks, no recording
application videochat {
live on;
# The following notifications receive all
# the session variables as well as
# particular call arguments in HTTP POST
# request
# Make HTTP request & use HTTP retcode
# to decide whether to allow publishing
# from this connection or not
on_publish http://localhost:8080/publish;
# Same with playing
on_play http://localhost:8080/play;
# Publish/play end (repeats on disconnect)
on_done http://localhost:8080/done;
# All above mentioned notifications receive
# standard connect() arguments as well as
# play/publish ones. If any arguments are sent
# with GET-style syntax to play & publish
# these are also included.
# Example URL:
# rtmp://localhost/myapp/mystream?a=b&c=d
# record 10 video keyframes (no audio) every 2 minutes
record keyframes;
record_path /tmp/vc;
record_max_frames 10;
record_interval 2m;
# Async notify about an flv recorded
on_record_done http://localhost:8080/record_done;
}
# HLS
# For HLS to work please create a directory in tmpfs (/tmp/hls here)
# for the fragments. The directory contents is served via HTTP (see
# http{} section in config)
#
# Incoming stream must be in H264/AAC. For iPhones use baseline H264
# profile (see ffmpeg example).
# This example creates RTMP stream from movie ready for HLS:
#
# ffmpeg -loglevel verbose -re -i movie.avi -vcodec libx264
# -vprofile baseline -acodec libmp3lame -ar 44100 -ac 1
# -f flv rtmp://localhost:1935/hls/movie
#
# If you need to transcode live stream use 'exec' feature.
#
application hls {
live on;
hls on;
hls_path /tmp/hls;
}
# MPEG-DASH is similar to HLS
application dash {
live on;
dash on;
dash_path /tmp/dash;
}
}
}
# HTTP can be used for accessing RTMP stats
http {
server {
listen 8080;
# This URL provides RTMP statistics in XML
location /stat {
rtmp_stat all;
# Use this stylesheet to view XML as web page
# in browser
rtmp_stat_stylesheet stat.xsl;
}
location /stat.xsl {
# XML stylesheet to view RTMP stats.
# Copy stat.xsl wherever you want
# and put the full directory path here
root /path/to/stat.xsl/;
}
location /hls {
# Serve HLS fragments
types {
application/vnd.apple.mpegurl m3u8;
video/mp2t ts;
}
root /tmp;
add_header Cache-Control no-cache;
}
location /dash {
# Serve DASH fragments
root /tmp;
add_header Cache-Control no-cache;
}
}
}我正在使用hls应用程序来流式传输。当我查看位于rtmp://ip:1936/hls/test的流时,我可以很好地看到它。当我尝试查看http://ip:1936/hls/test.m3u8时,我看不到它。我在这个位置为hls /usr/local/nginx/tmp/hls创建了一个文件夹。我想知道这是不是在正确的地方,因为什么都没有创建在文件夹中?会不会是权限问题?
我正在使用OBS来流式传输,它使用x246编码的视频,但不确定它是否是音频的AAC。
这里有一个类似的问题:https://groups.google.com/forum/#!topic/nginx-rtmp/dBKh4akQpcs,但没有答案:(.
任何帮助都是非常感谢的。谢谢。
发布于 2015-03-10 09:36:48
您的HLS内容超过端口8080,rtmp超过1936
意味着rtmp://ip:1936/hls/test或http://ip:8080/hls/test.m3u8
发布于 2015-03-04 06:04:03
看到您的配置,但您将文件放在/tmp文件夹下,而不是/usr/local/nginx (完整路径)下。如果问题仍然存在,一个好的策略是从一个包含所有编解码器(hls、mpeg-dash)的应用程序开始(就像github中的配置示例一样)。
P.D:此模块仅适用于h264和瑞声
发布于 2019-09-10 18:18:31
我通过更改为录制来修复它,设置如下:

除此之外,我还更改了JPhix提到的内容。
https://stackoverflow.com/questions/27876056
复制相似问题