Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I had a similar problem. For me it was because some of the videos were encoded with x265 which some client devices could not decode properly. Therefore the server had to decode them but it was not fast enough to do it.
I guess that is why on the Android device the videos are smooth, it can handle the decoding.
How did you solve it?
not OC, but i ended up redownloading whatever was x265 and replacing it with 264 or anything else.
also the 1060 in my NAS can do NVENC encoding. that helped a lot with compatibility.
You can also use something like handbrake to convert everything to 264 instead of redownloading everything. You can also set it up to convert after items are downloaded.
Does jellyfish not transcode on the fly?
Yes, but if the server isn't fast enough to do it, then you're going to have a bad time.
It can but it's the server hardware that decides your performance, you can just avoid transcoder on the fly and have h264 mp4 and can run JF on a toaster smoothly.
i had this problem. i fixed it with a faster machine. same os, same files. more cpu worked.
You mean a new sever or a new client?
yes!
server. it was choking on decoding
But I know of people running jellyfin on a raspberry, I have an old laptop but it's not that old... There'srno way to run it smoothly?
yeah, re-encode to a lighter encoding like 264. might be slightly larger, but less work for the cpu
I had the same issue, I used tdarr to re encode to h264 mp4
I do the same. I just have it do a transcode job every Sunday.
Yeah it's a great little set and forget kinda deal.
I did not really solve it. I looked around for a bit but found no good solution. The only thing that sort of worked was to copy the stream URL in Jellyfin and paste it into VLC Media Player, which could play the videos okay. But that was not really satisfactory for me.
In the end I installed a new OS on my PC which already came with the codecs to decode x265 preinstalled. I installed it for other reasons but it fixed also that issue and now I can play any video in the Jellyfin Media Player. I did not try if it also works in the browser. The OS I am now using is called Nobara.
So it's a problem on codecs on my pc, not my server, correct? So installing the correct drivers should solve the issue?
I do not think they are called drivers, but yes, installing the needed codecs should work. I just did not find out how to do it properly.
I just used ffmpeg to encode my files to h264, worked on all my devices
Doing this will prevent my files from seeding, I'd like to find a more "universal" solution
Thanks for the info tho!