Guide: Running Jellyfin in Synology's DSM 7 Using Docker Compose

[Kurt]

Yeah, that's it.

You could just add each genre individually. It would be a bit more work, but it will get you to the same outcome. Though one benefit of doing it this longer way is that it will make it impossible for you to mess up and mount the top-most folder to the library.

Now i have another problem... 

I stopped JF, and edited yaml file to "- /volume1/musicmusic:ro"/

The project was rebuild and when i went to choose the libraries, all the folders side the main one (music) become visible. I start adding each one and at the end, when i tried to save, i received the following error:

   

Even on the 1st time i set up JF, hadn't any problem. I'm feeling so dumb.
Maybe i should delete everything and start all over again from the scratch.

--

Update:

I decided to start from the scratch and now it seems to be working (scanning all the files/folders).
I'm a totally noob so, probably the issue was the number of times i edited the yaml file to try to make it work.


Thanks!

[Efficient_Good_5784]

yaml files are sensitive to spacing, so it could have been that.
Sorry about the late response. I was going to suggest that it may have been a permissions issue. Like maybe you switched the user that would run Jellyfin this time or something like that.

Also, take advantage of containers. You're allowed to separate the important data from the rest of the service.
So next time, make a copy of your config folder. So if you ever mess up, you can always go back. For example, Jellyfin v10.9 will make irreversible changes that won't allow your config files to go back to v10.8.13.
With a backup, you could go back.

Same if you mess things up, you got a backup to rely on.

I would even say don't wait for updates to make backups too. You could manually (or with a simple script) make a copy of your config folder at set intervals. This way, you'll always know that you have some form of going back in time if things go bad.

[Kurt]

yaml files are sensitive to spacing, so it could have been that.
Sorry about the late response. I was going to suggest that it may have been a permissions issue. Like maybe you switched the user that would run Jellyfin this time or something like that.

Also, take advantage of containers. You're allowed to separate the important data from the rest of the service.
So next time, make a copy of your config folder. So if you ever mess up, you can always go back. For example, Jellyfin v10.9 will make irreversible changes that won't allow your config files to go back to v10.8.13.
With a backup, you could go back.

Same if you mess things up, you got a backup to rely on.

I would even say don't wait for updates to make backups too. You could manually (or with a simple script) make a copy of your config folder at set intervals. This way, you'll always know that you have some form of going back in time if things go bad.

Hi again,
No problem. I only saw your reply now.

When i started from the scratch and decided to create a backup folder (outside of the main one for JF), and then i went to Container Manager -> Container and exported (only) the container settings. And to play safe, i also exported to my pc.

Now it's all working like i want; just need to figure out how to access from outside of my network without having to use a VPN (like Plex and Plexamp).


Thanks for all your time and patience!

[Haxornator]

Can anyone provide additional information on migrating from the community version of Jellyfin, to the docker version.

I mostly want to keep my configuration.

[TheDreadPirate]

You'd have to find where the community version stores the jellyfin data and find /config and make a copy of it.

[XavierP56]

I have followed this great tutorial, got it working.
I set network to host, I can connect but I don't see my Chromecast Ultra.
I'm using the embedded Web client (192.168.1.241:8096, where 192.168.1.241 is my DS423)

I'm using Ethernet on the PC, on the DS423+, the Chromecast Ultra is also on Ethernet. All in 192.168.1.x.
Can't understand....

If I'm using an android client, I can see the Chromecast
So it seems the embedded client can't see Chromecast.

What goes wrong ?
Thanks.

[xyu]

My YAML file is set up like this, and I've tried adding the volume2 bind and target to the compose file.  However, when i try to add the library in jellyfin, the library on volume2 does not show up at all.  (I ran out of space on volume 1 and would like to store my media in volume2)

Code:

version: '3.5'
services:
  jellyfin:
    image: jellyfin/jellyfin
    container_name: jellyfin
#    user: uid:gid
    network_mode: 'host'
    volumes:
      - ./config:/config
      - ./cache:/cache
      - type: bind
        source: /volume1/Media/Movies
        target: /movies
      - type: bind
        source: /volume2/Media2/Movies
        target: /movies
      - type: bind
        source: /volume1/Media/Shows
        target: /shows
      - type: bind
        source: /volume1/Media/Books
        target: /books
        read_only: false

Am I doing something wrong, is there another place i need to add volume2 so that jellyfin knows to look for it when adding a Library?

[quecup]

This will be a short guide for Synology NAS units running DSM 7 on how to run a Jellyfin

This worked for me up until I tried playing back any HDR content. In that case I have problems (either a fatal error on the Jellyfin player, or jerky video, depending on the options) on my DS918+

The error goes back to tone mapping. This is when I'm playing HDR content on a non-HDR screen or on a screen that doesn't support the content's specific HDR type (DV, HDR10, etc).

Three paths:

1. If Enable VPP Tone mapping is enabled, then I get a "fatal player error" when I try to play HDR content
   
2. If Enable Tone mapping is enabled, then my NAS CPU is near 100%, the video stutters, and it seems that hardware transcoding is bypassed and it uses software transcoding instead. Unwatchable.
   
3. If none are enabled (ie. tone mapping is disabled), then the HDR content plays just fine, but has no tone mapping. So, colour is off.
   

According to the Github bug thread [bug] 10.8.12 breaks transcoding with HDR content on Synology DS1019+ #10550 it seems that this is not going to be fixed. Can't be fixed. Intel's OpenCL driver no longer supports Linux 4.4.x (ie. every Synology device), and the only fix is to rollback to Jellyfin 10.8.11. This thread has good info on the problem.

I updated my NAS today to the latest DSM 7.2.2-72806 Update 1 which still runs the 4.4.302 kernel. Given what I've read from Synology, they are not going to jump their Linux kernel forward to regain support for Intel OpenCL's current driver. Synology has officially dropped HW encoding and decoding support with the latest DSM 7.2.2-72806. Is this in reaction to Intel dropping support for Linux 4.4.x? Either way, I can't see Synology fixing this after putting out a press release saying that breaking codec support is a new and improved feature, not a bug.

This took me a long time to figure out. Can you add to your instructions, that Synology owners who intend to HW transcode their HDR content, should use Jellyfin 10.8.11 instead of the latest version. And if they intend to go with the latest Jellyfin anyway, they should disable both tone mapping options. Otherwise, stutters and crashes will happen with every HDR video that needs transcoding.

It seems plausible that future Jellyfin versions (with baked in Intel driver updates) could break Synology HW decoding further. Right now, it's just HDR tone mapping that's broken on versions after 10.8.11.

As for me, I'm going to live with the bad colours for now, and possibly try pre-transcoding my HDR files with tdarr or something. That's a far future project.