5 ms·

Interestingly, not even a single mention of ffmpeg.

doppel 11y ago
I was wondering the same thing. I find it highly unlikely that they are doing this processing with in-house created tools, although their limited set of input and output codecs shrinks this down from "practically impossible" to "improbable".
legulere 11y ago
I guess using ffmpeg commercially is hard because of patent issues.
- MichaelGG 11y ago
  I would be surprised if Netflix cannot pay the patent fees. The ffmpeg page mentions that commercial ffmpeg users end up paying the groups like MPEG LA. In general, I'm guessing patent owners don't like saying "no, we don't want to accept your money". https://www.ffmpeg.org/legal.html https://www.ffmpeg.org/legal.html
astrange 11y ago
It's possible their AVC encoder is not x264, and their VC1 encoder might be from Microsoft, in which case it would be a pretty modified ffmpeg. And some of the input formats might not be using it either. But you can be sure it's involved somewhere, since there's no other ProRes decoder that works on Linux!
- coalescence 11y ago
  FFmpeg supports Prores decode and encode? FFMBC for sure last time I checked
  - garblegarble 11y ago
    FFmpeg does, it has different decoder implementations with their own quirks (btw, moot AFAIK because I think they use EyeIO): # ffmpeg -codecs | grep prores ffmpeg version 2.8.1 Copyright (c) 2000-2015 the FFmpeg developers built with Apple LLVM version 7.0.0 (clang-700.1.76) configuration: --prefix=/opt/local --enable-swscale --enable-avfilter --enable-avresample --enable-libmp3lame --enable-libvorbis --enable-libopus --enable-libtheora --enable-libschroedinger --enable-libopenjpeg --enable-libmodplug --enable-libvpx --enable-libspeex --enable-libass --enable-libbluray --enable-lzma --enable-gnutls --enable-fontconfig --enable-libfreetype --enable-libfribidi --disable-indev=jack --disable-outdev=xv --mandir=/opt/local/share/man --enable-shared --enable-pthreads --cc=/usr/bin/clang --enable-vda --enable-videotoolbox --arch=x86_64 --enable-yasm --enable-gpl --enable-postproc --enable-libx264 --enable-libxvid --enable-version3 --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libsmbclient --enable-nonfree --enable-libfdk-aac --enable-libfaac libavutil 54. 31.100 / 54. 31.100 libavcodec 56. 60.100 / 56. 60.100 libavformat 56. 40.101 / 56. 40.101 libavdevice 56. 4.100 / 56. 4.100 libavfilter 5. 40.101 / 5. 40.101 libavresample 2. 1. 0 / 2. 1. 0 libswscale 3. 1.101 / 3. 1.101 libswresample 1. 2.101 / 1. 2.101 libpostproc 53. 3.100 / 53. 3.100 DEVIL. prores Apple ProRes (iCodec Pro) (decoders: prores prores_lgpl ) (encoders: prores prores_aw prores_ks )
- contingencies 11y ago
  there's no other ProRes decoder that works on Linux! Lightworks supports ProRes: http://www.lwks.com/index.php?option=com_content&view=article&id=100&Itemid=211 http://www.lwks.com/index.php?option=com_content&view=articl...
garblegarble 11y ago
It's my understanding they use a transcoder from EyeIO rather than FFmpeg
- mkagenius 11y ago
  I haven't yet watched your linked video fully but at 8:00 he mentions they used ffmpeg in 2013: https://youtu.be/tQrsz3BrfwU?t=480 https://youtu.be/tQrsz3BrfwU?t=480
  - garblegarble 11y ago
    Yeah, they talk in a couple of different videos about the different approaches they've used over the years

I was wondering the same thing. I find it highly unlikely that they are doing this processing with in-house created tools, although their limited set of input and output codecs shrinks this down from "practically impossible" to "improbable".

legulere 11y ago

I guess using ffmpeg commercially is hard because of patent issues.

MichaelGG 11y ago
I would be surprised if Netflix cannot pay the patent fees. The ffmpeg page mentions that commercial ffmpeg users end up paying the groups like MPEG LA. In general, I'm guessing patent owners don't like saying "no, we don't want to accept your money". https://www.ffmpeg.org/legal.html https://www.ffmpeg.org/legal.html

astrange 11y ago

It's possible their AVC encoder is not x264, and their VC1 encoder might be from Microsoft, in which case it would be a pretty modified ffmpeg. And some of the input formats might not be using it either. But you can be sure it's involved somewhere, since there's no other ProRes decoder that works on Linux!

coalescence 11y ago
FFmpeg supports Prores decode and encode? FFMBC for sure last time I checked
- garblegarble 11y ago
  FFmpeg does, it has different decoder implementations with their own quirks (btw, moot AFAIK because I think they use EyeIO): # ffmpeg -codecs | grep prores ffmpeg version 2.8.1 Copyright (c) 2000-2015 the FFmpeg developers built with Apple LLVM version 7.0.0 (clang-700.1.76) configuration: --prefix=/opt/local --enable-swscale --enable-avfilter --enable-avresample --enable-libmp3lame --enable-libvorbis --enable-libopus --enable-libtheora --enable-libschroedinger --enable-libopenjpeg --enable-libmodplug --enable-libvpx --enable-libspeex --enable-libass --enable-libbluray --enable-lzma --enable-gnutls --enable-fontconfig --enable-libfreetype --enable-libfribidi --disable-indev=jack --disable-outdev=xv --mandir=/opt/local/share/man --enable-shared --enable-pthreads --cc=/usr/bin/clang --enable-vda --enable-videotoolbox --arch=x86_64 --enable-yasm --enable-gpl --enable-postproc --enable-libx264 --enable-libxvid --enable-version3 --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libsmbclient --enable-nonfree --enable-libfdk-aac --enable-libfaac libavutil 54. 31.100 / 54. 31.100 libavcodec 56. 60.100 / 56. 60.100 libavformat 56. 40.101 / 56. 40.101 libavdevice 56. 4.100 / 56. 4.100 libavfilter 5. 40.101 / 5. 40.101 libavresample 2. 1. 0 / 2. 1. 0 libswscale 3. 1.101 / 3. 1.101 libswresample 1. 2.101 / 1. 2.101 libpostproc 53. 3.100 / 53. 3.100 DEVIL. prores Apple ProRes (iCodec Pro) (decoders: prores prores_lgpl ) (encoders: prores prores_aw prores_ks )
contingencies 11y ago
there's no other ProRes decoder that works on Linux! Lightworks supports ProRes: http://www.lwks.com/index.php?option=com_content&view=article&id=100&Itemid=211 http://www.lwks.com/index.php?option=com_content&view=articl...

garblegarble 11y ago

It's my understanding they use a transcoder from EyeIO rather than FFmpeg

mkagenius 11y ago
I haven't yet watched your linked video fully but at 8:00 he mentions they used ffmpeg in 2013: https://youtu.be/tQrsz3BrfwU?t=480 https://youtu.be/tQrsz3BrfwU?t=480
- garblegarble 11y ago
  Yeah, they talk in a couple of different videos about the different approaches they've used over the years