Yesterday, 01:31 PM
(This post was last modified: Yesterday, 01:32 PM by ArneR. Edited 1 time in total.)
I... I'm a bit confused by this last answer, I was the one suggesting buying an A310/A380 over the B580. And I'm the same one that commented on the relative performance on your iGPU. There are not more than one of us (me).
The point still stands:
The B580 is not better than the A310.
An A310 is better than the UHD770.
A UHD770 is probably more than enough for your usecase, especially if you limit the bitrate/resolution some.
Why don't you just test and see for yourself where the limits of the iGPU lies? But I think you will find that the issue lies in space constraints in the /transcodes folder by running multiple 4K streams at full bitrate at the same time. I'd suggest to enable throttling of transcodes and consequently deleting of old segments to save space.
I transcode to a temporary directory created in RAM on my server since I have so much of it, and after some testing I found that throttling after three minutes and deleting segments 5 minutes after they have been played works fine for me, I also have allocated 30GiB of RAM for this directory, since a single 4K HDR movie can use quite a lot unless throttled etc.
Open three tabs in a browser to your jellyfin server, and start playback of the same 4K movie in all tabs. What happens? Do they all play nice? If so, open another tab and start another. My guess is that it will crash at some point in time, but then at least you know the limits.
Your cpu should have no issues transcoding audio for your household.
The point still stands:
The B580 is not better than the A310.
An A310 is better than the UHD770.
A UHD770 is probably more than enough for your usecase, especially if you limit the bitrate/resolution some.
Why don't you just test and see for yourself where the limits of the iGPU lies? But I think you will find that the issue lies in space constraints in the /transcodes folder by running multiple 4K streams at full bitrate at the same time. I'd suggest to enable throttling of transcodes and consequently deleting of old segments to save space.
I transcode to a temporary directory created in RAM on my server since I have so much of it, and after some testing I found that throttling after three minutes and deleting segments 5 minutes after they have been played works fine for me, I also have allocated 30GiB of RAM for this directory, since a single 4K HDR movie can use quite a lot unless throttled etc.
Open three tabs in a browser to your jellyfin server, and start playback of the same 4K movie in all tabs. What happens? Do they all play nice? If so, open another tab and start another. My guess is that it will crash at some point in time, but then at least you know the limits.
Your cpu should have no issues transcoding audio for your household.