<p>I work as an assistant editor on feature films, and use ffmpeg all the time, primarily for two purposes:</p>

<ul>
<li><p>Transcoding files to be uploaded for producers to view on digital dailies systems (Dax, PIX, etc). 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. It's convenient, faster than AME, and more stable than a Compressor cluster. When I figure out how to do SMPTE timecode and feet+frames burn-ins with ffmpeg, my use of the application will expand further. </p></li>
<li><p>Transcoding files for editorial whose original video or audio are in codecs or formats not supported by AME or Compressor. 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.</p></li>
</ul>

<p>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. 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 couldn't guess how many other people in features or TV are using it. I frequently recommend ffmpeg to other AE's, but most folk have a command-line aversion.</p>

<p>ffmpeg's use in professional film and broadcast settings is probably also limited by the learning curve of not just the application's own syntax(es) but also the exposed complexity of video formats. Sometimes in ffmpeg a user has to know a ton about source and target codec in order to get things done. Use Compressor or AME to transcode from one codec to another and you'll never have to deal with perusing a long list of different YUV pixel formats, or having to make sure that your target file's height is divisible by 2 to avoid an x264 error. Those of us who enjoy learning arcana and carving our way to solutions are probably silently using ffmpeg at work. </p>

CC BY-SA 4.0
2020-12-17T20:32:01.613Z
*I don't use ffmpeg for any sort of final or critical output.* Can I ask why?
Hashim Aziz
CC BY-SA 3.0
2015-03-17T23:33:04.603Z
2015-03-17T23:33:04.603Z
Zach Fine
<p>The main reason is support, usability and control.  First, lets clarify that FFMPEG is an encoder, QuickTime Pro is a video utility that happens to include multiple encoders and Final Cut Pro is a non-linear editor and has nothing to do with encoders other than the fact it can output to an encoder (generally QuickTime I believe).</p>

<p>For big budget commercial projects, the emphasis is going to be on having the highest possible quality encoding which often will involve manual review of the content and tweaking the way things are encoded to minimize artifacts and maximize the quality.  Commercial encoders or even proprietary ones used internally by encoding houses have far more control, support and development than ffmpeg.  It's great for a free tool, but it isn't a high end commercial product.</p>

<p>For smaller commercial projects, you may find some users, but most often people use the encoders that come with their NLEs at that level (such as QuickTime Pro or Adobe Media Encoder).  The main reason at that level is convenience since they are tied directly in to the NLEs and are easy to configure and behave well with good quality results.</p>

<p>I can't guarantee that there aren't any production chains that use FFMPEG or a modified form of it, but in general, it is worth simply pointing out that not all encoders are created equally and while ffmpeg does very, very well for being free, it isn't the best option in all cases all the time, even if for business reasons rather than technical ones.</p>

