Recherche avancée

Sur d’autres sites (5545)

• ffmpeg.so in PHP exec converting and no return

  13 juin 2015, par Tom

  I have seen many threads, but none working ones, so this is my issue :

  I have server installed ffmpeg (ffmpeg-php version 0.7.0, PHP Version 5.4.41) Linux CentOS 6 64bit :

  Using PHP :

  exec('/usr/lib64/php/modules/ffmpeg.so -i test.mp4 testdone.avi',$out,$ret);

  or

  exec('/usr/lib64/php/modules/ffmpeg.so -i /var/www/html/test.mp4 /var/www/html/testdone.avi',$out,$ret);

  or

  exec('/usr/lib64/php/modules/ffmpeg.so -i /var/www/html/test.mp4 /var/www/html/testdone.avi'.' 2>&1',$out,$ret);  

  the ffmpeg is actually found, but always returns : array(0) { } int(11) and with 2>&1 returns array(0) { } int(139) and does not return anything else like testdone.avi in the directory or -version (in the directory). Directories /var/www/html/ are set to 777.

  Thank you, should I hire someone to fix this or am I missing something in PHP.

• {avcodec,tests} : rename the bundled Mesa AV1 vulkan video headers

  14 février 2024, par Jan Ekström

  avcodec,tests : rename the bundled Mesa AV1 vulkan video headers
  This together with adjusting the inclusion define allows for the
  
  build to not fail with latest Vulkan-Headers that contain the
  
  stabilized Vulkan AV1 decoding definitions.
  Compilation fails currently as the AV1 header is getting included
  
  via hwcontext_vulkan.h -> <vulkan/vulkan.h> -> vulkan_core.h, which
  
  finally includes vk_video/vulkan_video_codec_av1std.h and the decode
  
  header, leading to the bundled header to never defining anything
  
  due to the inclusion define being the same.
  This fix is imperfect, as it leads to additional re-definition
  
  warnings for things such as
  
  VK_STD_VULKAN_VIDEO_CODEC_AV1_DECODE_SPEC_VERSION. , but it is
  
  not clear how to otherwise have the bundled version trump the
  
  actually standardized one for a short-term compilation fix.
  

  • [DH] libavcodec/Makefile
  • [DH] libavcodec/vulkan_video.h
  • [DH] libavcodec/vulkan_video_codec_av1std.h
  • [DH] libavcodec/vulkan_video_codec_av1std_decode.h
  • [DH] libavcodec/vulkan_video_codec_av1std_decode_mesa.h
  • [DH] libavcodec/vulkan_video_codec_av1std_mesa.h
  • [DH] tests/ref/fate/source

• Input seeking for frame at specified timestamp with Py-AV

  9 décembre 2019, par neonScarecrow

  I have a project already using Py-AV and am trying to replicate a specific ffmpeg command. The goal is to get a frame roughly around the specified timestamp.

  Here’s the ffmpeg commmand :
  https://trac.ffmpeg.org/wiki/Seeking

  ffmpeg -ss 14 -i https://some_url.mp4 -frames:v 1 frame_at_14_seconds.jpg

  Here’s my code :

      #return one frame around 14 seconds into the movie
  
      target_sec = 14 
  
      container = av.open('https://some_url.mp4', 'r')
  
      container.streams.video[0].thread_type = 'AUTO'
  
      video_stream = next(s for s in container.streams if s.type == 'video')
  
      time_base = float(video_stream.time_base)
  
      target_timestamp = int(target_sec / time_base) + video_stream.start_time
  
      video_stream.seek(target_timestamp)
  
      for frame in container.decode(video_stream):
  
          frame.to_image().save('frame_at_14_seconds.jpg')
  
          break

  Additionally, I have found any documentation about this, but does anyone know if either command (ffmpeg/av.open) is downloading the entire file to a tmp file behind the scenes. I’m looking for a less memory-intensive way to read a frame for every second in an up to 60 second video.