

I couldn't guess how many other people in features or TV are using it. But in answer to the original question - I do use ffmpeg a ton on both film and TV work, and think it's a great tool that helps me get through many of my regular tasks quickly and well. I don't use ffmpeg for any sort of final or critical output, and I only use it in a few limited ways that I've extensively tested. For example, clips needed for temp can be pulled from BDR or DVDR video discs, ingested into an mkv file, and then from there transcoded with ffmpeg to editorial-ready DnxHD or Prores. Transcoding files for editorial whose original video or audio are in codecs or formats not supported by AME or Compressor.

When I figure out how to do SMPTE timecode and feet+frames burn-ins with ffmpeg, my use of the application will expand further. It's convenient, faster than AME, and more stable than a Compressor cluster. I've written up shell scripts that accept property-of and recipient strings as command line input, along with target bitrate, and then generate the desired files with a watermark made from those inputs. Transcoding files to be uploaded for producers to view on digital dailies systems (Dax, PIX, etc). I work as an assistant editor on feature films, and use ffmpeg all the time, primarily for two purposes:
