Recherche avancée

Sur d’autres sites (13384)

• can I h265 video stream using rtmp ? in nginx

  16 juillet 2019, par Hakan Murat Aksüt

  exec_push /usr/bin/ffmpeg -re -i rtmp://localhost:1935/$app/$name -ar 44100 -vcodec libx264 -g 25 -f flv rtmp://localhost/live/$name_hi

  I can broadcast h264 video on my nginxg server. but it doesn’t work when I want to make h265 instead of h264. I found out that this is because rtmp does not support h265. Is there a way to do this using rtmp if possible ?
  if not, what else can be used to stream h265 video in nginx instead of rtmp.

  rtmp {
  
      server {
  
              listen 1935;
  
              chunk_size 4096;
  
  
  
              application src {
  
                  live on;
  
                  exec_push /usr/bin/ffmpeg -re -i rtmp://localhost:1935/$app/$name -ar 44100 -vcodec libx264 -g 25 -f flv rtmp://localhost/live/$name_hi;
  
              }
  
  
  
              application live {
  
                      live on;
  
                      hls on;
  
                      hls_path /usr/share/nginx/hls; #file path for save
  
                      hls_fragment 1;
  
                      hls_playlist_length 10; 
  
                      hls_cleanup on;
  
                      dash on;
  
                      dash_path /usr/share/nginx/dash; #Sets MPEG-DASH playlist and fragment directory. If the directory does not exists it will be created.
  
                      dash_fragment 1; #Sets MPEG-DASH fragment length. Defaults to 5 seconds.
  
                      dash_playlist_length 10; #Sets MPEG-DASH playlist length. Defaults to 30 seconds.
  
  
  
                      dash_cleanup on; `
  
                     } 
  
  }

• ffmpeg pause and resume live stream encode

  14 janvier 2021, par ayylmao

  I am trying to use ffmpeg to create a live stream from a video file, encoded on the fly, that can be paused and resumed (like what Plex does). Suspending the ffmpeg process pauses the encoding, but resuming it causes ffmpeg to try to catch up to where it would have been in the stream. I assume there is some kind of internal timestamp that ffmpeg is looking at to keep track of timing. I would like ffmpeg to continue encoding from where it left off.

  


  I am using the "-re" switch to read the file at it's native framerate. I have tried hls and dash formats ; as far as I can tell, they both behave the same. Segmenting the entire file beforehand is not an option, I would like to be able to stream using only temporary files created on the fly.

  


  Here are simplified commands I've been using.

  


  HLS :
ffmpeg -y -re -i "input.mkv" -movflags +frag_keyframe+empty_moov+faststart -f hls -hls_time 2 -hls_list_size 10 -hls_delete_threshold 1 -hls_flags split_by_time+delete_segments+second_level_segment_index -strftime playlist.m3u8

  


  DASH :
ffmpeg -re -i input.mkv" -f dash -seg_duration 2 -window_size 5 -extra_window_size 0 -remove_at_exit 1 playlist.m3u8

  


• mp3/aac trim precision issue

  27 janvier 2020, par Massimo Vantaggio

  Due to mp3/aac codec doesn’t support that level of trim precision so im unable to get rounded container duration (without this 6 ms) :

  ffprobe -v error -show_entries format=duration \
  
  >   -of default=noprint_wrappers=1:nokey=1 output_audio.mp4
  
  372.006000

  MP4box generation get 6 ms more for every cycle :

  [...]
  
  Next generation scheduled in 3895 ms (DASH time 412006 ms)
  
  [...]
  
  Next generation scheduled in 3895 ms (DASH time 414012 ms)

  My MP4box command :

  MP4Box -dash-live 2000 -subdur 4000 -bound -segment-timeline -no-cache -profile dashavc264:live -subsegs-per-sidx -1 -mpd-refresh 4 -time-shift 16 -min-buffer 2000 -url-template -insert-utc -bs-switching no -run-for 86400000 -dash-ctx ../../live/log.txt -out ../../live/manifest.mpd ../current/output_1080.mp4:bandwidth=4800000#video ../current/output_720.mp4:bandwidth=2400000#video ../current/output_360.mp4:bandwidth=800000#video ../current/output_audio.mp4:bandwidth=384000#audio

  after 50% of the advertised duration an error will occur (probably)

  I say probably because the time for testing it is very long so may ask if the mp4box command provide for a stable loop or if the error will occur, and if yes, it will occur, may ask an help to debug my command line on mp4box to avoid this issue ?

  Im sorry but trial and error it’s too long since every try is about 24 hours..

  Dash.js web based purpose.

  Thansk in advance !