Jellyfin on Roku 3.0.0 released

[jimdogx]

It didn't work. 

"Install Failure: No manifest. Invalid package."

A legacy version of the app (v2.3.1) will be available in the Roku store on Tuesday at 10 am Pacific time.

[Soloman2469]

Live TV no longer shows the guide, just the channel list.  I've been through the settings and if there is a way to bring the guide back I've missed it.

While in the Live TV library, press the * button and select a new view.

I did miss that, thank you.

[joshuaboniface]

 its maxed out on the supported operating system and I cant update my Jellyfin server anymore because the more current ones are not supported on the latest operating system my computer can handle.

What OS/system are you running that can no longer get updates, and what version of Jellyfin are you on? There might be other workarounds to get your server updated if we know exactly what you're running, though this might be better in a Troubleshooting thread. Or of course, we now have the Legacy Roku app coming very shortly that will let you "roll back" so to speak. But it is worth noting that Roku is actually the last - or close to the last - app that wasn't enforcing at least 10.9 if not 10.10.

I wish there was a way to not have these updates forced.

That is, unfortunately, on Roku (and the various other similar App Store-driven client devices) - we push out new versions, and they force updates. Probably the only thing you could get that didn't do this is a DIY box like a Kodi Pi or something like that and then just never update it.

For what it's worth, we've seen a disproportionate number of people running the 10.8.x series of releases in response to this new Roku version, which really begs the question of why so many folks are running a 2-major-version-old version of Jellyfin still. I can think of a few possible reasons, but hard confirmation from a few folks would be helpful here. If there's a serious blocker in this regard and we can fix it, we're more than willing to, we just need to know what it is!

[mc1984]

 its maxed out on the supported operating system and I cant update my Jellyfin server anymore because the more current ones are not supported on the latest operating system my computer can handle.

What OS/system are you running that can no longer get updates, and what version of Jellyfin are you on? There might be other workarounds to get your server updated if we know exactly what you're running, though this might be better in a Troubleshooting thread. Or of course, we now have the Legacy Roku app coming very shortly that will let you "roll back" so to speak. But it is worth noting that Roku is actually the last - or close to the last - app that wasn't enforcing at least 10.9 if not 10.10.

I wish there was a way to not have these updates forced.

That is, unfortunately, on Roku (and the various other similar App Store-driven client devices) - we push out new versions, and they force updates. Probably the only thing you could get that didn't do this is a DIY box like a Kodi Pi or something like that and then just never update it.

For what it's worth, we've seen a disproportionate number of people running the 10.8.x series of releases in response to this new Roku version, which really begs the question of why so many folks are running a 2-major-version-old version of Jellyfin still. I can think of a few possible reasons, but hard confirmation from a few folks would be helpful here. If there's a serious blocker in this regard and we can fix it, we're more than willing to, we just need to know what it is!

Thanks for replying! So I'm running a Mid 2012 Mac Mini. The last supported OS is Catalina 10.15.7. I tried updating to a more current Jellyfin build, but as fas as I can tell 10.8 is the newest version that can run on 10.15.7. The work around is to figure out how to install an unsupported operating system on my computer. I'm sure if i was able to give up a couple of days trying to figure it out I could, but that is a couple of days I do not have to give at the moment. My entire issue is that something that was working perfectly fine the night before, the next day is completely unusable. I, as I'm sure a ton of people in my same situation, spent a TON of time setting up a working system with Jellyfin 10.8 and was happy with the way it performed. I don't have extra money to spend on a newer computer, at don't really feel like I should have to when the day prior to, everything was working fine. This is at the core of my issue with the current state of technology. The constant updating and "improving" if you want to call it that, forces obsolesce for otherwise perfectly fine systems.

[mylinuxguy]

Thanks for the response! After checking, it seems the server version was outdated, and we now have 10.10.6 running on our setup with container manager/Synology. Updating the version however, completely wiped the old server (settings, users and indexed media), so we just reconfigured from scratch and are now waiting for the chance to test streaming again once the media hopefully syncs up. 

Would you have any suggestions for maintaining smoother server updates like this in the future? 

Thank you!

The issue is that you need to mount the /config folder to be outside the container.

As the name implies, a container holds all relevant data for a service.
If you delete the container, you delete everything associated with it since all of that is inside of it.

