3 ms·

That is good. But this reminds me of the first time I installed 'ffmpeg' on Ubuntu only to have it not work with my well-tested parameters and also declare ffm

by craigyk 13y ago

That is good. But this reminds me of the first time I installed 'ffmpeg' on Ubuntu only to have it not work with my well-tested parameters and also declare ffmpeg 'deprecated'. Only after some head scratching did I figure out it had installed libav and an ffmpeg wrapper that tried but failed to be compatible with the real ffmpeg interface. I wasn't even aware of the split at the time, but this shenanigan definitely gave me a strong negative initial impression of libav.

astrange 13y ago
libav tries to ship a compatible wrapper called ffmpeg and a redone one called avconv. But ffmpeg itself just ships ffmpeg and puts incompatible changes in there, so you'd actually be worse off. What issues were you having, and with what file types?
- nathancahill 13y ago
  Incompatible? Do you mean with libav?
  - astrange 13y ago
    Backwards incompatible with previous versions of itself.
    - ux 13y ago
      Most of the old options have been mapped to the new interface (see opt_old2new() for instance). So most of the old commands are still compatible. Libav also has dropped ffmpeg forked copy since a long while, so FFmpeg is actually more retro compatible.
nathancahill 13y ago
For sure. The story of FFmpeg and libav is full of sneaky shenanigans like that.
- vezzy-fnord 13y ago
  A good entry on this, for those interested: http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html
  - teddyh 13y ago
    That is written by the FFmpeg side. Do you have a complementary view?
    - 0x09 13y ago
      The mpv developers have published an overview of the situation from their independent perspective which (FWIW) is very accurate from my vantage point as well: https://github.com/mpv-player/mpv/wiki/FFmpeg-versus-Libav https://github.com/mpv-player/mpv/wiki/FFmpeg-versus-Libav
- dfc 13y ago
  I thought that shenanigan was entirely the result of actions by a DD/UD and not upstream? I really miss ffprobe, I can never get avprobe to work on the first or second attempt.

by craigyk 13y ago

astrange 13y ago

libav tries to ship a compatible wrapper called ffmpeg and a redone one called avconv. But ffmpeg itself just ships ffmpeg and puts incompatible changes in there, so you'd actually be worse off. What issues were you having, and with what file types?

nathancahill 13y ago
Incompatible? Do you mean with libav?
- astrange 13y ago
  Backwards incompatible with previous versions of itself.
  - ux 13y ago
    Most of the old options have been mapped to the new interface (see opt_old2new() for instance). So most of the old commands are still compatible. Libav also has dropped ffmpeg forked copy since a long while, so FFmpeg is actually more retro compatible.

nathancahill 13y ago

For sure. The story of FFmpeg and libav is full of sneaky shenanigans like that.

vezzy-fnord 13y ago
A good entry on this, for those interested: http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html
- teddyh 13y ago
  That is written by the FFmpeg side. Do you have a complementary view?
  - 0x09 13y ago
    The mpv developers have published an overview of the situation from their independent perspective which (FWIW) is very accurate from my vantage point as well: https://github.com/mpv-player/mpv/wiki/FFmpeg-versus-Libav https://github.com/mpv-player/mpv/wiki/FFmpeg-versus-Libav
dfc 13y ago
I thought that shenanigan was entirely the result of actions by a DD/UD and not upstream? I really miss ffprobe, I can never get avprobe to work on the first or second attempt.