Recherche avancée

Sur d’autres sites (5856)

• OpenCV+ffmpeg : Set max_analyze_duration ?

  3 avril 2013, par Christian Jonassen

  import sys
  
  import cv
  
  
  
  video = "http://192.168.1.15:8000/video.mjpg" # from motion
  
  capture = cv.CaptureFromFile(video)
  
  print capture
  
  cv.NamedWindow('Stream', 1 )
  
  
  
  while True:
  
    frame = cv.QueryFrame(capture)
  
  
  
    if frame is None:
  
      print "No frame, exiting program"
  
      break
  
    else:
  
      cv.ShowImage('Stream', frame)
  
      cv.WaitKey(20)

  , which sort of works. Meaning that after a while, I get

  Using network protocols without global network initialization. Please use avformat_network_init(), this will become mandatory later.
  
  Using network protocols without global network initialization. Please use avformat_network_init(), this will become mandatory later.
  
  [mjpeg @ 0xb46720] max_analyze_duration reached
  
  [mjpeg @ 0xb46720] Estimating duration from bitrate, this may be inaccurate
  
  Using network protocols without global network initialization. Please use avformat_network_init(), this will become mandatory later.
  
  Using network protocols without global network initialization. Please use avformat_network_init(), this will become mandatory later.
  
  [mjpeg @ 0xb46720] max_analyze_duration reached
  
  [mjpeg @ 0xb46720] Estimating duration from bitrate, this may be inaccurate
  
  <capture 0x7f0aed25c630="0x7f0aed25c630">
  
  </capture>

  The stream then works fine (it's a bit speedy in the start).

  It makes sense : FFMPEG finds the stream mysterious, and therefore analyzes it for the maximum duration, which makes the buffer full, and hence the speediness at the start. Now, is there a way I can (without recompiling FFMPEG) set max_analyze_duration, or otherwise pass some hints to FFMPEG so that it doesn't analyse the stream until max_analyze_duration has passed ?

  The stream is from the motion program : an MJPEG stream of 10 FPS with 640x480.

• FFMPEG Audio/Video out of sync after transcoding video in segments

  25 mai 2017, par Idan

  My system transcodes videos in a very specific way.

  1. separating the video and the audio
  2. transcoding the audio stream
  3. segmenting the video
  4. transcoding each of the segments of the video
  5. concat all segments back to 1 video
  6. merging the new transcoded video and audio back together

  While at 99% of the times the process works as it should and the result is a valid video+audio file. in 1% of the times, I get the video and audio out of sync.

  When investigated the issue I noticed that the sync issue appears in a specific segment/s. Meaning, if the video was sliced into 100 segments, the sync can be ok for the first 50 segments, then something happens and the audio or video gets an offset and goes out of sync. It can occur in any number of segments in one video.

  I guess it’s something to do with timestamps getting lost in the process and segments changing their length in the process but I have no idea how I can overcome it. Open for suggestions.

  The commands I use for each step (paths were shorten and may not match, not real issue there) :

  Segmenting the video :

  ffmpeg -fflags +genpts -i $INPUT_FILE -c copy -map 0:0 -flags -global_header -segment_time 10 -break_non_keyframes 0 -reset_timestamps 1 -segment_list segments.list -segment_list_type ffconcat -write_empty_segments 0 -segment_format mp4 -f segment seg-%d.mp4

  Transcoding audio :

  ffmpeg -i $INPUT_FILE  -vn -c:a aac -threads 1 -ac 2 -b:a 125588 audio.mp4

  Transcoding each of the segments :

  ffmpeg -y -i $f -an -vcodec libx264 -threads 4 -r 30 -pix_fmt yuv420p -crf 20 -preset:v fast -profile:v main -level:v 4.1 transcoded/$f

  Concat segments :

  ffmpeg -y -f concat -i segments.list  -c copy -movflags +faststart file_video.mp4

  Combine video and audio :

  ffmpeg -y -i file_video.mp4 -i file_audio.mp4 -c copy -shortest file_out.mp4

• rtsp : rename certain options after a deprecation period

  25 janvier 2018, par wm4

  rtsp : rename certain options after a deprecation period
  The "timeout" option name inherently clashes with the meaning of the
  
  HTTP libavformat protocol option with the same name. Rename it after a
  
  deprecation period to make it compatible with the HTTP one.
  

  • [DH] doc/APIchanges
  • [DH] libavformat/rtsp.c
  • [DH] libavformat/version.h