I have one of these that I use as a Jellyfin server. It’s not affected by those problems and has been performing more than adequately for my purposes, after setting up hardware transcoding
I have one of these that I use as a Jellyfin server. It’s not affected by those problems and has been performing more than adequately for my purposes, after setting up hardware transcoding
Also, Roku or whoever has no way of verifying you pirated it and aren’t just watching a blu-ray you owned and ripped to your jellyfin server
Glad to hear it. Should be relatively straightforward to fix it, now that you’ve identified the issue.
In order to see if it’s client-side or server side, let’s try another client. Try installing Jellyflix and see if it gives you the same issue when you lower the bitrate
Which client are you using? Are you switching the max bitrate during playback, or while it’s paused?
Intel N100 Beelink box with 16GB of single channel RAM runs my Jellyfin server and Caddy. It’s also hooked up to my home theater system directly so I can use Moonlight on it to stream my main gaming PC.
My storage is a 4-bay aluminum USB 3.0 external enclosure attached to an M1 Mac Mini running Asahi Linux (Arch BTW). The Mac mini runs my Arr stack and mergerfs on the external drives so I can load balance across them and scale it up or down as needed. So basically the Mac Mini acts as a NAS.
Symphonium is also the best for listening to audiobooks in the car. It has a really comprehensive set of DSP options
Have you tried setting up Kodi and the Jellyfin plugin instead on it?
The AndroidTV client does notably have a quirk in that it’ll stop playing at the end of a season if doing an autoplay of a TV show and playlists don’t seem to work for TV shows yet, so unless you’ve got something with long seasons you can put on, it might be best to make a collection and play that.
It’s cool. I stalk the discord and the forums, so I pick up the dev chatter.
Hope you’re enjoying it! I love how there’s no central servers like Plex has. It’s my own private Netflix so I can share what I have with my friends and family easily!
It’s planned to be upstreamed in version 10.10, due to come out approximately 6 months from now.
There’s a couple things that stick out to me in these logs:
the androidtv client logs show the crash was due to a time-out while waiting for the server to respond to a request for over 3 seconds.
you included a DirectStream log, that’s usually not too hard for even a Raspberry Pi to handle reasonably well
the first log I looked at showed libx264 was using 36 threads
So my guess is that, due to video encoding not scaling all that well across larger numbers of threads, your server is being bogged down with this transcoding and isn’t providing http responses fast enough to your client device(s).
A simple way to troubleshoot this would be to explicitly set the transcoding thread count to something a bit lower than what your server has, say 16 or 20, and see if that does any better.
An obvious potential fix would be to use hardware acceleration if it’s available to you. I run my Jellyfin server off of a little N100 mini PC and it can transcode 4K HDR 70 Mbps video (tonemapping included) at about 45 fps due to the hw acceleration. That said, I know it can be tricky to set up in a VM and you may not have the HW accel capability in your server CPU anyhow.
CIFS is probably more robust than curlftpfs, but I’d probably just go full NFS on it if you care about performance.
And that’s why you always make a backup before trying out alpha or beta software
I use Jellyseer for the same thing. Works great and integrates with radarr/sonarr
I’ve personally found that maintaing Jellyfin via Docker is far simpler and provides a more convenient upgrade path than a direct installation. I have a docker compose file in my home folder so when I want to upgrade it’s just docker compose pull
followed by docker compose up -d
A shield is just a client, can’t be used as a server AFAIK.
DTS is just a different set of audio formats/standards, originally popularized in theaters by the movie Jurassic Park.
DTS-HD Master Audio is their lossless audio format, meaning it decompresses out to being the exact same audio bit-for-bit as the mixer heard when they finalized the audio for the movie.
Likewise, Dolby TrueHD is also a lossless digital audio format, so it also decompresses to the exact same audio the mixer heard when mixing/mastering the movie.
The Shield is also one of the only Android TV devices that passes on HD audio codecs, so if you stream any Blu-ray rips with DTS-HD Master Audio or Dolby TrueHD and you want passthrough to work correctly, you probably want a Shield.
The very first time you connect you’ll need to do it from a web browser, rather than the app. Once you have your username/password setup you can do everything else from the android app