Jellyfin ffprobe

General Discussion
1

Hello,
I’ve recently installed dietpi v9.11 on my old raspberry pi 2 (arm7, 32bits) and installed Jellyfin server on it. My files are stored on a samba shared mounted on the raspberry at startup.

It works quite well (no transcoding) for searching / displaying informations on the movies… except for files bigger than 4GB.

For files bigger than 4GB, ffprobe never ends when scanning the library. I know it’s not a dietpi problem, but I can’t say if it’s a ffprobe or a samba limitation problem. I also know that my RPi 2 is really weak to support latest version of Jellyfin but I would be happy just to solve this problem.

If someone here have some clues,
thank you.

Stéphane

2

It is a samba thing, are your movies on a separate drive from the OS? Did you set up samba with dietpi-software so it uses the dietpi user and a separate mount point? Basically it looks like you need to have your samba share mounted to /mnt/dietpi_userdata directly which is handled in the samba config files.

3

Thanks a lot for your help.

The drive containing the movies is not directly connected to the RPi but available as a samba
share. I tried to use dietpi-drive_manager to setup the mount point, but it did not changed the
ffprobe problem.
In fact, I realize it’s probably not a samba problem as most of the movie files were downloaded
by the RPi with Nicotine+ and directly saved to the samba shared drive. So if Nicotine+ can
read/write files bigger than 4GB on the samba share, the problem is probably on the ffprobe
side ?

Stéphane

4

Maybe it’s about file system permissions that files on the samba share are not readable by Jellyfin?

5

Thank you for your answer.

Everything works fine except for files bigger than 4GB.

As I run a 32bit system, I suspect jellyfin-ffmpeg/ffprobe 32bits arm7 version (and perhaps
others) to contain a bug for files bigger than 4GB (4GB is the maximum integer value
that can be stored on a 32bits integer).

Stéphane

6

I don’t think this is a bug. Probably a technical limitation of the 32bit app in general.

7

I am guessing usb drive, which was mentioned in a couple threads on the internet having to do with the 4GB limit. Do you have the samba mounting @ / on that drive?

Anyway to test, just change where samba mounts to a folder with the movies and not / and see what happens, of course you have to change the samba config.

8

Okay, maybe ignore my advise since it is solved??? A 32bit limitation, thought we got rid of those years ago but maybe not.

9

I managed to setup the build environment for jellyfin-ffmpeg for debian bookworm armv7, I’ll try to investigate a bit in the next weeks and if I can find a solution, I will submit it to Jellyfin or ffmpeg team.
Thanks for your support.

1 Like
10

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.