Sur d’autres sites (11798)

• Make mime-type award a bonus probe score

  21 novembre 2023, par Peter Zebühr

  Make mime-type award a bonus probe score
  This changes the default behaviour of ffmpeg where content-type headers
  
  on an input gives an absolut probe score (of 75) to instead give a bonus
  
  score (of 30). This gives the probe a better chance to arrive at the
  
  correct format by (hopefully) giving a large enough bonus to push edge
  
  cases in the right direction (MPEG-PS vs MP3, I am looking at you) while
  
  also not adversly punishing clearer cases (raw ADTS marked as
  
  "audio/mpeg" for example).
  This patch was regression tested against 20 million recent podcast
  
  submissions (after content-type propagation was added to
  
  original-storage), and 50k Juno vodcasts submissions (dito). No adverse
  
  effects observed (but the bonus may still need tweaking if other edge
  
  cases are detected in production).
  

  • [DH] libavformat/avformat.h
  • [DH] libavformat/format.c
  • [DH] libavformat/libopenmpt.c

• lavu/hwcontext_vulkan : support mapping VUYX, P012, and XV36

  20 août 2022, par Philip Langdale

  lavu/hwcontext_vulkan : support mapping VUYX, P012, and XV36
  If we want to be able to map between VAAPI and Vulkan (to do Vulkan
  
  filtering), we need to have matching formats on each side.
  The mappings here are not exact. In the same way that P010 is still
  
  mapped to full 16 bit formats, P012 has to be mapped that way as well.
  Similarly, VUYX has to be mapped to an alpha-equipped format, and XV36
  
  has to be mapped to a fully 16bit alpha-equipped format.
  While Vulkan seems to fundamentally lack formats with an undefined,
  
  but physically present, alpha channel, it has have 10X6 and 12X4
  
  formats that you could imagine using for P010, P012 and XV36, but these
  
  formats don't support the STORAGE usage flag. Today, hwcontext_vulkan
  
  requires all formats to be storable because it wants to be able to use
  
  them to create writable images. Until that changes, which might happen,
  
  we have to restrict the set of formats we use.
  Finally, when mapping a Vulkan image back to vaapi, I observed that
  
  the VK_FORMAT_R16G16B16A16_UNORM format we have to use for XV36 going
  
  to Vulkan is mapped to Y416 when going to vaapi (which makes sense as
  
  it's the exact matching format) so I had to add an entry for it even
  
  though we don't use it directly.
  

  • [DH] libavutil/hwcontext_vulkan.c
  • [DH] libavutil/version.h

• PHP HTML5 compatible MP4 video using FFMPEG

  9 août 2013, par Annie

  Hi I am using FFMPEG to convert the uploaded video with PHP.

  echo "conversion exercise started...<br /><br />";
  
  
  
  /* looping through all files in the directory */
  
  if ($handle = opendir(&#39;assets/uploaded_videos&#39;)) {
  
      while (false !== ($entry = readdir($handle))) {
  
  
  
          /* filtering the desired extensions */
  
          if ($entry != "." &amp;&amp; $entry != ".." &amp;&amp; in_array(substr($entry, strrpos($entry, &#39;.&#39;)), array(".wmv", ".mpg", ".mpeg", ".flv", ".ogg", ".mp4")))
  
          {
  
              $filename = substr($entry, 0, strrpos($entry, &#39;.&#39;));
  
  
  
              //$command = "ffmpeg -i assets/uploaded_videos/$entry -vcodec libx264 assetss/videos/$filename.mp4";
  
  
  
              $command = "ffmpeg -i assets/uploaded_videos/$entry -vcodec mpeg4 -acodec libfaac files/videos/$filename.mp4";
  
  
  
              echo $command."<br />";
  
  
  
              shell_exec($command."> /dev/null 2>/dev/null &amp;");
  
          }
  
      }
  
      closedir($handle);
  
  }

  I have embedded the player in view file like this :

  <video width="350" poster="&lt;?php echo $first_video[&#39;thumb_path&#39;];?>" controls="controls">
  
      <source src="&lt;?php echo $first_video[&#39;video_path&#39;]; ?>"></source>
  
      <span></span>
  
  </video>

  Now, when I run in IE10, the player gives me invalid source error. I am having this issue with both libx264 and mpeg4 MP4 codecs.

  Any ideas whats going wrong ?

  Update

  Following Ian's direction, I finally get it working. I have used baseline-level3 profile with libx264. You can provide extra parameters but I guess profile is the key ! I experimented couple of profiles and observed that all HTML5 videos on vimeo and youtube use this baseline L3 profile.

  Anyone struggling with MP4 can consider the following command for conversion :

  /* following command converted all my uploaded *.wmv files to mp4 */
  
  $command = "ffmpeg -i files/uploaded_videos/$entry -vcodec libx264 -profile:v baseline -level 3 files/videos/$filename.mp4";