Recherche avancée

Sur d’autres sites (9986)

• Pack ffmpeg executable insde myProject's executable to run

  8 décembre 2023, par zur

  TLDR ;

  


  I would like to pack the ffmpeg executable inside my own executable. Currently I am getting

  


  FileNotFoundError: [Errno 2] No such file or directory: 'ffmpeg'
Skipping ./testFile202312061352.mp4 due to FileNotFoundError: [Errno 2] No such file or directory: 'ffmpeg'


  


  Details :

  


  I am creating executable file using following command :

  


  pyinstaller cli.py \&#xA;  --onefile \&#xA;  --add-binary /Users/<machineuser>/anaconda3/envs/my_env/bin/ffmpeg:bin&#xA;</machineuser>

  


  The code that uses ffmpeg is not authored by me. And I would like to keep that part the same. I hope that when I run from command line while conda environment is active I can successfully run it as python (or perhaps anaconda) knows where the binaries are. May be there is some environment variable that is pointing to /Users/<machineuser>/anaconda3/envs/my_env/bin/</machineuser> I have a pretty empty cli.py. That seems to be the entry point and I hope if it is possible I can set the bin directory's path there ...

  


  I am able to successfully run the application like following :

  


  (my_env) machineUser folder % "dist/cli_mac_001202312051431" ./testFile202312061352.mp4


  


  I would like to run like following :

  


  (base) machineUser folder % "dist/cli_mac_001202312051431" ./testFile202312061352.mp4


  


  I would like to keep the world out side my executable's tmp folder the same. I would not want to change something that will be "left behind" after the exec is terminated.

  


  Question :

  


  Can some one please mention how to modify the pyinstaller command or what to change in cli.py to achieve it successfully ?

  


• avformat/mxfdec : treat Random Index Pack as end of file

  26 mars 2023, par Marton Balint

  avformat/mxfdec : treat Random Index Pack as end of file
  RIP, if exists is the last KLV item in the MXF files therefore we can stop
  
  parsing the file if it is encountered. This allows us to support files created by
  
  broken muxers such as OpenCube MXFTk Advanced 2.8.0.0.1. which dumps some extra
  
  garbage after the RIP.
  Signed-off-by : Marton Balint <cus@passwd.hu>
  

  • [DH] libavformat/mxfdec.c

• 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.