CC BY-SA 3.0
2013-12-03T18:18:17.763Z
It is debatable that commercial encoders have more active development that ffmpeg. Just look at the [large number of commits to FFmpeg](http://git.videolan.org/?p=ffmpeg.git;a=shortlog) per week. Of course the commercial stuff will not disclose their information. As for quality I can get what I want with FFmpeg, but AME is often more annoying than useful. [How to encode with ffmpeg from Adobe Premiere Pro](https://trac.ffmpeg.org/wiki/FFmpegPremierePro) may interest some users.
llogan
CC BY-SA 3.0
2013-12-03T18:33:32.343Z
There is more to amount of development than the number of commits.  There is the level of responsiveness to industry concerns that come up.  If a production studio has a problem with a commercial encoder, they can get direct professional support.  They can't do this without having their own in house developer for FFmpeg.  That said, nice link about the using ffmpeg with Adobe Premiere Pro.  I'll probably give that a shot as I'm always a fan of having more options available even if I generally find AME to be useful.
AJ Henderson
CC BY-SA 3.0
2013-12-03T18:38:07.420Z
FFmpeg has good, free user support and interested [developers can also be hired](http://ffmpeg.org/consulting.html) for employment or direct consulting support.
llogan
CC BY-SA 3.0
2013-12-03T18:43:18.140Z
@LordNeckbeard - yes, but a production company isn't a software company and doesn't want to have to deal with developers.  They want an organization to be the knowledge expert on it for them so they don't have to worry about it.  This is the same reason that commercial software continues to do well in so many other areas where there is similar open source products available.  I'm not saying you couldn't necessarily accomplish the same thing with FFmpeg, but by the time you do, it's likely going to cost more than commercial options.  That's just a general rule of thumb for FOSS.  It's time vs $
AJ Henderson
CC BY-SA 3.0
2014-01-02T02:28:14.180Z
I'd like to add that our team uses FFMPEG pretty regularly, but the learning curve was not pretty. I think this holds back a lot of other video pros I talk to. I've heard countless stories of people who tried FFMPEG once or twice, got an unexpected result, and returned to the encoder they're more comfortable with. I can't really blame them, time is money. We use FFMPEG because we make backend video frameworks, and easily being able to access FFMPEG from Python and command line are invaluable to us.
elburzs
CC BY-SA 3.0
2015-03-21T04:54:36.593Z
The codec quality thing is definitely an issue.  I'm a sound designer and I generally have to turn over review quicktimes as MP4s with AAC, and the stock ffmpeg AAC encoder is *atrocious*, you gotta go Fraunhofer. It just gives me the heebeejeebees about using FFMpeg for any video encoding apart from just draft stuff.
iluvcapra
CC BY-SA 4.0
2020-12-17T20:35:22.553Z
@iluvcapra The stock AAC encoder is no longer experimental and is now claimed to be better than FDK-AAC for bitrates over 96kb, though I don't personally know how true that is.
Hashim Aziz
CC BY-SA 4.0
2020-12-18T18:23:19.110Z
@Prometheus It's good to know, I use ffmpeg pretty routinely now though I only export audio as LPCM.
iluvcapra
CC BY-SA 3.0
2013-12-03T17:55:21.060Z
2013-12-03T18:54:15.577Z
2013-12-03T18:54:15.577Z
AJ Henderson
<p>I use it in <em>my</em> professional production chain all the time. Last week I was using it to batch through dozens of videos that needed subtitles burnt-in. It would have taken me weeks of tedious labour with Final Cut, it took me a couple of minutes burning the srts in with ffmpeg, and I was able to automatically rename the files and compress them for the various playback devices at the same time, and keep editing in the background.</p>

<p>I'd say unfamiliarity with the command line is the major reason most people don't use it. Typy-typy is too scary, they need clicky-clicky. Though there are definitely some areas - archival preservation for one, where it is one of the main tools of choice. In any situation where you need to automate video manipulation or conversion there is really nothing that beats it.</p>

CC BY-SA 3.0
2014-01-19T13:28:57.977Z
2016-12-05T03:22:49.330Z
2016-12-05T03:22:49.330Z
stib
<p>FFmpeg is probably being used more than you believe. I think the BBC uses it for some workflows, there is evidence that Laika and Weta may use it, and there is a fork called FFmbc which is targeted for professional broadcast usage.</p>

<p>YouTube probably uses FFmpeg to decode as shown by some unique decoding issues (but this was several years ago that I read about this and I'm not sure of the current status).</p>

<p>Also see the <a href="http://ffmpeg.org/projects.html">FFmpeg Projects</a> page for a small list of who uses FFmpeg in their projects.</p>

CC BY-SA 3.0
2013-12-04T14:35:41.893Z
Could you please add some reference link about the usage of ffmpeg at BBC or Laika, or somewhere else?
tomsv
CC BY-SA 3.0
2013-12-04T18:02:14.887Z
@dontomaso No, unfortunately. These are just inferences from observing who is asking questions in the [ffmpeg-user](http://ffmpeg.org/contact.html) mailing list and some discussions in various IRC channels. Perhaps you can ask on ffmpeg-user who is actually using ffmpeg and get answers straight from the source.
llogan
CC BY-SA 3.0
2014-03-14T15:31:25.917Z
Some of the [FFmbc](https://code.google.com/p/ffmbc/) development was funded by the BBC. They are credited inside the source code.
UmNyobe
CC BY-SA 3.0
2013-12-03T18:11:29.223Z
2013-12-31T23:28:40.807Z
2013-12-31T23:28:40.807Z
llogan
<p>Is the assumption in the title true?</p>

<p>What is preventing the use of ffmpeg when producing a movie or broadcast quality material?</p>

<p>Are there any prominent or well known users of ffmpeg?</p>

<p>What is used instead of ffmpeg? Quicktime pro? Final Cut Pro/Adobe Premiere/Avid media composer?</p>

<p>Edit:</p>

<p>One interesting indication of ffmpeg usage could be job offer listings from major media firms where they are looking for ffmpeg skills.</p>

CC BY-SA 3.0
2014-01-03T13:25:59.023Z
If you say "ffmpeg skills" do you mean "I am able to read documentation and use (standard) tools" or do you mean "I know the sourcecode and can add any feature you want". The former is nothing special, the later is highly sought.
Andreas
<ffmpeg><final-cut-pro><broadcasting><quicktime>
Why isn't ffmpeg used in movie production or broadcasting tool chains?
tomsv
# Why isn't ffmpeg used in movie production or broadcasting tool chains?

(Asked by: username_0 on 2013-12-03)

Is the assumption in the title true?

What is preventing the use of ffmpeg when producing a movie or broadcast quality material?

Are there any prominent or well known users of ffmpeg?

What is used instead of ffmpeg? Quicktime pro? Final Cut Pro/Adobe Premiere/Avid media composer?

Edit:

One interesting indication of ffmpeg usage could be job offer listings from major media firms where they are looking for ffmpeg skills.

**Tags:** ffmpeg, final-cut-pro, broadcasting, quicktime

> **Comments:**
> **username_1**: If you say "ffmpeg skills" do you mean "I am able to read documentation and use (standard) tools" or do you mean "I know the sourcecode and can add any feature you want". The former is nothing special, the later is highly sought.  

---

## 4 answers

### Answer by username_5 on 2013-12-03. Score: 11 | Accepted answer

FFmpeg is probably being used more than you believe. I think the BBC uses it for some workflows, there is evidence that Laika and Weta may use it, and there is a fork called FFmbc which is targeted for professional broadcast usage.

YouTube probably uses FFmpeg to decode as shown by some unique decoding issues (but this was several years ago that I read about this and I'm not sure of the current status).

Also see the [FFmpeg Projects](http://ffmpeg.org/projects.html) page for a small list of who uses FFmpeg in their projects.

> **Comments:**
> **username_0**: Could you please add some reference link about the usage of ffmpeg at BBC or Laika, or somewhere else?  
> **username_5**: @dontomaso No, unfortunately. These are just inferences from observing who is asking questions in the [ffmpeg-user](http://ffmpeg.org/contact.html) mailing list and some discussions in various IRC channels. Perhaps you can ask on ffmpeg-user who is actually using ffmpeg and get answers straight from the source.  
> **username_9**: Some of the [FFmbc](https://code.google.com/p/ffmbc/) development was funded by the BBC. They are credited inside the source code.  

---

### Answer by username_2 on 2015-03-17. Score: 12

I work as an assistant editor on feature films, and use ffmpeg all the time, primarily for two purposes:

* Transcoding files to be uploaded for producers to view on digital dailies systems (Dax, PIX, etc). 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. It's convenient, faster than AME, and more stable than a Compressor cluster. When I figure out how to do SMPTE timecode and feet+frames burn-ins with ffmpeg, my use of the application will expand further.
* Transcoding files for editorial whose original video or audio are in codecs or formats not supported by AME or Compressor. 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.

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. 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 couldn't guess how many other people in features or TV are using it. I frequently recommend ffmpeg to other AE's, but most folk have a command-line aversion.

ffmpeg's use in professional film and broadcast settings is probably also limited by the learning curve of not just the application's own syntax(es) but also the exposed complexity of video formats. Sometimes in ffmpeg a user has to know a ton about source and target codec in order to get things done. Use Compressor or AME to transcode from one codec to another and you'll never have to deal with perusing a long list of different YUV pixel formats, or having to make sure that your target file's height is divisible by 2 to avoid an x264 error. Those of us who enjoy learning arcana and carving our way to solutions are probably silently using ffmpeg at work.

> **Comments:**
> **username_3**: *I don't use ffmpeg for any sort of final or critical output.* Can I ask why?  

---

### Answer by username_4 on 2013-12-03. Score: 5

The main reason is support, usability and control. First, lets clarify that FFMPEG is an encoder, QuickTime Pro is a video utility that happens to include multiple encoders and Final Cut Pro is a non-linear editor and has nothing to do with encoders other than the fact it can output to an encoder (generally QuickTime I believe).

For big budget commercial projects, the emphasis is going to be on having the highest possible quality encoding which often will involve manual review of the content and tweaking the way things are encoded to minimize artifacts and maximize the quality. Commercial encoders or even proprietary ones used internally by encoding houses have far more control, support and development than ffmpeg. It's great for a free tool, but it isn't a high end commercial product.

For smaller commercial projects, you may find some users, but most often people use the encoders that come with their NLEs at that level (such as QuickTime Pro or Adobe Media Encoder). The main reason at that level is convenience since they are tied directly in to the NLEs and are easy to configure and behave well with good quality results.

I can't guarantee that there aren't any production chains that use FFMPEG or a modified form of it, but in general, it is worth simply pointing out that not all encoders are created equally and while ffmpeg does very, very well for being free, it isn't the best option in all cases all the time, even if for business reasons rather than technical ones.

> **Comments:**
> **username_5**: It is debatable that commercial encoders have more active development that ffmpeg. Just look at the [large number of commits to FFmpeg](http://git.videolan.org/?p=ffmpeg.git;a=shortlog) per week. Of course the commercial stuff will not disclose their information. As for quality I can get what I want with FFmpeg, but AME is often more annoying than useful. [How to encode with ffmpeg from Adobe Premiere Pro](https://trac.ffmpeg.org/wiki/FFmpegPremierePro) may interest some users.  
> **username_4**: There is more to amount of development than the number of commits.  There is the level of responsiveness to industry concerns that come up.  If a production studio has a problem with a commercial encoder, they can get direct professional support.  They can't do this without having their own in house developer for FFmpeg.  That said, nice link about the using ffmpeg with Adobe Premiere Pro.  I'll probably give that a shot as I'm always a fan of having more options available even if I generally find AME to be useful.  
> **username_5**: FFmpeg has good, free user support and interested [developers can also be hired](http://ffmpeg.org/consulting.html) for employment or direct consulting support.  
> **username_4**: @LordNeckbeard - yes, but a production company isn't a software company and doesn't want to have to deal with developers.  They want an organization to be the knowledge expert on it for them so they don't have to worry about it.  This is the same reason that commercial software continues to do well in so many other areas where there is similar open source products available.  I'm not saying you couldn't necessarily accomplish the same thing with FFmpeg, but by the time you do, it's likely going to cost more than commercial options.  That's just a general rule of thumb for FOSS.  It's time vs $  
> **username_6**: I'd like to add that our team uses FFMPEG pretty regularly, but the learning curve was not pretty. I think this holds back a lot of other video pros I talk to. I've heard countless stories of people who tried FFMPEG once or twice, got an unexpected result, and returned to the encoder they're more comfortable with. I can't really blame them, time is money. We use FFMPEG because we make backend video frameworks, and easily being able to access FFMPEG from Python and command line are invaluable to us.  
> **username_7**: The codec quality thing is definitely an issue.  I'm a sound designer and I generally have to turn over review quicktimes as MP4s with AAC, and the stock ffmpeg AAC encoder is *atrocious*, you gotta go Fraunhofer. It just gives me the heebeejeebees about using FFMpeg for any video encoding apart from just draft stuff.  
> **username_3**: @username_7 The stock AAC encoder is no longer experimental and is now claimed to be better than FDK-AAC for bitrates over 96kb, though I don't personally know how true that is.  
> **username_7**: @Prometheus It's good to know, I use ffmpeg pretty routinely now though I only export audio as LPCM.  

---

### Answer by username_8 on 2014-01-19. Score: 5

I use it in *my* professional production chain all the time. Last week I was using it to batch through dozens of videos that needed subtitles burnt-in. It would have taken me weeks of tedious labour with Final Cut, it took me a couple of minutes burning the srts in with ffmpeg, and I was able to automatically rename the files and compress them for the various playback devices at the same time, and keep editing in the background.

I'd say unfamiliarity with the command line is the major reason most people don't use it. Typy-typy is too scary, they need clicky-clicky. Though there are definitely some areas - archival preservation for one, where it is one of the main tools of choice. In any situation where you need to automate video manipulation or conversion there is really nothing that beats it.


---

