Recherche avancée

Sur d’autres sites (10231)

• Streaming HLS with Nginx & FFMPEG : How to prevent repeating or skipping scenes (.ts) when playback ?

  31 août 2022, par Fugen

  I set up HLS streaming server using Nginx & FFMPEG, then i watch it using vlc or ffplay on another pc. The problem is sometimes it repeating scenes or skipping scenes for few seconds then it continue like normal, it happens at random but occurs occasionally and not always on the same spots.
  

  


  Here is sample of ffplay log :

  


  [http @ 000002c6e2611c00] Opening 'http://172.20.120.75:8080/hls/test-3.ts' for reading
[hls @ 000002c6e260bcc0] Skip ('#EXT-X-VERSION:3')sq=    0B f=0/0
[hls @ 000002c6e260bcc0] Skip ('#EXT-X-DISCONTINUITY')
[http @ 000002c6e2614500] Opening 'http://172.20.120.75:8080/hls/test-3.ts' for reading
[http @ 000002c6e2611c00] Opening 'http://172.20.120.75:8080/hls/test-4.ts' for reading
[http @ 000002c6e81c8140] Opening 'http://172.20.120.75:8080/hls/test.m3u8' for reading
[hls @ 000002c6e260bcc0] Skip ('#EXT-X-VERSION:3')sq=    0B f=1/1
[hls @ 000002c6e260bcc0] Skip ('#EXT-X-DISCONTINUITY')
[http @ 000002c6e2614500] Opening 'http://172.20.120.75:8080/hls/test-3.ts' for reading
[http @ 000002c6e2611c00] Opening 'http://172.20.120.75:8080/hls/test-4.ts' for reading
[http @ 000002c6e81c8140] Opening 'http://172.20.120.75:8080/hls/test.m3u8' for reading
[hls @ 000002c6e260bcc0] Skip ('#EXT-X-VERSION:3')sq=    0B f=2/2
[http @ 000002c6e2614500] Opening 'http://172.20.120.75:8080/hls/test-6.ts' for reading
[http @ 000002c6e2611c00] Opening 'http://172.20.120.75:8080/hls/test-7.ts' for reading
[http @ 000002c6e81c8140] Opening 'http://172.20.120.75:8080/hls/test.m3u8' for reading
[hls @ 000002c6e260bcc0] Skip ('#EXT-X-VERSION:3')sq=    0B f=2/2
[http @ 000002c6e2614500] Opening 'http://172.20.120.75:8080/hls/test-7.ts' for reading
[http @ 000002c6e81c8140] Opening 'http://172.20.120.75:8080/hls/test.m3u8' for reading
[hls @ 000002c6e260bcc0] Skip ('#EXT-X-VERSION:3')sq=    0B f=2/2
[http @ 000002c6e2611c00] Opening 'http://172.20.120.75:8080/hls/test-8.ts' for reading


  


  From that log, repeating scenes are : test-3.ts, test-4.ts, test-7.ts, and skipped scene : test-5.ts.
  My question is : how to prevent this ?

  


  When i checked .m3u8 playlist on server side it seems normal, no repeated or skipped .ts file. Here is .m3u8 file :

  


  #EXTM3U
#EXT-X-VERSION:3
#EXT-X-MEDIA-SEQUENCE:17
#EXT-X-TARGETDURATION:4
#EXTINF:3.600,
test-1.ts
#EXTINF:3.560,
test-2.ts
#EXTINF:3.600,
test-3.ts
#EXTINF:3.600,
test-4.ts
#EXTINF:3.600,
test-5.ts
#EXTINF:3.600,
test-6.ts
#EXTINF:3.600,
test-7.ts
#EXTINF:3.520,
test-8.ts
#EXTINF:3.600,


  


  My Nginx Configuration :

  


  worker_processes 4;
events {
        worker_connections 1024;
        use epoll;
        multi_accept on;
}

# RTMP configuration
rtmp {
    server {
        listen 1935; # Listen on standard RTMP port
        chunk_size 4096;

        application show {
            live on;
            # Turn on HLS
            hls on;
            hls_path /tmp/hls/;
            hls_fragment 3;
            hls_playlist_length 60;
            # disable consuming the stream from nginx as rtmp
            deny play all;
        }
    }
}

http {
        sendfile off;
        tcp_nopush on;
        tcp_nodelay on;
        reset_timedout_connection on;
        directio 512;
        default_type application/octet-stream;

    server {
        listen 8080;

        location /hls {
            # Disable cache
            add_header 'Cache-Control' 'no-cache';
            access_log off;
            # CORS setup
            add_header 'Access-Control-Allow-Origin' '*' always;
            add_header 'Access-Control-Expose-Headers' 'Content-Length';
            # allow CORS preflight requests
            if ($request_method = 'OPTIONS') {
                add_header 'Access-Control-Allow-Origin' '*';
                add_header 'Access-Control-Max-Age' 1728000;
                add_header 'Content-Type' 'text/plain charset=UTF-8';
                add_header 'Content-Length' 0;
                return 204;
            }

            types {
                application/dash+xml mpd;
                application/vnd.apple.mpegurl m3u8;
                video/mp2t ts;
            }

            root /tmp/;
        }
location /nginx_status {
        # Turn on stats
        stub_status on;
        allow all;
    }
}
}


  


  My FFMPEG Command :

  


  ffmpeg -re -stream_loop -1 -i 'video1.mp4' -vcodec libx264 -vprofile baseline -g 30 -acodec aac -strict -2 -f flv 'rtmp://172.20.120.75/show/test' &


  


  Thank You for Your Help.

  


• Nginx allow only my domain to access a video url

  4 septembre 2019, par Bruno F

  i’m setting up a web server that contains live video streaming embed into the html5 video tag. My workflow is to grab the rtsp video from an ip camera, decode it to a HLS format using ffmpeg and send the video to my server.
  Nginx allows access to the video through a url, which I put in my video tag as a source.

  Everything works perfectly, the only problem is that anyone can access the URL of the video and put that URL on their website without my permission.

  Is there any way to only allow my domain to access, and block for example www.domain2.com to put it into their video tag or other framework thath they use ? i’m think Nginx can do the job maybe.

  Here are the codes of Nginx and my html in case is needed.

  HTML :

  <video class="video-js vjs-default-skin vjs-big-play-centered vjs-fluid" controls="controls" preload="none">
  
  <source src="//mydomain.com/live/stream.m3u8" type="application/x-mpegURL"></source>
  
  </video>

  Nginx :

  location /live {
  
              types {
  
                      application/vnd.apple.mpegurl m3u8;
  
              }
  
              limit_conn addr 5;
  
              alias /home/stream;
  
              add_header Cache-Control no-cache;
  
              add_header 'Access-Control-Allow-Origin' '*';
  
      }

  Many thanks guys !

• avformat/hls : do not care about stream start timestamps

  30 décembre 2013, par Anssi Hannula

  avformat/hls : do not care about stream start timestamps
  While selecting a packet to return to caller in read_packet(), the code
  
  corrects the timestamps for starting timestamps.
  However, this is wrong, since for live streams the initial timestamps
  
  might differ just because of the time delay between the retrieval of the
  
  various Media Playlists.
  Fortunately, spec 6.2.4 mandates that all variant streams must have
  
  matching timestamps, so we do not need to correct for initial
  
  timestamps.
  Drop the correction code.
  Note that ID3 timestamps were previously ignored, so this code was
  
  previously actually needed.
  Signed-off-by : Anssi Hannula <anssi.hannula@iki.fi>
  

  • [DH] libavformat/hls.c