Après une année de développement et de tests intensifs, Jellyfin 10.11.0 marque l’une des évolutions les plus importantes du projet open source. Cette nouvelle version met l’accent sur la performance, la fiabilité et la préparation du futur, avec une refonte du système de gestion des métadonnées, de nouveaux outils d’administration et plusieurs améliorations côté utilisateur. Regardons de plus près cette nouvelle version…

Jellyfin 10.11.0 : le changement, c’est maintenant

Visuellement, Jellyfin 10.11.0 n’apporte que peu de modifications. Les véritables avancées se situent à l’intérieur du moteur : la base de données de la bibliothèque a été entièrement migrée vers EF Core.

Concrètement, Jellyfin abandonne les requêtes SQLite dispersées au profit d’une gestion centralisée des données. Résultat :

• des requêtes plus rapides,
• des migrations plus sûres,
• et une base bien plus facile à faire évoluer.

Cette refonte ouvre également la voie à la prise en charge future d’autres moteurs de base de données, comme PostgreSQL, pour plus de flexibilité et de robustesse.

Maintenance simplifiée

La migration des bibliothèques s’accompagne d’un processus de déduplication et de nettoyage des données (suppression d’entrées orphelines ou doublons). Selon la taille et l’ancienneté de la base, cette étape peut durer de quelques minutes à plusieurs heures.
Avant toute mise à jour, il est impératif de :

• sauvegarder manuellement les dossiers de données et de configuration,
• être déjà sur la version 10.10.7,
• et ne jamais interrompre la migration en cours.

Autre nouveauté appréciable : la fonction de sauvegarde et restauration intégrée. Elle permet de créer des instantanés (snapshots) de la base de métadonnées et de les restaurer facilement, un vrai plus pour la maintenance et la sécurité des données.

Performances et consommation mémoire

Le moteur de base de données tire désormais parti d’un cache en mémoire plus agressif, ce qui réduit les accès disque et améliore nettement la réactivité, notamment sur les grandes bibliothèques. En contrepartie, Jellyfin utilise davantage de RAM, mais cette mémoire est libérée automatiquement si d’autres processus en ont besoin. De nouveaux modes de verrouillage (locking) viennent aussi améliorer la stabilité dans les environnements sollicités.

Compatibilité et évolutions techniques

Jellyfin abandonne définitivement le support des systèmes ARM 32 bits (armhf). Pour continuer à bénéficier des mises à jour, il faut désormais utiliser un système d’exploitation ARM64.

Autre changement annoncé : la suppression prochaine du support TLS/SSL interne (prévue pour la version 10.12.0). Les développeurs recommandent désormais d’utiliser un reverse proxy (comme Nginx ou Caddy) pour la gestion des certificats, plus fiable et plus simple à maintenir.

Nouvelles fonctionnalités et améliorations clés

Parmi les nouveautés les plus notables de Jellyfin 10.11.0 :

• Recherche plus rapide et gestion enrichie des favoris (Live TV, clips, albums photo, saisons, etc.) ;
• Support HEVC dans Firefox 134+ et option pour désactiver le style natif des sous-titres ;
• Affichage en collections des séries et ajout d’un splash screen personnalisable sur la page de connexion ;
• Tableau de bord enrichi, avec statistiques médias et suivi de l’espace disque ;
• Support AV1 via VideoToolbox et passage à FFmpeg 7.1, pour de meilleures performances en décodage et transcodage ;
• Amélioration du rendu HDR et Dolby Vision sur certains matériels compatibles ;
• Nouvelle API de sauvegarde (BackupApi) et migration complète des plugins vers EF Core.

Cette version corrige également plusieurs failles de sécurité, y compris des correctifs issus de projets externes.

En synthèse

Jellyfin 10.11.0 pose des fondations solides pour l’avenir du projet. Plus rapide, plus stable et mieux structurée, cette version facilite la maintenance tout en préparant de futures innovations. Une mise à jour vivement conseillée, à condition de la planifier avec soin…. pensez aux sauvegardes.

source

Get Graphics Drivers and Hardware Transcoding BACK for Plex/Jellyfin/Emby on your Synology NAS

Note – the video on this fix will be published soon and I will update this article with images ASAP.

Synology’s 2025 refresh brought the DS225+ and DS425+ with the familiar Intel Celeron J4125, but it also quietly removed the kernel graphics driver support that Plex, Jellyfin, and Emby use for hardware transcoding of H.264 and HEVC. This guide explains what changed, why it matters for real-world streaming, and how you can restore GPU-accelerated transcoding on these models using an unofficial SSH method shared by the community. If you rely on your NAS to reshape 4K or high bitrate files for phones, tablets, hotel TVs, or limited connections, this walkthrough will help you get that efficiency back.

IMPORTANT – Massive credit to RROrg group over on Github for ‘cracking the nut’ on this with their latest repo HERE 

Additionally, credit to Luka @ Blackvoid, who made this great article, covered this first and gave me permission to use his guide here and in my upcoming video. Read his article HERE

What Happened to Hardware Transcoding on the Synology 2025 NAS, and Why Is This a Problem

