Source : https://github.com/jellyfin/jellyfin
Download :
https://www.myqnap.org/product/jellyfin/ (standard ffmpeg no HW transcoding unless apache8x ou Qmultimedia is installed)
ARM64 Apache84 version : https://www.myqnap.org/product/jellyfin-aarch64-apache84/
x86_64 Apache84 IDH version : https://www.myqnap.org/product/jellyfin-ihd-apache84/ (HW Transcoding enabled)
x86_64 Apache84 I965 version : https://www.myqnap.org/product/jellyfin-i965-apache83/ (HW Transcoding enabled)
x86_64 Apache83 IDH version : https://www.myqnap.org/product/jellyfin-ihd-apache84/ (HW Transcoding enabled)
x86_64 Apache83 I965 version : https://www.myqnap.org/product/jellyfin-i965-apache83/ (HW Transcoding enabled)
note :
listen on port 8096
autmoatilcally export H/W acceleration i965 driver
Jellyfin is Media System that puts you in control of managing and streaming your media.
It is an alternative to the proprietary Emby and Plex, to provide media from a dedicated server to end-user devices via multiple apps.
Jellyfin is descended from Emby's 3.5.2 release and ported to the .NET Core framework to enable full cross-platform support.
There are no strings attached, no premium licenses or features, and no hidden agendas: just a team who want to build something better and work together to achieve it.
[fr] Jellyfin est un système de média logiciel libre qui vous permet de contrôler la gestion et le streaming de vos médias.
Il s'agit d'une alternative aux systèmes propriétaires Emby et Plex, permettant de fournir des médias à partir d'un serveur dédié vers les appareils des utilisateurs finaux via plusieurs applications.
Jellyfin est issu de la version 3.5.2 d'Emby et est transposé sur le framework .NET Core pour permettre un support multiplateforme complet.
Il n'y a pas de conditions à remplir, pas de licences ou de fonctionnalités premium et pas d'agendas cachés : juste une équipe qui veut construire quelque chose de mieux et travailler ensemble pour l'atteindre.
Code:
the iHD driver supports the QSV (Quick Sync Video) and VA-API interfaces, which provide better performance and more fine-tuning options on supported platforms.
The i965 driver only supports the VA-API interface, which is required for compatibility on pre-Broadwell platforms.
The iHD driver also supports HDR/DV to SDR tone-mapping, which is a feature that the i965 driver lacks.
The iHD driver supports most Intel GPUs that have Quick Sync Video (QSV) capability, which is a hardware feature that enables fast and efficient video encoding and decoding.
The QSV feature is available on most Intel processors released after 2011, such as Sandy Bridge, Ivy Bridge, Haswell, Broadwell, Skylake, Kaby Lake, Coffee Lake, Whiskey Lake, Comet Lake, Ice Lake, Tiger Lake, and others.
You can check the QSV support for a specific processor model on the Intel ark website.
The i965 driver, on the other hand, is mainly used for older Intel GPUs that do not have QSV capability, such as pre-Broadwell platforms.
These include Nehalem, Westmere, Sandy Bridge, Ivy Bridge, and Haswell. The i965 driver may also work for some newer platforms, but it may not offer the same performance and features as the iHD driver.
Therefore, if you want to use hardware acceleration with the iHD and i965 drivers, you need to choose a processor that has an Intel GPU that supports either of these drivers.
The best option would be to choose a processor that has QSV capability and use the iHD driver, as this will give you the best performance and features.
However, if you have an older platform that does not have QSV capability, you can still use the i965 driver for hardware acceleration, but you may have to compromise on some aspects.
Dernière édition:
