user6685: Two years ago I've used ffmbc to encode videos to prores, but nowadays ffmpeg also supports prores and avchd. What is the difference between ffmpeg and ffmbc now?

user9147: One difference at least :
-target xdcamhd422

is supported by FFmbc but not by FFmpeg.
Very useful in a professional broadcast environment.
the -target option allows to specify several parameters at once. The -target option value must be one supported by FFm**. In the case of the xdcamhd422 value, it specifies the video codec to be used (mpeg2video), the frame size (1920 x 1080), and other parameters in order to have an output file conform to the XDCam HD standard.

user1760: Usage differences
Note: ffmbc/ffmpeg will refer to the tools, while FFmbc/FFmpeg will refer to the projects themselves and/or each whole collection of tools and libraries.

There are syntax differences including:

ffmbc uses the old, confusing -newaudio option while ffmpeg can just use -map.
ffmbc does not support -codec or -c, so instead all stream types must be explicitly defined if you do not want to rely on the defaults. For example -vcodec copy -acodec copy -scodec copy vs just -c copy.
Probably lots more that I didn't think of. Feel free to edit answer and add more.

ffmbc will automatically relocate some data after encoding to MOV, MP4, etc while ffmpeg requires the -movflags +faststart option.
ffmbc does not support -filter_complex so filtering is different. For example, using the overlay video filter:

ffmbc: -i video.mp4 -vf "movie='overlay.png' [movie]; [in][movie] overlay [out]"
ffmpeg: -i video.mp4 -i image.png -filter_complex "[0:v][1:v]overlay"

FFmbc seems to support more broadcast formats.
FFmpeg has more features and filters.
FFmbc dropped ffplay and ffserver.

Development differences

FFmbc is GPL, and FFmpeg is mostly LGPL which makes porting features from FFmbc to FFmpeg more difficult.
FFmbc is basically the project of a former FFmpeg developer with a few contributions from others. FFmpeg has many developers and contributors.
FFmpeg often merges things form Libav, while FFmbc ignores Libav. Libav cherry-picks occasionally from FFmpeg, but ignores most stuff from FFmpeg (Libav is often joked to have "NIH syndrome").


6685: <p>Two years ago I've used ffmbc to encode videos to prores, but nowadays ffmpeg also supports <a href="http://en.wikipedia.org/wiki/Apple_ProRes">prores</a> and <a href="http://de.wikipedia.org/wiki/Advanced_Video_Codec_High_Definition">avchd</a>. What is the difference between <a href="http://www.ffmpeg.org/">ffmpeg</a> and <a href="https://code.google.com/p/ffmbc/">ffmbc</a> now?</p>
 9147: <p>One difference at least :</p>

<pre><code>-target xdcamhd422
</code></pre>

<p>is supported by FFmbc but not by FFmpeg.</p>

<p>Very useful in a professional broadcast environment.</p>

<p>the <code>-target</code> option allows to specify several parameters at once. The <code>-target</code> option value must be one supported by FFm**. In the case of the <code>xdcamhd422</code> value, it specifies the video codec to be used (<code>mpeg2video</code>), the frame size (1920 x 1080), and other parameters in order to have an output file conform to the XDCam HD standard.</p>
 1760: <h1>Usage differences</h1>

<p><sub>Note: <code>ffmbc</code>/<code>ffmpeg</code> will refer to the tools, while FFmbc/FFmpeg will refer to the projects themselves and/or each whole collection of tools and libraries.</sub></p>

<ul>
<li><p>There are syntax differences including:</p>

<ul>
<li><p><code>ffmbc</code> uses the old, confusing <code>-newaudio</code> option while <code>ffmpeg</code> can just use <code>-map</code>.</p></li>
<li><p><code>ffmbc</code> does not support <code>-codec</code> or <code>-c</code>, so instead all stream types must be explicitly defined if you do not want to rely on the defaults. For example <code>-vcodec copy -acodec copy -scodec copy</code> vs just <code>-c copy</code>.</p></li>
<li><p>Probably lots more that I didn't think of. Feel free to edit answer and add more.</p></li>
</ul></li>
<li><p><code>ffmbc</code> will automatically relocate some data after encoding to MOV, MP4, etc while <code>ffmpeg</code> requires the <code>-movflags +faststart</code> option.</p></li>
<li><p><code>ffmbc</code> does not support <code>-filter_complex</code> so filtering is different. For example, using the overlay video filter:</p>

<ul>
<li><code>ffmbc</code>: <code>-i video.mp4 -vf "movie='overlay.png' [movie]; [in][movie] overlay [out]"</code></li>
<li><code>ffmpeg</code>: <code>-i video.mp4 -i image.png -filter_complex "[0:v][1:v]overlay"</code></li>
</ul></li>
<li><p>FFmbc seems to support more broadcast formats.</p></li>
<li><p>FFmpeg has more features and filters.</p></li>
<li><p>FFmbc dropped <code>ffplay</code> and <code>ffserver</code>.</p></li>
</ul>

<h1>Development differences</h1>

<ul>
<li><p>FFmbc is GPL, and FFmpeg is mostly LGPL which makes porting features from FFmbc to FFmpeg more difficult.</p></li>
<li><p>FFmbc is basically the project of a former FFmpeg developer with a few contributions from others. FFmpeg has many developers and contributors.</p></li>
<li><p>FFmpeg often merges things form Libav, while FFmbc ignores Libav. Libav cherry-picks occasionally from FFmpeg, but ignores most stuff from FFmpeg (Libav is often joked to have "<a href="http://en.wikipedia.org/wiki/Not_invented_here" rel="nofollow">NIH syndrome</a>").</p></li>
</ul>
