• 11 Posts
  • 47 Comments
Joined 1 year ago
cake
Cake day: August 15th, 2023

help-circle










  • If your Jellyfin collection starts to grow big enough, and x264 transcoding on the fly is as easy as passing through the GPU these days…it’s pretty much a no brainer. You have small files, and if someone still needs x264 (which would need to be specifically a Firefox streamer, as I believe Chrome supports it, and the Jellyfin apps also support it if your computer/phone does), the transcoding on the fly can be done using about 1-2% of the server CPU. I did something like 12 simultaneous different transcodes once, and my oldish i5 9500T held its ground perfectly, I think it reached about 35% CPU at the peak of it.


  • Hmmm what do you mean the video kept crashing? Where is your server set up? What are you using for OS? Is it bare metal, is it running in a Windows, in a VM, in a container?

    In my case it’s running in a Proxmox LXC container (the container is running Ubuntu). I’m passing through the integrated GPU, as instructed in the Jellyfin docs. And then I enable Intel QSV transcoding on Jellyfin. The CPU consumption is close to negligible. Then again, you need an Intel CPU capable of x264 transcoding at decent rates. Anything after 8th gen should be able to do the trick (with this I mean, you can ALSO transcode whatever source to x265 on the fly, but that’s not a feature I’m actively using at the moment, as the resulting file is usually larger anyway). I’m using an i5 9500T, and I benchmarked something like 8 transcodes simultaneously to almost no impact. I think it was starting to be noticeable past 12 transcodes simultaneously. But that’s some heavy streaming there! That’d mean EVERYONE is connecting at once to your server using FF (I believe Chrome is x265 capable, and the apps also take x265 just fine if your phone/computer support it). So…in short, my i5 from a few generations ago is already overkill for x265















  • Sigh…Thanks. I wish it was. I just ran the same Alan Wake install on the provided Lutris and well…the Textures are indeed fixed, I can see the FBI jackets and the faces look better…but now performance is abysmal, with frame drops to 10-15fps (1080p all max)…and RT is not even enabled (still grayed out), checked both in Wayland and X11. I think for a 7800XT I should be getting much better as long as RT or Path Tracing is not running.

    EDIT: Seems this happens only with AW2. Cyberpunk and Starfield seem to have similar performance as before. So there’s something going on with AW2 in Nobara.


  • So…how did you get that damn partition working?? I’ve just tried it. Which required me an EFI partition of at least 600MB. I already had it at 500MB but apparently it didn’t think that was enough…So I had to reinstall all of windows in order to resize the EFI. Then Nobara installer was happy when I chose the EFI partition as “/boot/efi”, and 500GB at the end of the same SSD as “/”. After a reinstall, reboot…and it goes to Windows. Ugh. Manually choosing from the BIOS the new “Fedora” entry I get a grub crash. start_image returned “not found”…Wtf? For a “simplified” installation, this is resulting quite the PITA.

    EDIT: OMG…figured it out, but holy cow. The installer is rather borked. It demands 600MB for /boot/efi, which at least this, it warns you of. BUT. It will install without warnings a full system and then crap out, if you ignore a very specific requisite not mentioned anywhere during the install! You need at least a 1GB ext4 partition somewhere for /boot. Ignore this, and you’re crapped.