Recherche avancée

Sur d’autres sites (4021)

• Can FFmpeg encode multiple files at once ?

  28 décembre 2016, par ivan

  I’m working on a shell script to encode the audio files in a given directory and output .flac files to another directory. My proof of concept loops through each file one by one and runs it through ffmpeg. I suspect there’s a way to pass the whole list of input files to ffmpeg in a single command, but haven’t been able to figure it out.

  My current version looks like this :

  #!/bin/sh
  
  
  
  encode_album() {
  
      local artist=$1; shift
  
      local album=$1; shift
  
      local in_dir="${HOME}/Music/raw-imports/${artist}/${album}"
  
      local out_dir="${HOME}/Music/library/${artist}/${album}"
  
  
  
      mkdir -p "${out_dir}"
  
  
  
      find "${in_dir}" -type f -name *.aiff | while IFS= read -r in_file; do
  
          local track_name=$(basename "${in_file}" .aiff)
  
          local out_file="${out_dir}/${track_name}.flac"
  
  
  
          encode_track "${in_file}" "${out_file}"
  
      done
  
  }
  
  
  
  encode_track() {
  
      local in_file=$1; shift
  
      local out_file=$1; shift
  
  
  
      null ffmpeg -i "${in_file}" -codec:a flac "${out_file}"
  
  }
  
  
  
  encode_album "Rolf Lislevand" "La Mascarade"

  This works, but do I need to feed these files into ffmpeg one by one, or is it capable of accepting a batch of files and processing them ?

• avutil/buffer : Never poison returned buffers

  4 octobre 2021, par Andreas Rheinhardt

  avutil/buffer : Never poison returned buffers
  Poisoning returned buffers is based around the implicit assumption
  
  that the contents of said buffers are transient. Yet this is not true
  
  for the buffer pools used by the various hardware contexts which store
  
  important state in there that needs to be preserved.
  
  Furthermore, the current code is also based on the assumption
  
  that the complete buffer pointed to by AVBuffer->data coincides with
  
  AVBufferRef->data ; yet an implementation might store some data of its
  
  own before the actual user-visible data (accessible via AVBufferRef)
  
  which would be broken by the current code.
  (This is of course yet more proof that the AVBuffer API is not the right
  
  tool for the hardware contexts.)
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
  

  • [DH] libavutil/buffer.c

• Piwik 3 Release Candidate

  14 décembre 2016, par Piwik Core Team — Development

  The release candidate for Piwik 3 is now available.

  RC means we think we’re done, but it’s possible we’ve missed something. We hope to ship Piwik 3 on Sunday, December 18th (updated). If you haven’t tested Piwik 3 yet, now is the time ! To test Piwik 3, you can use the beta release channel or you can download the release candidate here (zip).

  Piwik 3 is a jam-packed release, with a number of features focused on security, performance, and more advanced analytics capabilities. Highlights include new UI design, responsive experience on mobile, better email reports, secure password storage, better tracking of downloads and outlinks, and more.

  Not sure where to start with testing ? Try setting up a new installation and taking notes on what you enjoyed and what got you stuck. For more details about what’s new in version 3.0, check out the beta 1, beta 2, beta 3, beta 4 changelogs as well as these blog posts : Piwik 3 overview, and Important notes and API breaking changes in Piwik 3.

  Think you’ve found a bug ? Please post to our Issues tracker. If any known issues come up, you’ll be able to search and find them there.

  Developers, please test your plugins and themes against Piwik 3 and update your plugin.json to require Piwik 3. An in-depth field guide to developer-focused changes and plugin migration is published on the Developer website.

  Do you speak a language other than English ? Help us translate Piwik into more than 50 languages !

  Happy testing !