This should eventually make it’s way into jellyfin. Eager to see the performance improvements.

  • scholar@lemmy.world
    link
    fedilink
    English
    arrow-up
    37
    ·
    1 year ago

    As far as I’m aware this is only for the cli version of ffmpeg and won’t affect the threading of codecs many of which were already multithreaded.

    • vynlwombat@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      I recently tried figuring out how to build ffmpeg with Nvidia codecs. I’m very new to ffmpeg and codec terminology. How is multithreading for the CLI different than the codecs?

      • notfromhere@lemmy.one
        link
        fedilink
        English
        arrow-up
        7
        ·
        1 year ago

        My understanding is some parts have to be done sequentially even though the parts themselves are multithreaded, now the different parts can all be done in parallel.

      • Lmaydev@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        1 year ago

        Change the main loop and every component (demuxers, decoders, filters, encoders, muxers) to use the previously added transcode scheduler.

        The components are what they have parallelised.