Recherche avancée

Sur d’autres sites (6610)

• FFMPEG Batch Convert for Windows [duplicate]

  11 avril 2019, par Ash_dog

  This question already has an answer here :

  • How do you convert an entire directory with ffmpeg ?
    
    14 answers
    

  I’ve been trying to convert entire folders of files using ffmpeg for a long time now. I’ve searched the web, found various answers, but none that helped me. Currently I’m using multiple instances of ffmpeg to convert more than one file at a time. But it’s very time consuming and annoying to type in everything all the time, even with copy/paste.

  To simplify my current code it would look something like this. I specify the input file and the output format (+ various settings) :

   ffmpeg -i "EXAMPLE.avi" newEXAMPLE.mp4

  But what I would like is a single instance of ffmpeg to convert all files in a specific folder to a new format and for the files to keep their original name.

  example1.avi > example1.mp4

  example2.avi > example2.mp4

  example3.avi > example3.mp4

  and so on...

  PS. I’m a bit new to these kind of things, so I’d much appreciate an explanation with your answer, so I can understand and learn. Thank you !

• avutil/hwcontext_dxva2 : Don’t improperly free IDirect3DSurface9 objects

  16 mai 2017, par Aaron Levinson

  avutil/hwcontext_dxva2 : Don’t improperly free IDirect3DSurface9 objects
  Add dxva2_pool_release_dummy() and use it in call to
  
  av_buffer_create() in dxva2_pool_alloc().
  Prior to this change, av_buffer_create() was called with NULL for the
  
  third argument, which indicates that av_buffer_default_free() should
  
  be used to free the buffer’s data.  Eventually, it gets to
  
  buffer_pool_free() and calls buf->free() on a surface object (which is
  
  av_buffer_default_free()).
  This can result in a crash when the debug version of the C-runtime is
  
  used on Windows.  While it doesn’t appear to result in a crash when
  
  the release version of the C-runtime is used on Windows, it likely
  
  results in memory corruption, since av_free() is being called on
  
  memory that was allocated using
  
  IDirectXVideoAccelerationService::CreateSurface().
  Signed-off-by : Aaron Levinson <alevinsn@aracnet.com>
  
  Reviewed-by : wm4 <nfxjfg@googlemail.com>
  
  Reviewed-by : Steven Liu <lingjiujianke@gmail.com>
  
  Reviewed-by : Mark Thompson <sw@jkqxz.net>
  
  Signed-off-by : Anton Khirnov <anton@khirnov.net>
  

  • [DBH] libavutil/hwcontext_dxva2.c

• avutil/hwcontext_dxva2 : Don't improperly free IDirect3DSurface9 objects

  16 mai 2017, par Aaron Levinson

  avutil/hwcontext_dxva2 : Don't improperly free IDirect3DSurface9 objects
  Add dxva2_pool_release_dummy() and use it in call to
  
  av_buffer_create() in dxva2_pool_alloc().
  Prior to this change, av_buffer_create() was called with NULL for the
  
  third argument, which indicates that av_buffer_default_free() should
  
  be used to free the buffer's data.  Eventually, it gets to
  
  buffer_pool_free() and calls buf->free() on a surface object (which is
  
  av_buffer_default_free()).
  This can result in a crash when the debug version of the C-runtime is
  
  used on Windows.  While it doesn't appear to result in a crash when
  
  the release version of the C-runtime is used on Windows, it likely
  
  results in memory corruption, since av_free() is being called on
  
  memory that was allocated using
  
  IDirectXVideoAccelerationService::CreateSurface().
  Signed-off-by : Aaron Levinson <alevinsn@aracnet.com>
  
  Reviewed-by : wm4 <nfxjfg@googlemail.com>
  
  Reviewed-by : Steven Liu <lingjiujianke@gmail.com>
  
  Reviewed-by : Mark Thompson <sw@jkqxz.net>
  

  • [DH] libavutil/hwcontext_dxva2.c