In a transient way I might say rather than constantly. I use Emby and when something is streaming to a Roku in a format that’s not native it ends up using something around 80% of the allocated power. I don’t use the throttling option though so it’s actually working well ahead of the stream and finishes up a full movie in a few minutes rather than going along in realtime.
So yeah it could be heavily mitigated but I’d rather just have it done rather than hoping it’s smart enough plan ahead.
CmdrShepard@lemmy.one 1 year ago
The power is only needed for transcoding. Multiple 4k streams should be little more than directly serving up the files to the client machine (like your TV) which consumes very few resources. You should avoid transcoding 4k down to 1080p or 720p by either avoiding 4k content, grabbing only stuff that is directly compatible, or having duplicate copies of stuff in 4k and 1080p so that the 1080p file gets transcoded if needed. Many of us have separate 4k libraries on our servers to prevent any possibility of transcoding it (like for remote streams when you don’t have the upload speed to stream 4k directly).
cwagner@lemmy.cwagner.me 1 year ago
CmdrShepard@lemmy.one 1 year ago
That was just an example of when you might need to transcode multiple streams at once. Typically you shouldn’t need to transcode anything especially if you’re just watching at home. In that case you can have dozens of streams in any resolution running at once without the computer sweating at all.