#Default transcode config: No hardware acceleration

1 messages · Page 1 of 1 (latest)

wooden sandal
#

I noticed that after about half an hour of watching I'd start to buffer a lot - after investigating it turned out the server was being thermally throttled and the CPU was at 100%, because the default transcode config was set to "Software (no GPU)". I changed it to "Video Acceleration API (VA-API) (Best Effort)", which I think is right for my N100 docker setup on the vaapi image? "Intel QuickSync (Best Effort)" was also an option.

Anyways - I had my friend who's running the Windows build on a system with a dedicated Nvidia GPU check, and their default transcode config was also set to "Software (no GPU)". Is that the default value on purpose? We are both on 0.19.3. They changed to "nvidia (cuda)".

latent cedar
#

it's the default on purpose for no reason other than Tunarr not making an assumption / proactively setting the right one based on what hardware it sees is available. probably some room for improvement here

wooden sandal
#

I'd seen this part of the System Health before, and assumed it meant hardware acceleration was being used - might be an improvement if it gave a warning about acceleration being turned off, with a link to the default transcode config page, as an idea?

image.png
latent cedar
#

Yea I like that. That was originally meant to warn if your provided ffmpeg did not have any hw accel libs built in (which is only relevant for certain install types too). I think we can be more precise in that check or maybe split it into multiple separate checks

#

I think I gotta also get the health checks visible on the onboarding page

#

Can ofc take it a step further with health checks and attempting to do the same for non container deploys

wooden sandal
#

Yay! I'd imagine a very decent chunk of people are out there not realizing they're doing software transcoding - it would have taken me way longer to notice if not for the thermal throttling

If showing health checks during onboarding, it may also be worth looking into that ffmpeg version warning, which I now understand is normal and expected for docker users - if only to avoid a lot more support requests

latent cedar
#

Yea solving those 2 things would eliminate a whole class of support tickets I get frequently

#

Really hoping I can find some contributors! I will eventually get to all of this but it’s a butt load of work haha

wooden sandal
#

You're an absolute champ for what you've managed to do by yourself so far, though 😎