Recherche avancée

Sur d’autres sites (5683)

• avfilter/vf_bwdif_cuda : CUDA accelerated bwdif deinterlacer

  30 août 2019, par Philip Langdale

  avfilter/vf_bwdif_cuda : CUDA accelerated bwdif deinterlacer
  I've been sitting on this for 3 1/2 years now(!), and I finally got
  
  around to fixing the loose ends and convincing myself that it was
  
  correct. It follows the same basic structure as yadif_cuda, including
  
  leaving out the edge handling, to avoid expensive branching.
  

  • [DH] Changelog
  • [DH] configure
  • [DH] doc/filters.texi
  • [DH] libavcodec/version.h
  • [DH] libavfilter/Makefile
  • [DH] libavfilter/allfilters.c
  • [DH] libavfilter/vf_bwdif_cuda.c
  • [DH] libavfilter/vf_bwdif_cuda.cu

• lavf/mov.c : offset index timestamps by the minimum pts to make first pts zero

  6 juin 2017, par Sasi Inguva

  lavf/mov.c : offset index timestamps by the minimum pts to make first pts zero
  If the videos starts with B frame, then the minimum composition time
  
  as computed by stts + ctts will be non-zero. Hence we need to shift
  
  the DTS, so that the first pts is zero. This was the intention of that
  
  code-block. However it was subtracting by the wrong amount.
  For example, for one of the videos in the bug nonFormatted.mp4 we have
  stts :
  
  sample_count  duration
  
  960           1001
  ctts :
  
  sample_count  duration
  
  1             3003
  
  2             0
  
  1             3003
  
  ....
  The resulting composition times are :  3003, 1001, 2002, 6006, ...
  The minimum composition time or PTS is 1001, which should be used to
  
  offset DTS. However the code block was wrongly using ctts[0] which is
  
  3003. Hence the PTS was negative. This change computes the minimum pts
  
  encountered while fixing the index, and then subtracts it from all the
  
  timestamps after the edit list fixes are applied.
  Samples files available from :
  https://bugs.chromium.org/p/chromium/issues/detail?id=721451
  
  https://bugs.chromium.org/p/chromium/issues/detail?id=723537
  fate-suite/h264/twofields_packet.mp4 is a similar file starting with 2
  
  B frames. Before this change the PTS of first two B-frames was -6006
  
  and -3003, and I am guessing one of them got dropped when being decoded
  
  and remuxed  to the framecrc before, and now it is not being dropped.
  Signed-off-by : Sasi Inguva <isasi@google.com>
  

  • [DH] libavformat/mov.c
  • [DH] tests/ref/fate/h264-twofields-packet

• Shutil not detecting ffmpeg module and python3 incorrectly, all when compiled with pyinstaller

  9 juin 2021, par vanilla

  Right now I am almost finished with my version of my app. The last thing I am having trouble with is detecting the FFmpeg module, to warn users that they need it for certain features that have been added this version. When I run the script through my python interpreter in terminal, which the directories of it is in my library frameworks directory, The shutil will run as expected and return the version or whatever as I do have it installed. However, when I compile it and launch specifically the one windowed, with no console output, it doesn’t work. Now what I mean by that it returns none type.

  


  From talking to someone in my previous Reddit thread I tried printing out python3 and seeing what directories that would bring with shutil.which(‘python3’). Interesting enough, when put into my tkinter text field (don't have a console) it would bring up my python binary from the directory /usr/bin/python3. The one I have all my modules for it and everything installed on is the one :

  


  >>> import shutil
>>> print(shutil.which('python3'))
/Library/Frameworks/Python.framework/Versions/3.9/bin/python3


  


  So we can see that there are to installations or whatever of python3 interpreters (I believe I am saying this right), and I am confused on maybe I am being hinted to use the python3 binary from /usr/bin/ to compile it with pyinstaller and install the needed modules with /usr/bin/pip3 with it ?

  


  A user from the reddit thread I made below made a alternative :

  


  


  I tested it on my computer after fixing a bug, and both the shutil and os methods work. It seems to be a problem on your end, which is strange. What version of Python do you have ? Also in your script right above testing for ffmpeg, try inserting this line :
print('ffmpeg' in os.listdir('/usr/local/bin'))

  


  


  This other method with os unfortunately returned a None as well. I am ultimately trying to have some kind of method to reliably detect ffmpegs's binary on all operating systems. If anyone can provide some insight as to what may cause problems similar to these or knows other solutions, or can identify some kind of hiccup I can avoid that would be amazing.

  


  I have a hunch since shutil when compiled returned the bin directory for python3 instead of the framework one that actually has all the modules installed, that could mean something to me to try using pyinstaller with that one instead ?

  


  Thanks !

  


  https://www.reddit.com/r/learnpython/comments/nu3a1d/functionallity_supposedly_of_shutilwhichffmpeg/