Recherche avancée

Sur d’autres sites (7452)

• FFMPEG : Remove packets based on PTS/DTS

  9 mai 2018, par stevendesu

  I have a video which contains some audio packets beyond the end of the video data :

  $> ffprobe -show_packets video.mp4
  
  ...
  
  ...
  
  ...
  
  [PACKET]
  
  codec_type=video
  
  stream_index=0
  
  pts=5653648
  
  pts_time=235.568667
  
  dts=5653648
  
  dts_time=235.568667
  
  duration=1001
  
  duration_time=0.041708
  
  convergence_duration=N/A
  
  convergence_duration_time=N/A
  
  size=1030
  
  pos=25233684
  
  flags=__
  
  [/PACKET]
  
  [PACKET]
  
  codec_type=audio
  
  stream_index=1
  
  pts=11310080
  
  pts_time=235.626667
  
  dts=11310080
  
  dts_time=235.626667
  
  duration=1024
  
  duration_time=0.021333
  
  convergence_duration=N/A
  
  convergence_duration_time=N/A
  
  size=284
  
  pos=25234714
  
  flags=K_
  
  [/PACKET]
  
  [PACKET]
  
  codec_type=audio
  
  stream_index=1
  
  pts=11311104
  
  pts_time=235.648000
  
  dts=11311104
  
  dts_time=235.648000
  
  duration=1024
  
  duration_time=0.021333
  
  convergence_duration=N/A
  
  convergence_duration_time=N/A
  
  size=285
  
  pos=25234998
  
  flags=K_
  
  [/PACKET]
  
  [PACKET]
  
  codec_type=audio
  
  stream_index=1
  
  pts=11312128
  
  pts_time=235.669333
  
  dts=11312128
  
  dts_time=235.669333
  
  duration=992
  
  duration_time=0.020667
  
  convergence_duration=N/A
  
  convergence_duration_time=N/A
  
  size=290
  
  pos=25235283
  
  flags=K_
  
  [/PACKET]
  
  $>

  The last video packet in the video has a PTS time of 235.568667 and a duration of 0.041708 - meaning all video data ends at 235.610375. However there are audio packets beginning at 235.626667 and later.

  Is there an easy way to strip these audio packets from the file so that the audio and video end simultaneously ?

• ffmpeg : improving MP4 to webm ogg conversions

  14 juillet 2017, par Randy

  (Edited to include some of the things I’ve tried)

  I’m a musician, and occasional web coder. I’ve been using video editing software (old version of Roxio Videowave from 2011) to build promotional videos from clips of some of my performances, and I’d like to put some of them on my own web pages in HTML5 video format. So that currently means I need MP4, WEBM, and OGG conversions. Fortunately the editing software churns out some very nice MP4 (H264) files, and has plenty of options for doing so. I purposely output the output size about 2X the likely display size, in hopes of offering more detail for better conversions. Specifically, the video output was AVC/H.264, 800 x 450, 30fps, variable bit rate, but with 600000 as a base line (that was the default for this setting anyway).

  Now I’m nowhere near expert at this stuff, and I probably left out some important data. But bottom line, the resulting MP4 looked very good. Unfortunately, to put it on my own web page means at least converting to WEBM and OGG formats. It would be nice if all browsers just supported MP4, but then there would be licensing fees, so conversions are needed. Sadly, I’ve been wasting days now trying to do this with ffmpeg. Its easy to do, its doing it WELL that is a mystery to me. Just letting ffmpeg work using its defaults (meaning I just specify an input and output file) results in pretty terrible video. But I’ve also tried most of the settings for better quality available, and the resulting conversions are nowhere near as good as youtube’s conversions.

  Based on the info about my original MP4 file, can someone suggest some better settings for ffmpeg conversions to WEBM and OGG ? Am I going about this all wrong ? The best I’ve done so far was with a string like this, which specified a high quality and a fairly robust bit rate...

  ffmpeg -i input-file.mp4 -c:v libvpx -crf 10 -b:v 1M -c:a libvorbis output-file.webm

  That was much better than the default settings, but still nowhere near the quality of YOUTUBE conversions. In my resulting WEBM video, you can pretty plainly see how the picture degrades, and will snap into focus every few seconds when a "key frame" comes up. These artifacts should not be so obvious. Thanks for any help.

• ffmpeg : transmission problems / artifacts in rtsp screen grab - might be a WiFi problem

  1er décembre 2022, par Jo Kerner

  In short : Is there a way to "force" ffmpeg to not save a grabbed frame if there are transmission problems ? Or any other software that does the same and I just don't know of ?

  


  Long story :

  


  Updating my house surveillance from almost 10 years old DCS-932L cameras to Tapo C100 Cameras, I changed the image delivery method from ftp push to rtsp grab via ffmpeg.

  


  I had written a program in C++ to check for "bad" pictures from the old cameras, where parts of the picture tended to be simply black once every minute or so (I'm grabbing a pic every 2 seconds). The Tapo C100 doesn't feature ftp-push, thus I tried (after a few days trying)

  


  ffmpeg.exe -y -i rtsp://user:pass@10.0.0.%ld:554/stream1 -vframes 1 %scamera\rtsp.jpg -loglevel quiet


  


  This works absolutely perfect in my main house, which features a Fritz !Box 7590 and a set of Fritz !Powerline (510/and two 540e) repeaters, plus one WiFi repeater Fritz 600) as my phone line and the router are in the basement.

  


  In my holiday home, though, it doesn't. The Wifi is managed by a Hybrid DSL/5G - box I have no alternative to, which is a Huawei DN9245W and works as DHCP Server, because this is almost impossible to change. Everything "real" is managed by another Fritz !Box 7590, connected via ethernet, and another set of Fritz !Powerline 510 and two 540e repeaters plus half a dozen Wifi Repeaters, mostly Fritz ! 310, 450E and 600. The house was partially built with local stones, which are very iron-y, and there's a lot of metallized glass. Full set is show in Image

  


  Now, this does produce different artifacts, about two per minute or in every 15th picture, see
Image with artifacts No. 1

  


  Thinking this might be a transmission problem, I tried forcing the streamgrab via TCP, because while rtsp doesn't have error correction, TCP does :

  


  ffmpeg.exe -rtsp_transport tcp -i
rtsp://user:pass@10.0.0.%ld:554/stream1 -y -f image2 -update 1 -r
1 -vframes 1 -qscale:v 30 %scamera\rtsp.jpg -loglevel quiet


  


  Which didn't change the artifacts much, see Image with artifacts No. 2

  


  The house now has a total of 12 Cameras, six of which are each "managed" by an older Dell Optiplex Desktop bought used off ebay with an i3 or i5 processor from about 2015, which goes to about 65% load. My software will check if the grabbed picture is finished saving (to RAMdisk), rename it, check if there are artifacts, if so, drop it, if not, convert to bitmap and then compare it to previous image, guess if there's a change, mark that change with a rhombus and rate it, save that as a jpeg file, and then some other stuff that's not relevant here. See : Image of my program running with six cameras

  


  I did try grabbing keyframes only, but a bunny or deer or burglar hopping through my property doesn't produce a keyframe, so that turned out to be missing the point.

  


  I'm out of ideas here. It does work flawlessly in the main house. It doesn't in the holiday house. I can hardly install more repeaters ; I already tried mesh and not-mesh, and the problem isn't exactly wifi overload, because even with just one camera running, it still persists. In certain places. Some have no problems. Reasons ? No clue. I really hope someone has a good idea.