Recherche avancée

Sur d’autres sites (5684)

• avcodec/metasound_data : Fix inconsistency in tables

  22 octobre 2013, par Michael Niedermayer

  avcodec/metasound_data : Fix inconsistency in tables
  Fixes out of array read
  This issue can be reproduced with :
  
  Lucky.asf
  
  teuflisch.asf
  
  from http://samples.ffmpeg.org/A-codecs/VoxWare/
  as well as other samples
  fcb16m has 320 elements but the code before the patch can address a
  
  table of 384 elements in its place.
  
  I dont know if theres some elements missing, or its maybe the wrong
  
  table, or if the parameters affecting the table size are wrong, or
  
  if theres something else wrong.
  
  if someone reading this has easy access to some reference. (binary
  
  with the tables in it, spec, whatever, please contact us)
  This solution fixes the inconsistency by padding the table with zeros,
  
  this variant was suggested by Vitor Sessak. And ensures that nothing
  
  currently working breaks.
  Found-by : Mateusz "j00ru" Jurczyk and Gynvael Coldwind
  
  Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] libavcodec/metasound_data.c

• Ffmpeg - convert Aces exr sequence to h264

  25 mars 2023, par Michael B

  I would like to convert an exr sequence to an h264 video. This is fairly easy but the exr sequence is in [AcesCG][1] colourspace which is a colourspace created by [OCIO][2] (an open source colour management solution that has become the standard for VFX).

  


  One solution would be to convert the exrs to a more common colourspace (e.g. srgb or rec709) using [oiio][3] and then use ffmpeg to create an h264 from those images, but that adds an extra step and will be slow. I would like to find a solution where I can directly convert the exrs into an h264 using open source software (e.g. ffmpeg)

  


  [1] : https://en.m.wikipedia.org/wiki/Academy_Color_Encoding_System#:~:text=ACEScg%20(ACES%20computer%20graphics%20space,graphics%20rendering%20and%20compositing%20tools.  ;[2] : https://opencolorio.org/
[3] : https://www.google.com/url?sa=t&source=web&rct=j&url=https://github.com/OpenImageIO/oiio&ved=2ahUKEwjZ9_Gc59D8AhWKdcAKHcG_CUEQFnoECDIQAQ&usg=AOvVaw27FWYrbTnUMqgfYMPRKia_

  


• How to use a framework build of Python with Anaconda

  18 juin 2019, par Addem

  I’m unable to get matplotlib animations to display on a Mac computer. I’ve chased down several attempts at installing ffmpeg but they’ve all failed and I’m starting to wonder if that isn’t the wrong way to solve the problem.

  I found this page.

  Since I’m running Python from the Spyder app in Anaconda, the section for this seems relevant. It says

  The default python provided in (Ana)Conda is not a framework build.
  However, the Conda developers have made it easy to install a framework
  build in both the main environment and in Conda envs. To use this
  install python.app conda install python.app and use pythonw rather
  than python

  I’m not perfectly clear on what this means, but I opened a terminal, ran conda install python.app and it seemed to work—at least there were no error messages. I could navigate to a folder that contained the file python.app.

  I’m not clear on what it means to "use pythonw" but I navigated to the animation I’m trying to compile and ran $ pythonw anim.py and it gave me an I/O error. I’m not sure if I’m supposed to use pythonw in some other way, or what. If I restart and try to run the code in Spyder I get the same error as before.

  I know that the code works, because I’ve run it on a Linux machine that has ffmpeg and it worked.

  Is there something else I need to do to get a framework build, whatever that means ?