Jellyfin: Difference between revisions

(9 intermediate revisions by 7 users not shown)

Line 1:

Jellyfin is the volunteer-built media solution that puts you in control of your media. Stream to any device from your own server, with no strings attached.

== ~~Usage~~ ==

== Installation and configuration ==

<code>~~services~~.jellyfin.~~enable = true;~~</code>

To get up and running with Jellyfin, add the packages <code>pkgs.jellyfin</code> <code>pkgs.jellyfin-web</code> & <code>pkgs.jellyfin-ffmpeg</code> to your `configuration.nix` file as shown below.

== Hardware ~~Transcoding~~ ==

In most cases you want to make most of your hardware. Modern boards often come with ~~Hardware Accelerators~~, all you need to do is enable it!

{

services.jellyfin.enable = true;

environment.systemPackages = [

pkgs.jellyfin

pkgs.jellyfin-web

pkgs.jellyfin-ffmpeg

];

}

</syntaxHighlight>

If you want more advanced configuration, use something like what's shown below and [https://search.nixos.org/options?query=jellyfin see the docs for more configuration options]

{

services.jellyfin = {

enable = true;

openFirewall = true;

};

}

</syntaxHighlight>

Once you have included the packages to be installed, and enabled and configured Jellyfin to your liking, then rebuild your system for changes to take effect.

<syntaxHighlight lang=bash>$ sudo nixos-rebuild switch</syntaxHighlight>

After the rebuild is complete, Jellyfin should be running. Verify that it is with the following command.

<syntaxHighlight lang=bash>$ sudo systemctl status jellyfin</syntaxHighlight>

If jellyfin is not running you should be able to start it by running <code>jellyfin</code> in your terminal.

<syntaxHighlight lang=bash>$ jellyfin</syntaxHighlight>

After you've verified that Jellyfin is running you can start the configuration process.

* The Jellyfin server should be running on port 8096.

* Go to http://localhost:8096 if you are setting this up on your primary computer or want to test your build locally.

* If you're logging into a remote server, replace localhost with the ip address of the server.

=== Allow Jellyfin to read external drives ===

You might encounter permission issues when you try to access external drives if you haven't configured anything else with the server yet. If you haven't explicitly set up a mounting configuration for your drives and instead let your desktop environment (e.g. GNOME or KDE) automatically mount it when you try accessing it via their file explorers, Jellyfin won't be able to access the drive. This is because the desktop environment mounts it to your user, while Jellyfin runs by default as the "jellyfin" user.

The easiest way to allow it to see these external drives is to change the service's user . Here is an example:

services.jellyfin = {

enable = true;

openFirewall = true;

user="yourusername";

};

</syntaxhighlight>

If you have changed the user option after you have already installed Jellyfin, you have to change the ownership of the folder /var/lib/jellyfin to the user you set it to by doing this:

sudo chown -R /var/lib/jellyfin

</syntaxhighlight>

The alternative is to explicitly mount the drives via [[Filesystems]]. This takes more effort to set up and requires every new drive to be explicitly declared, but allows more control in what Jellyfin is allowed to see.

=== Intro Skipper plugin ===

If you install the Intro Skipper plugin, it will not be able to display the skip button in the web interface. This is due to the plugin being unable to modify contents of files in the nix store. To get around this you can make the changes yourself with this:

nixpkgs.overlays = with pkgs; [

(

final: prev:

{

jellyfin-web = prev.jellyfin-web.overrideAttrs (finalAttrs: previousAttrs: {

installPhase = ''

runHook preInstall

# this is the important line

sed -i "s#</head>#<script src=\"configurationpage?name=skip-intro-button.js\"></script></head>#" dist/index.html

mkdir -p $out/share

cp -a dist $out/share/jellyfin-web

runHook postInstall

'';

});

}

)

];

</syntaxhighlight>

== Hardware transcoding ==

In most cases you want to make most of your hardware. Modern boards often come with a hardware accelerator, all you need to do is enable it!

Source: https://jellyfin.org/docs/general/administration/hardware-acceleration.html

=== VAAPI ===

=== VAAPI and Intel QSV ===

VAAPI is often available on ~~intel boards (~~Intel ~~HD)~~.

VAAPI and QSV is often available on platforms with Intel GPUs but need their corresponding packages in <code>hardware.graphics.extraPackages</code>.

Line 20:

Line 103:

vaapiIntel = pkgs.vaapiIntel.override { enableHybridCodec = true; };

};

hardware.~~opengl~~ = {

hardware.graphics = { # hardware.opengl in 24.05

enable = true;

extraPackages = with pkgs; [

intel-media-driver

vaapiIntel

intel-vaapi-driver # previously vaapiIntel

vaapiVdpau

~~libvdpau-va-gl~~

intel-compute-runtime # OpenCL filter support (hardware tonemapping and subtitle burn-in)

vpl-gpu-rt # QSV on 11th gen or newer

intel-media-sdk # QSV up to 11th gen

];

};

Line 36:

Line 120:

</syntaxHighlight>

Related: [[~~Accelerated_Video_Playback~~]]

Related: [[Accelerated Video Playback]] and [[Intel Graphics]]

[[Category:Server]]

[[Category:Applications]]