this post was submitted on 13 Dec 2023
124 points (99.2% liked)

Jellyfin: The Free Software Media System

5721 readers
13 users here now

Current stable release: 10.10.0

Community Standards

Website

Forum

GitHub

Documentation

Feature Requests

Matrix (General Information & Help)

Matrix (Announcements)

Matrix (General Development)

Matrix (Off-Topic) - Come get to know the team and blow off steam!

Matrix Space - List of all the available rooms on Matrix.

Discord - Bridged to our Matrix rooms

founded 4 years ago
MODERATORS
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] scholar@lemmy.world 37 points 11 months ago (2 children)

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.

[–] Lmaydev@programming.dev 6 points 11 months ago

It's literally for the CLI yeah.

[–] vynlwombat@lemmy.world 2 points 11 months ago (2 children)

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 7 points 11 months 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 1 points 10 months ago* (last edited 10 months 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.