When Synology launched the 2025 “x25” lineup, users expected a minor refresh of familiar models like the DS225+ and DS425+. Instead, they discovered that Synology had removed the i915 graphics driver from DSM, effectively disabling hardware transcoding on the Intel Celeron J4125 CPU. This meant that Plex, Jellyfin, and Emby could no longer tap into the iGPU’s Quick Sync Video capabilities. Synology confirmed the change in support tickets, explaining that both H.264 (AVC) and H.265 (HEVC) transcoding had been deliberately blocked at the kernel driver level. The company cited licensing costs for HEVC, even though AVC is license-free, and argued that most client devices already support native playback. The earliest and longest discucssions on this topic are HERE on this Plex Forum thread.

The result is a significant downgrade for users who bought these models expecting the same multimedia performance as their predecessors. Instead of 10–20% CPU usage during hardware-accelerated transcoding, users now see 80–100% CPU utilization when reshaping video on the fly. For remote streaming, converting 4K to 1080p or 720p becomes slow, inefficient, and often unworkable. This change undermines the value proposition of the J4125 platform and leaves Plex and Jellyfin users with hardware that is technically capable but artificially restricted, creating frustration across the Synology community.

Disclaimer: This Is Unofficial – Know the Risks!

Before diving into the workaround, it is important to understand that this method is not supported by Synology and involves altering core system modules via SSH. These steps rely on community-compiled drivers and are provided “as is,” without warranty. Making changes at the kernel level can cause instability, break after DSM updates, or in the worst case, lead to data loss if mistakes are made. You should always keep verified backups of your data before proceeding, and only attempt this if you are comfortable working with the command line and root-level access. Proceed entirely at your own risk.

Step By Step Guide to Get J41225  Graphics Drivers Hardware Transcoding Back

1. Download the Source Code

   • Go to Dave Russell’s GitHub repo (007revad) and download the Source Code (.zip) for the graphics driver fix.

   • 

   • Do not unpack the archive on your computer.

2. Create a Folder on Your NAS

   • Log into DSM and create a new Shared Folder (e.g. scripts) on your main volume.

   • 

   • Make sure your DSM account has full access, since root privileges will be needed later.

3. Upload the Archive

   • Use File Station or SMB to upload the .zip file into the new scripts shared folder.

   • 

   • Once uploaded, extract it on the NAS by right-clicking and selecting Extract Here.

   • 

   • If extraction creates subfolders, move the relevant script files (such as transcode_4_x25.sh) directly into the main scripts directory for easier referencing.

   • 

4. Create a Scheduled Task

   • Open Control Panel > Task Scheduler.

   • 

   • Select Create > Triggered Task > User-defined Script.

   • 

   • Give the task a name (e.g. Synogfx).

   • 

   • Set the User to root.

   • Set the event to Boot-up so the script runs every time the NAS restarts.

   

5. Point to the Script

   • In the task settings, paste the full path to the script file, for example:

     sh /volume1/scripts/transcode_4_x25.sh


   • If unsure, right-click the .sh file in File Station, select Properties, and copy the full directory path.

   • 

6. Confirm and Save

   • DSM will warn you about using root and non-standard scripts. Acknowledge this and proceed.

   • 

   • Enter your DSM admin password when prompted.

   • The scheduled task will now appear in the list.

   • 

7. Run the Script

   • Right-click the new task and select Run to execute it immediately.

   • 

   • Optionally, reboot your NAS to confirm that the driver loads automatically on startup.

   • 

8. Verify Hardware Transcoding

   • Open Plex (or Jellyfin/Emby) and play a file requiring transcoding.

   • 

   • Check playback statistics: you should now see HW (hardware transcoding) instead of CPU-only usage.

• 

Conclusion

Synology’s decision to remove iGPU drivers from the 2025 DS225+ and DS425+ left many users frustrated, especially those who rely on Plex or Jellyfin for remote streaming. While the company cites licensing costs and client-side decoding as justification, the hardware itself remains fully capable of transcoding. Thanks to community-driven efforts, it is possible to re-enable Quick Sync on these models with an SSH-based workaround. This fix restores the efficiency and functionality users expected, though it comes with risks and requires maintenance after reboots. For multimedia enthusiasts who value hardware transcoding, this unofficial solution may be the only way to unlock the true potential of these NAS systems.

---

SUBSCRIBE TO OUR NEWSLETTER
[contact-form-7]
Join Inner Circle

This description contains links to Amazon. These links will take you to some of the products mentioned in today's content. As an Amazon Associate, I earn from qualifying purchases. Visit the NASCompares Deal Finder to find the best place to buy this device in your region, based on Service, Support and Reputation - Just Search for your NAS Drive in the Box Below

Need Advice on Data Storage from an Expert?

Finally, for free advice about your setup, just leave a message in the comments below here at NASCompares.com and we will get back to you. Need Help? Where possible (and where appropriate) please provide as much information about your requirements, as then I can arrange the best answer and solution to your needs. Do not worry about your e-mail address being required, it will NOT be used in a mailing list and will NOT be used in any way other than to respond to your enquiry. [contact-form-7] TRY CHAT Terms and Conditions   Alternatively, why not ask me on the ASK NASCompares forum, by clicking the button below. This is a community hub that serves as a place that I can answer your question, chew the fat, share new release information and even get corrections posted. I will always get around to answering ALL queries, but as a one-man operation, I cannot promise speed! So by sharing your query in the ASK NASCompares section below, you can get a better range of solutions and suggestions, alongside my own.

WE LOVE COFFEE