Recherche avancée

Sur d’autres sites (8539)

• Updating ffmpeg on Ubuntu 12.04 ; conflicts with old version from standard repository

  29 octobre 2016, par Frank van Wensveen

  I have never used ffmpeg on my Ubuntu Linux 12.04 (Precise Pangolin) box until now. Typing ’ffmpeg’ at the command prompt revealed that ffmpeg 0.8.17 (listed as ffmpeg 0.8.17-4:0.8.17-0ubuntu0.12.04.2) was installed. Seeing as I need to convert h.265 to h.264, an update was obviously required.

  Following posted instructions, I installed a ream of packages :

  $ sudo apt-get install faad libmp4v2-dev libfaac0 libfaac-dev
  
  libxvidcore4 libxvidcore4-dev liba52-0.7.4 liba52-0.7.4-dev libx264-dev
  
  libgsm-tools libogg-dev libtheora-bin libfaad-dev libvorbis-dev 
  
  libtheora-dev libdts-dev git-core yasm texi2html checkinstall

  followed by

  $ sudo apt-get purge ffmpeg

  in order to get rid of the old stuff from the original repo.

  Downloaded the latest ffmpeg, and a ."/configure ; make ; sudo make install" later, I should be in business.

  Except that typing ’ffmpeg’ at the prompt still fired up the old version. A quick look revealed that the old ffmpeg binary was still sitting in /usr/bin with the new one being installed in /usr/local/bin. But ffmpeg is no longer listed as an installed package, and sudo apt-get remove ffmpeg tells me that "Package ffmpeg is not installed, so not removed".

  Running /usr/local/bin/ffmpeg directly works, however then fails in an Unknown encoder ’libx264’ error. Which is puzzling because the package libx264-120 is installed and /usr/lib/i386-linux-gnu/libx264.so.120 (with the appropriate symlink to /usr/lib/i386-linux-gnu/libx264.so) does exist.

  Maybe I’ve been looking at this for too long, because I’m sure this is a simple issue but I just can’t see it.

  Can someone please hand me the stupid had and point out why I deserve to wear it ?

  Tnx !

• Updating ffmpeg on Ubuntu 12.04 ; conflicts with old version from standard repository

  29 octobre 2016, par Frank van Wensveen

  I have never used ffmpeg on my Ubuntu Linux 12.04 (Precise Pangolin) box until now. Typing ’ffmpeg’ at the command prompt revealed that ffmpeg 0.8.17 (listed as ffmpeg 0.8.17-4:0.8.17-0ubuntu0.12.04.2) was installed. Seeing as I need to convert h.265 to h.264, an update was obviously required.

  Following posted instructions, I installed a ream of packages :

  $ sudo apt-get install faad libmp4v2-dev libfaac0 libfaac-dev
  
  libxvidcore4 libxvidcore4-dev liba52-0.7.4 liba52-0.7.4-dev libx264-dev
  
  libgsm-tools libogg-dev libtheora-bin libfaad-dev libvorbis-dev 
  
  libtheora-dev libdts-dev git-core yasm texi2html checkinstall

  followed by

  $ sudo apt-get purge ffmpeg

  in order to get rid of the old stuff from the original repo.

  Downloaded the latest ffmpeg, and a ."/configure ; make ; sudo make install" later, I should be in business.

  Except that typing ’ffmpeg’ at the prompt still fired up the old version. A quick look revealed that the old ffmpeg binary was still sitting in /usr/bin with the new one being installed in /usr/local/bin. But ffmpeg is no longer listed as an installed package, and sudo apt-get remove ffmpeg tells me that "Package ffmpeg is not installed, so not removed".

  Running /usr/local/bin/ffmpeg directly works, however then fails in an Unknown encoder ’libx264’ error. Which is puzzling because the package libx264-120 is installed and /usr/lib/i386-linux-gnu/libx264.so.120 (with the appropriate symlink to /usr/lib/i386-linux-gnu/libx264.so) does exist.

  Maybe I’ve been looking at this for too long, because I’m sure this is a simple issue but I just can’t see it.

  Can someone please hand me the stupid had and point out why I deserve to wear it ?

  Tnx !

• Is there a fix for the 'flashing console' bug with FFMPEG ?

  29 août 2022, par NedNoodleHead

  When using a compiled a program that utilizes FFMPEG (Not library, but the path to the exe), and a GUI library ; that has a function that uses FFMPEG, a console window from FFMPEG will quickly open and disappear.

  


  I have a github repo that can be used to reproduce the bug : https://github.com/nednoodlehead/ffmpegthreading

  


  I also have a quick youtube video showing what the bug looks like, and what it should look like : https://www.youtube.com/watch?v=tCZ0z9E5Iyw

  


  A few things to note with this :

  


  1). This will only occur when the app is compiled. Running this in a virtual environment works as expected. I run it from my IDE all the time with no console flashing. (as seen in video)

  


  2). It will only flash while a GUI is present. So using a regular script to call the same command that produces the bug will NOT cause the bug

  


  3). The bug was tested in Tkinter and PyQt5 and produced the same result (flashing console)

  


  4). Threading is NOT needed to reproduce this bug, it just makes the debugging a bit easier

  


  5). Using the ffmpeg module does not work as my entire project is based around an interface for PyDub (Which uses ffmpeg)

  


  6). This solution does not work for me : How to hide console output of FFmpeg in Python ? (Because this uses the module, while I use the exe)

  


  7). I am using auto-py-to-exe to compile (which uses pyinstaller)

  


  8). Running 'ffmpeg -version' (in regular cmd (same result in venv)) gives : ffmpeg version N-106605-gf67403edb3-20220413

  


  I would appreciate any help, this is tying my brain up.