TheDreadPirate dateline='[url=tel:1699468100' Wrote: 1699468100[/url]']
If you aren't transcoding or tone mapping, you are going to be disk IO or bandwidth limited before anything.
4K isn't the problem. It's tone mapping HDR. Because of how computationally expensive tone mapping is compared to just transcoding, the suggested setup is to have 4K HDR content in a separate library and pre-transcode and tone map your 4K HDR to 1080P SDR to use in your main library. If your setup supports 4K HDR, the content is there and no transcoding or tone mapping is necessary. If a user's setup doesn't support 4K HDR, having the 4K content in a separate library prevents a user from accidentally forgetting to switch which version they are watching.
In terms of just transcoding, the RTX 5000 should easily support 7 users. You MIGHT be able to support 7 tone mapped streams as well, if you don't want to pre-transcode and tone map your 4K library. The Intel Arc A380 can do 5 and it is my understanding that the 6GB of memory is the limitation. So having 16GB on your card should enable more tone mapped transcodes.
Thank you, that's really helpful to know. I completely forgot about HDR but luckily all of the 4k endpoints do support 4k HDR although some are just standard HLG while others have HDR 10, 10+ and Dolby Vision. Would this make a difference to the tone mapping side of things?
Thanks!
toytown dateline='[url=tel:1699470150' Wrote: 1699470150[/url]']
The Arc380 can certainly do 7x 2160p>2160p HDR>SDR and 10x 2160p>1080p HDR>SDR (preset SLOW) transcodes to H264. So if you don't anticipate any more clients than this, i wouldn't bother splitting your library and having different resolutions.
That's awesome, thanks!
Do you see any potential bottlenecks in the system that could be fixed with a high spec component, or even somewhere where I've gone overkill so the system could be cheaper?
Thanks you!