Extracting a subtitle stream is a disk I/O bottlenecked operation as
ffmpeg has to read through the whole file, but usually there is nothing
CPU intensive to do.
If a file has multiple subtitle streams, and we want to extract more
of them, extracting them one-by-one results in reading the whole file
again and again.
However ffmpeg can extract multiple streams at once.
We can optimize this by extracting the subtitle streams all at once
when only one of them gets queried, then we will have all of them
cached for later use.
It is useful for people switching subtitles during playback.
It is even more useful for people who extract all the subtitle streams
in advance, for example with the "Subtitle Extract" plugin.
In this case we reduce the extraction time significantly based on the
number of subtitle streams in the files, which can be 5-10 in many
cases.
Signed-off-by: Attila Szakacs <szakacs.attila96@gmail.com>
* Fix fedora
* Fix RID Linux
* Fix package and image versions
* Fix buildling and optimize docker images
```
* Removed find obj
* Changed curl command and added gpg
* Added to Contributors
* Removed apt-transport-https package
* Removed RASPI
* Update Intel drivers version
* Update Dockerfile for CentOS, Fedora, and portable deployments
- Changed Jammy docker image to Built-in Jammy Microsoft .NET SDK image
- Switched from using "Yum" to "Dnf" for CentOS and Fedora
- Added "dnf clean all" and "rm -rf /var/cache/dnf" to the end of CentOS and Fedora Dockerfiles
- Added "apt-get clean", "apt-get autoremove", "rm -rf /var/lib/apt/lists/*" to the end of the Debian/Ubuntu Dockerfiles
- Added ${DOTNET_VERSION} in every Dockerfile except CentOS/Fedora
- Removed previous warning comment for dotnet publish build in parallel
- Arranged package installation
* Re-arranged Dockerfile package installation
* Re-align
* Remove curl
* Remove curl