2023-10-17, 01:11 PM
A RAM disk is only suggested if you don't have an SSD in your system. Or, if you're like me, have an ooooold SATA2 SSD with pretty slow write speeds.
If you have straight off the disc 4K HDR, 50-70Mbps, 50-75GB in size, your transcodes are going to be about that big or larger. You have to do a lot of testing to see how your system handles those transcodes. Monitor how big the transcode directory becomes.
The general wisdom with 4K HDR media is to keep it in a separate library. Pre-transcode your 4K HDR to 1080P SDR and put that 1080P copy in your main library. And for your clients/users with 4K HDR capable setups they can go to the 4K library and not have to transcode.
If you have straight off the disc 4K HDR, 50-70Mbps, 50-75GB in size, your transcodes are going to be about that big or larger. You have to do a lot of testing to see how your system handles those transcodes. Monitor how big the transcode directory becomes.
The general wisdom with 4K HDR media is to keep it in a separate library. Pre-transcode your 4K HDR to 1080P SDR and put that 1080P copy in your main library. And for your clients/users with 4K HDR capable setups they can go to the 4K library and not have to transcode.
Jellyfin 10.10.3 (Docker)
Ubuntu 24.04 LTS
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
![[Image: GitHub%20Sponsors-grey?logo=github]](https://img.shields.io/badge/GitHub%20Sponsors-grey?logo=github)
Ubuntu 24.04 LTS
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)