2024-02-24, 09:10 AM
(2024-02-23, 01:24 PM)nardisowhat Wrote: I don’t want to hijack this thread but wanted to say that I tried jellyfin 10.8.13 on my M1 Mac mini a few weeks ago. I am trying to move away from Plex and getting a Plex pass for hardware transcoding. Plex macOS App is Apple Silicon native.
Since jellyfin 10.8.13 isn’t Apple Silicon native yet, I have low expectations. 10.9 is supposed to be Apple Silicon native but there’s no info when 10.9 stable is due out. Software transcoding is ok on Jellyfin 10.8.13 for macOS using Rosetta. I do see a lot of high iGPU and CPU usage when transcoding HEVC movies for jellyfin clients that aren’t capable of playing it directly. Also when scanning libraries, it hangs.
I am hoping when 10.9 comes out as Apple Silicon native this will be corrected.
Out of curiosity, last week I picked up a miniPC n100 for $179 last week on Amazon and tried out jellyfin on it in just windows 11 pro and it’s amazing and efficient at hardware transcoding HEVC. I got the miniPC to use proxmox, pfsense, pi-hole but was curious how Jellyfin would operate. Ideally, I will use the miniPC for proxmox, pfsense and pi-hole solely and use Jellyfin on my M1 Mac mini when 10.9 comes out.
I tend to belive that its not an issue with Rosseta since everything other than harware transcoding on HEVC, seems to work fine. I personally did not encounter problem with library scaning(about 3TB library size).
Not like yours, I didn't see iGPU usage for ffmpeg at all(almost 0% at all time), without hardware transcoding CPU usage is like full 800%, and with hardware transcoding on, CPU
usage is around 200%.
So I think the problem now is that I cannot modify the path of ffmpeg via editing the "encoding.xml" in config file, so I cannot confirm if it is the problem the ffmpeg build. Is there a way to change the ffmpeg path in Jellyfin 10.8.13?