Recherche avancée

Sur d’autres sites (5409)

• Programmatically convert multiple midi files to wave using timidity, ffmpeg, and bash

  21 mai 2014, par Kyle Nevling

  I am trying to build a script to do as the title says, but I am somewhat unfamiliar with Bash and other online resources have only been so helpful.

  #! /bin/bash
  
  function inout  #Create Function inout
  
  {
  
      output[0]=" " #Initialize variables
  
      input[0]=" "
  
      count=1
  
      while [ "$count" -lt  10 ]; #Start loop to get all filenames
  
      do
  
          echo "Grabbing filename"             #User feedback
  
  
  
          input=$(ls | grep 0$count | grep MID | sed 's/ /\\ /g') #Grab filename
  
          #Replace ' ' character with '\ '
  
          output=$(echo $input | tr 'MID' 'mp3')
  
          #set output filename
  
          echo $count #Output variables for testing
  
          echo $input
  
          echo $output
  
          let count+=1 #Increment counter
  
  
  
          echo "converting $input to $output." #User feedback
  
          foo="timidity $input -Ow -o - | ffmpeg -i - -acodec libmp3lame -ab 320k $output"
  
          echo $foo
  
          #The last two lines are for the purpose of testing the full output
  
          #I can get the program to run if I copy and paste the output from above
  
          #but if I run it directly with the script it fails
  
  
  
      done
  
  }
  
  
  
  inout

  I am trying to figure out why I can’t just run it from inside the script, and why I must copy/paste the output of $foo

  Any ideas ?

• Reduce ffmpeg CPU usage with h265 [closed]

  23 septembre 2024, par Neskelogth

  I have a video file to convert using ffmpeg on Ubuntu 22.04. The input uses the codec h264 and I want to convert it to h265 (mainly for storage capacity reasons). The output of ffmpeg -version is

  


  ffmpeg version N-113725-g37702e2066 Copyright (c) 2000-2024 the FFmpeg developers
built with gcc 11 (Ubuntu 11.4.0-1ubuntu1~22.04)
configuration: --enable-nonfree --enable-cuda-nvcc --enable-libnpp --extra-cflags=-I/usr/local/cuda/include --extra-ldflags=-L/usr/local/cuda/lib64 --disable-static --enable-shared --enable-libx265 --enable-gpl
libavutil      58. 39.100 / 58. 39.100
libavcodec     60. 39.101 / 60. 39.101
libavformat    60. 21.101 / 60. 21.101
libavdevice    60.  4.100 / 60.  4.100
libavfilter     9. 17.100 /  9. 17.100
libswscale      7.  6.100 /  7.  6.100
libswresample   4. 13.100 /  4. 13.100
libpostproc    57.  4.100 / 57.  4.100


  


  I saw online that one of the options of ffmpeg is -threads, but apparently it does not work, since using ffmpeg -i input.mp4 -c:v libx265 -c:a copy output.mp4 and ffmpeg -i input.mp4 -c:v libx265 -c:a copy -threads 2 output.mp4 seem to be exactly the same in terms of CPU usage as shown by htop. Is there something wrong in my usage of -threads ?

  


• WebVTT Audio Descriptions for Elephants Dream

  10 mars 2015, par silvia

  When I set out to improve accessibility on the Web and we started developing WebSRT – later to be renamed to WebVTT – I needed an example video to demonstrate captions / subtitles, audio descriptions, transcripts, navigation markers and sign language.

  I needed a freely available video with spoken text that either already had such data available or that I could create it for. Naturally I chose “Elephants Dream” by the Orange Open Movie Project , because it was created under the Creative Commons Attribution 2.5 license.

  As it turned out, the Blender Foundation had already created a collection of SRT files that would represent the English original as well as the translated languages. I was able to reuse them by merely adding a WEBVTT header.

  Then there was a need for a textual audio description. I read up on the plot online and finally wrote up a time-alignd audio description. I’m hereby making that file available under the Create Commons Attribution 4.0 license. I’ve added a few lines to the medadata headers so it doesn’t confuse players. Feel free to reuse at will – I know there are others out there that have a similar need to demonstrate accessibility features.