transcoding

[FSmoker 1]

I have my media encoded in H265, AAC audio, and want to be able to have 1-30 users or more? Would an intel i5 be enough? If not how many users can just an i5 transcode? I’m looking into getting an intel i9 12900H mini PC for my server. But I have a i5 I want to put it on. The server is currently running on a mini pc with an N95 cpu In it. Open to recommendations on a CPU for a server supporting a good amount of users.

[Neminem 1518]

I would guess it depends only on client hardware support of H265 and internet bandwidth. 

If clients do not support H265 you would have to transcode.

 

[FSmoker 1]

I’d have to transcode anyway I believe. Since Emby’s native video codec is h265, I think the audio is the same though. My reason for using h265 is to save storage

[Neminem 1518]

I'm confused now, what are you talking about ?

Ether your clients does not support the codec and  transcode, or they will and direct play.

Most of my clients support this format, and direct play.

[FSmoker 1]

I’m sorry to be confusing. My goal is to put as little strain as possible on my server, and save as much space as possible. I prefer my media into be in 1080p, I have no other preference than that. I do have access to handbrake but I’m not sure what settings to use to format the files for direct play.

[RanmaCanada 494]

If you want to put as little strain as possible on your server then the object should be to ensure all your client devices are Android (preferably a Shield or a 3rd Gen Firecube), as it can direct play everything (HDR and DV is another story). No Apple TV users, no Roku users, and no PC users. An i5 will do the job if it's at least 8th gen, preferably you want 12th gen, but understand that nothing can transcode 30 simultaneous encodes as you will run into array bandwidth issues. Don't misunderstand this and think I am saying you can't stream 30 simultaneous encodes, as streaming (direct playing) is completely different from transcoding. Honestly the N95 would more than enough if every one of your clients could direct play and no transcoding would be necessary, pending of course on connections to users as I've had users get throttled down and Emby transocdes the HEVC stream into H264..frustrating.

[ebr 16169]

5 hours ago, FSmoker said:

AAC audio

Unless it is only 2-channel, that wouldn't be my choice for compatibility.  I'd chose AC3 instead.

[Q-Droid 989]

5 hours ago, FSmoker said:

I’m sorry to be confusing. My goal is to put as little strain as possible on my server, and save as much space as possible. I prefer my media into be in 1080p, I have no other preference than that. I do have access to handbrake but I’m not sure what settings to use to format the files for direct play.

Your target ought to be compatibility. Pick the most commonly supported codes for audio and video across your user base. Shoot for at least 80% or more (nice round number). Then pre-convert your media to those codecs.

You want:
1. lots of users.
2. save space.
3. reduced load.
4. transcoding.

Realistically you can have two of those unless you're prepared to spend lots to build up your hardware and network to support more. All four are a dream. But then you might as well spend the money on storage (cheap) and pre-convert your media.

You didn't mention upstream bandwidth.

Newish Intel CPUs can do the job better than most other gear. Depending on your OS how new could matter. Linux tends to lag behind in support of the latest Intel generation.