2023-09-08, 01:08 PM
I've noticed that with VAAPI HWA, the CRF settings don't do anything.
I have tried setting the CRF settings to the lowest and highest quality and comparing the final transcode, but both transcodes with VAAPI just look the same.
It only ever worked with software transcoding for me.
Ideally, you want to watch your content as close to the original source's quality. When transcoding, you're just re-encoding the content. Each time a video file is re-encoded, more information is lost. But since transcoding doesn't replace the original file, this is fine.
Your goal would be to set CRF values that would produce a transcode around the same quality as the source. The values depend on a lot of factors, like the quality/efficiency of the encoder, the video file in question, and how powerful your hardware is.
There is no point in using up more hardware utilization and temp disk space to create a bloated transcode so that no quality is lost during the transcode. As in, after a point, really low CRF values keep using up a lot of space and power just to get ever-so-close to the original quality of the source video. You can't create a better looking video by increasing CRF values. Your limit is the original source.
Most people set their CRF values around 20-16.
I have tried setting the CRF settings to the lowest and highest quality and comparing the final transcode, but both transcodes with VAAPI just look the same.
It only ever worked with software transcoding for me.
Ideally, you want to watch your content as close to the original source's quality. When transcoding, you're just re-encoding the content. Each time a video file is re-encoded, more information is lost. But since transcoding doesn't replace the original file, this is fine.
Your goal would be to set CRF values that would produce a transcode around the same quality as the source. The values depend on a lot of factors, like the quality/efficiency of the encoder, the video file in question, and how powerful your hardware is.
There is no point in using up more hardware utilization and temp disk space to create a bloated transcode so that no quality is lost during the transcode. As in, after a point, really low CRF values keep using up a lot of space and power just to get ever-so-close to the original quality of the source video. You can't create a better looking video by increasing CRF values. Your limit is the original source.
Most people set their CRF values around 20-16.