Docker lets you host mount external directories outside of the container, and makes it accessible from the inside.
On a new install, you just need to set a host mount linked to /config on the inside.
Then when you build and start the container for the first time, it will populate all necessary things to wherever on your system you linked /config to.

Whenever you need to update containers, you simply link the place where your previous /config folder was mounted on.

Keep a mental note that updating Docker containers is not like updating regular programs.
You always need to make a new container and delete the old one. There's no way to update the image of an existing container, so you always have to start fresh for a new image version.
Host mounts lets you carry over content from past containers to newer ones as those remain after you delete a container.

Not sure about proper form etiquette... just wanted to say... and maybe I updated wrong... but I have a docker container running jellyfin.  I have: 

Code:

services:
  jellyfin:
    image: jellyfin/jellyfin
    container_name: jellyfin
    network_mode: 'host'
    restart: 'unless-stopped'
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/Chicago
      - VERSION=docker
    volumes:
      - /data/jellyfin/config:/config
      - /data/jellyfin/tv:/tv
      - /data/jellyfin/movies:/movies
      - /data/jellyfin/cache:/cache

I did a

Code:

docker compose down
docker compose pull 
docker compose up -d

and went from 10.10.3 to 10.10.6 without needed to back anything up or re-make changes. 

Maybe an older 10.8.x to 10.10.6 might not have gone smoothly, but 10.10.3 to 10.10.6 was painless just doing a docker compose pull to get the latest jellyfin code.

[Efficient_Good_5784]

The work around is to figure out how to install an unsupported operating system on my computer.

You can get more life out of your old computer by installing Linux on it.
You would then be able to properly install a newer Jellyfin server version either directly onto the OS, or through Docker.

The constant updating and "improving" if you want to call it that, forces obsolesce for otherwise perfectly fine systems.

There's nothing that can be done about this. The Roku app got an update that fixed lots of issues that people were having with it.
The code changes it received works with the newer versions of Jellyfin only.

It's great that the old version worked for your use case. It wasn't for other people and their use cases.
However the blame for this issue you had lies with Roku as they force your apps to always get the latest updates.

[pingloss]

I'm seeing an issue when trying to play back files using the new v3 version. Files that are in 4K HEVC Dolby Vision Profile 8.1 (HDR10) are giving the following error:

'some encoding parameters are not supported by the QSV runtime.'

Playing the same file on the old version (2.3.1) works with no issues.

The new version tries to transcode the video
Stream #0:0 -> #0:0 (hevc (native) -> hevc (hevc_qsv))

while the old version does not
Stream #0:0 -> #0:0 (copy)

Any reasons why this would be?

[He-who-is-tired]

I'm seeing an issue when trying to play back files using the new v3 version. Files that are in 4K HEVC Dolby Vision Profile 8.1 (HDR10) are giving the following error:

'some encoding parameters are not supported by the QSV runtime.'

Playing the same file on the old version (2.3.1) works with no issues.

The new version tries to transcode the video
Stream #0:0 -> #0:0 (hevc (native) -> hevc (hevc_qsv))

while the old version does not
Stream #0:0 -> #0:0 (copy)

Any reasons why this would be?

I ran into a similar issue,  if you look in the settings (find your user icon,  arrow up to it and hit 'ok' zz then settings)  I think it's under 'playback', there's an option to 'disable hevc on this device' or something like that.   it stopped transcoding issues iwas having with video playback.

Hope that helps.   I'm not a dev or anything just another user who is amazed by the sheer volume of fixes,  updates,  enhancements just dropped!

---

[He-who-is-tired]

Jellyfin on Roku 3.0.0 has been released.

Announcement Blog Post: https://jellyfin.org/posts/roku-300

Release Notes: https://github.com/jellyfin/jellyfin-rok.../tag/3.0.0

NOTE:
* Jellyfin Roku requires a recent version of the Jellyfin Server (10.8 will not work).

* For those running on older Jellyfin servers and are not able to upgrade, there will be a Jellyfin Legacy App (2.3.1) available on the Roku store starting Tuesday, Apr 1, 2025 10:00 AM PT

I just gotta say:  WOW!  This is just an enormous amount of work, and kudos to 1hitsong and the whole crew for transforming the jellyfin app on Roku.  You guys rock,  ain't no 2 ways about it.

Sure there's gonna be some issues, but holy moly! You just modernized,  enhanced,  fixed, added,  so much,  it's just unbelievable!

Thank you!

[Alliyance]

So far,everything works, Great job!