Recherche avancée

Sur d’autres sites (7649)

• How to sync multiple rtsp inputs in ffmpeg ?

  9 décembre 2019, par KOMsandFriends

  I am combining multiple rtsp streams from local network cameras to a single output using ffmpeg. In the resulting video, the videos are out of sync.

  ffmpeg -loglevel warning \
  
          -f image2 -loop 1 \
  
          -i logo.png \
  
          -rtsp_transport tcp -thread_queue_size 1024 \
  
          -i "rtsp://10.0.0.1" \
  
          -rtsp_transport tcp -thread_queue_size 1024 \
  
          -i "rtsp://10.0.0.2" \
  
          -rtsp_transport tcp -thread_queue_size 1024 \
  
          -i "rtsp://10.0.0.3" \
  
          -filter_complex "[3:v][2:v][0:v][1:v]xstack=inputs=4:layout=0_0|w0_0|0_h0|w0_h0[v]" \
  
          -map "[v]" \
  
          -filter_complex "[1:a][1:a]amerge=inputs=2[aout]" -map "[aout]" \
  
          -vcodec libx264 -pix_fmt yuv420p -r 30 -g 60 \
  
          -preset fast -b:v 2400k -maxrate 4600k -bufsize 6000k \
  
          -acodec aac -ar 44100 -b:a 128k \
  
          -f flv "rtmp://live-api-s.facebook.com:80/rtmp/$STREAMKEY"

  If we take the first input (0) (10.0.0.1) as reference, the second input (1) is initially about 1000ms ahead, the third input (2) is about 2000ms ahead. It looks like the offset is even slightly increasing over time.

  I tried to exchange the different inputs (e.g. 10.0.0.3 to input 0, 10.0.0.1 to input 2), then 10.0.0.1 is ahead of 10.0.0.3. So I would assume this is a matter of ffmpeg and how it processes the inputs.

  How could I sync the different sources in the output ?

• Announcing TMPGEnc 4 : now with x264 !

  26 novembre 2010, par Dark Shikari — commercial, japan, licensing, x264

  A few months ago, we announced a commercial licensing program so that even companies unable to use GPL software in their products have a chance to use the open source x264 instead of proprietary alternatives. The system worked on two basic concepts. First, all licensees would still be required to give their changes to x264 back to us : x264 must forever remain free, with no useful contributions kept hidden from the community. Second, all the profits would go directly back to x264, primarily to the developers who’ve made the most significant contributions to x264 over the years, but also to funding future development, bounties for new features, as well as contributing to other related projects (e.g. Videolan and ffmpeg).

  Over the past couple of months, we’ve gotten an enormous response ; over 40 companies have inquired about licensing, with more contacting us every day. Due to the sheer volume of interest, we’ve partnered with CoreCodec, the creators of the free Matroska container format and developers of CoreAVC, to make x264 as widely available as possible in the world of commercial software as it is in the world of open source. All of this is already filtering back to benefiting x264 users, with many bugs being reported by commercial licensees as well as some code contributed.

  Today, we announce the first commercial consumer encoding software to switch to x264 : Pegasys Inc.’s TMPGEnc. Expect many more to follow : with x264 now available commercially as well as freely, there are few excuses left to use any other H.264 encoder. Vendors of overpriced, underpowered proprietary competitors should begin looking for new jobs.

  (Pegasys press release : English, Japanese)

• Unable see video after encoding it using ffmpeg

  22 septembre 2015, par Sharathreddy

  I have used ffmpeg for video encoding using following parameters.

  ffmpeg -i movie.mov -c:v libx264 -preset slow -b:v 500k -maxrate 500k -bufsize 1000k -s 480x360 -acodec libvo_aacenc -b:a 128k -async 1 -movflags faststart -y movie.mp4

  "movie.mov" successfully encoded and created "movie.mp4".
  But when I play movie.mp4 in windows media player or android player, blank screen appears but the movie is playing since I’m able hear audio.
  Is there any way to re-encode movie.mp4 so that I can get video.