All the giant companies used ffmpeg

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

Nutrient - The #1 PDF SDK Library
Bad PDFs = bad UX. Slow load times, broken annotations, clunky UX frustrates users. Nutrient’s PDF SDKs gives seamless document experiences, fast rendering, annotations, real-time collaboration, 100+ features. Used by 10K+ devs, serving ~half a billion users worldwide. Explore the SDK for free.
nutrient.io
featured
CodeRabbit: AI Code Reviews for Developers
Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
coderabbit.ai
featured
  1. ffmpeg-libav-tutorial

    FFmpeg libav tutorial - learn how media works from basic to transmuxing, transcoding and more. Translations: 🇺🇸 🇨🇳 🇰🇷 🇪🇸 🇻🇳 🇧🇷

    I think you're supposed to read the header files? I have no idea how people write ffmpeg stuff. The only good tutorial I've seen is: https://github.com/leandromoreira/ffmpeg-libav-tutorial

  2. Nutrient

    Nutrient - The #1 PDF SDK Library. Bad PDFs = bad UX. Slow load times, broken annotations, clunky UX frustrates users. Nutrient’s PDF SDKs gives seamless document experiences, fast rendering, annotations, real-time collaboration, 100+ features. Used by 10K+ devs, serving ~half a billion users worldwide. Explore the SDK for free.

    Nutrient logo
  3. ffmpeg-tutorial

    Discontinued A set of tutorials that demonstrates how to write a video player based on FFmpeg

  4. FFmpeg

    Mirror of https://git.ffmpeg.org/ffmpeg.git

    >setting up ffmpeg to work with buffers instead of files

    I'd take a look at https://github.com/FFmpeg/FFmpeg/blob/master/tools/target_de...

    In io_seek I'd also clamp pos at the end to be between 0 and the filesize. That might be needed for some files. It doesn't hurt though.

    >I'm thinking that for long-term maintainability it might be better to use the CLI anyways

    It's definitely easier that way. You don't have to deal with gotchas like having to set some random flags or needing to specify a filename. It's just so easy to write code that fails on 1% of files which ffmpeg can actually decode.

  5. oss-fuzz

    OSS-Fuzz - continuous fuzzing for open source software.

    ffmpeg/libav is being fuzzed with reasonable success. See for example https://github.com/google/oss-fuzz/tree/master/projects/ffmp... and https://security.googleblog.com/2014/01/ffmpeg-and-thousand-....

    They found issues in code I wrote...

    (I work for Google but do not speak for it)

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • Show HN: LLMpeg

    9 projects | news.ycombinator.com | 14 Jan 2025
  • Show HN: I completed shipping my desktop app

    2 projects | news.ycombinator.com | 3 Jan 2025
  • Ten years after the last release, Aegisub 3.4.0 released

    2 projects | news.ycombinator.com | 21 Dec 2024
  • LINUX ÜZERINDE OPERA BROWSER VIDEO OYNATMAMA SORUNU

    1 project | dev.to | 26 Nov 2024
  • Hall of shame: Fake LosslessCut clones

    1 project | news.ycombinator.com | 18 Nov 2024