[Issue]: Cannot resume media that is in progress about jellyfin HOT 10 OPEN

Hi, it seems like your issue report has the following item(s) that need to be addressed:

• You have not provided the ffmpeg log unaltered from the server. Please provide a valid ffmpeg log.

This is an automated message, currently under testing. Please file an issue here if you encounter any problems.

from jellyfin.

This is a bug I’ve also run into. Newly added movies (since upgrading to 10.9) do not allow resumes and don’t save the position at all.

Movies added under 10.8.x are able to resume mid-movie (even when running 10.9x)

there seems to be something broken when Jellyfin 10.9.x adds new movies that’s not allowing it to save the position.

from jellyfin.

If you are using a reverse proxy, please check your configuration, especially the one for websockets.

from jellyfin.

Not me. I’m just running it raw. It running locally too (nothing over the internet, all local intranet).

from jellyfin.

Newly added media (under 10.9.x) is missing the media info (other than file path and container). Meaning it missing video information, audio information m, subtitle information, etc.

This might be the bug that is the source of this bug.

from jellyfin.

Newly added media (under 10.9.x) is missing the media info (other than file path and container). Meaning it missing video information, audio information m, subtitle information, etc.

This might be the bug that is the source of this bug.

Check your ffmpeg install if this happens to you. Your ffmpeg installation is very likely to be invalid.

from jellyfin.

@gnattu

I use the default FFMpeg install for Debian Sid.

Running ffmpeg -version returns:

ffmpeg version 6.1.1-4+b2 Copyright (c) 2000-2023 the FFmpeg developers
built with gcc 13 (Debian 13.2.0-25)
configuration: --prefix=/usr --extra-version=4+b2 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --disable-omx --enable-gnutls --enable-libaom --enable-libass --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libglslang --enable-libgme --enable-libgsm --enable-libharfbuzz --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-openal --enable-opencl --enable-opengl --disable-sndio --enable-libvpl --disable-libmfx --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-ladspa --enable-libbluray --enable-libjack --enable-libpulse --enable-librabbitmq --enable-librist --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libx264 --enable-libzmq --enable-libzvbi --enable-lv2 --enable-sdl2 --enable-libplacebo --enable-librav1e --enable-pocketsphinx --enable-librsvg --enable-libjxl --enable-shared
libavutil      58. 29.100 / 58. 29.100
libavcodec     60. 31.102 / 60. 31.102
libavformat    60. 16.100 / 60. 16.100
libavdevice    60.  3.100 / 60.  3.100
libavfilter     9. 12.100 /  9. 12.100
libswscale      7.  5.100 /  7.  5.100
libswresample   4. 12.100 /  4. 12.100
libpostproc    57.  3.100 / 57.  3.100

Nothing exotic. Also, this exact FFMpeg install worked fine for Jellyfin 10.8.x. It's an internal changes between 10.8.x and 10.9.x that's causing these problems.

Yes, I'm not using the Jellyfin variant of FFMPeg -- I haven't had time to compile it for Debian Sid, and the vanilla version has worked perfectly for my needs. Also, the non-Jellyfin version also worked fine for 10.8.x.

from jellyfin.

It's an internal changes between 10.8.x and 10.9.x that's causing these problems.

And if you do this you need to remove the --ffmpeg cli in the startup options. We now explicitly search for jellyfin-ffmpeg for our debian packages. You need to remove that to use the system one.

from jellyfin.

I see, removing that option did allow Jellyfin 10.9.x to scan the metadata and populate it correctly.

I’ll check later if it allows resuming mid-media.

If so this is definitely a “user configuration error” … but could benefit from better fallback mechanism (or more visible errors letting the user how to fix it).

I’ll report back later, thanks.

from jellyfin.

Yep, this was exactly the issue I was facing. FFMpeg wasn’t being correctly detected because whatever script I used (likely from Jellyfin’s own documentation from 10.8.x era) had that extra ffmpeg parameter which worked fine in 10.8 but broke things in 10.9

I don’t currently contribute any code to Jellyfin (though might in the future if I have time), but I believe 1 of 2 remedies should be applied:

1. Ignore incorrect ffmpeg parameter passed to Jellyfin (thus restoring 10.8 functionality).
2. Warn about incorrect ffmpeg location directly in the interface.

from jellyfin.