intro-skipper VS docker-jellyfin

you could always cut up the video into segments A,B,C,D,E using like ffmpeg -ss 00:00:00 -t 00:10:00 -i input -c copy A.ext (where A is the first 10 minutes of video) and then recombine with https://trac.ffmpeg.org/wiki/Concatenate, might take a while though and some basic math. maybe you could do something programatically with chromaprint by identifying the repeating audio segments? that's just an idea since that's what this jellyfin plugin does to identify repeated segments of shows in the form of opening credits.

Is anyone using the modified web interface for the Intro Skipper plugin https://github.com/ConfusedPolarBear/intro-skipper/blob/master/docs/web_interface.md with Unraid?

You mean the beta software with many bugs? Not remotely acceptable in my opinion. https://github.com/ConfusedPolarBear/intro-skipper/issues

Make sure to follow the instructions - Here

Download and extract the latest modified web interface from GitHub actions Click the most recent action run In the Artifacts section, click the jellyfin-web-VERSION+COMMIT.tar.gz link to download a pre-compiled copy of the web interface. This link will only work if you are signed into GitHub.

I believe you would have to install the modified web interface to get the prompt to skip the intros. Instructions to install the modified web interface if you run Jellyfin as a container: https://github.com/ConfusedPolarBear/intro-skipper/blob/master/docs/web_interface.md

Please read through the installation instructions on the README and the instructions for using the modified web interface (method 2 is what I helped improve).

The container's Dockerfile is based on Ubuntu Jammy and performs a straight-up install of the debs from repo.jellyfin.org, so it'll be the same as on any Debian-based system, indeed /var/lib/jellyfin/plugins.

The Linuxserver.io image is, first of all, a 3rd party unofficial image, but with our blessing. They take a base Ubuntu OS image and install our official Ubuntu packages in the Docker environment. On startup it also executes the same binary in the end, so functionally, to anyone who doesn't know any different, they're the same: you get Jellyfin out in the end.

Are you using Docker? If so you’ll probably need to expose the device through to Docker too. Instructions for Pi here, which may or may not work: https://github.com/linuxserver/docker-jellyfin

I'm on an Arch Linux host with linuxserver image (J4005 with UHD600). OpenCL tone mapping does not work out of the box. I have to add DOCKER_MODS=linuxserver/mods:jellyfin-opencl-intel , per this GitHub issue, as an additional environment flag to my docker-compose.yml file, lest ffmpeg complains about not able to find device ocl@va.

If you don't want to migrate to the official one, just wait for https://github.com/linuxserver/docker-jellyfin/pull/155