My experience is it doesn’t work with all distros. Works fine with popos (what I am using).
@here
I have noticed a steep drop off on encoding performance in the last few weeks with my arc gpus. I was seeing average 100 to 200fps initially. Now everything I do is 50 or less. I am wondering if intel released a driver that broke it. Or windows update that broke it. Either way it is not the speedy option anymore. I mean it still is but using more energy than cpu per second and takes 40minutes+ to encode one episode.
Sorry, can not really help with that since I do neither use Windows for this nor the Windows Intel drivers. As for Linux the i915 driver that Intel uses is still wonky and crashes the encoding often in 4k and the new intel xe driver is still in beta status and does not work for a lot of things and crashes even when I try to play video.
Figured it out. On boot of windows I noticed intel saying rebar was not enabled. I checked bios it is enabled. Anyways I updated the bios and now all is good. 200+ fps.
Seems to be a bios issue and reflashing the same bios fixed it.
Interesting.
Update to Truenas app working with tdarr and intel arc. Seems to be working now. Not sure if they updated the app. But it is functioning as intended.
@here
What is this tdarr exactly, what is it used for? I heard it being mentioned several times now. Explain like I have no idea please, because I have not.
It’s a wrapper around ffmpeg with the ability to do distributed encoding. You set up a tdarr server, and one or more nodes.
It is a webgui for handbrake and ffmpeg.
output arguments: -map 0 -pix_fmt p010le -c:v av1_qsv -preset 1 -global_quality:v 20 -mapping_family 1 -ac 6 -c:a:0 libopus -metadata:s:a:0 language='eng' -c:s copy -map_chapters 0
Thank you, that looks useful. I will put at on the list of things I need to do.
Does it do vbr av1 via intel arc yet?
If not then its kind of useless to me
I will look, but i know crf is a form of vbr, but based on quality you seek. It will give more or less depending on scene by scene basis and so a variable bitrate. Like a darker scene might use less bitrate and more detailed scene has more bitrate, it also can lead to inconsistent uniformity with file size. Like one show might need a lot more bit rate to be crf 20 but something like person of interest requires less. So for instance fringe might be 2 to 3GB per episode with crf 16 and poi might be 1 to 2GB.
CRF is constant quality metric. Meaning to keep each scene constant in quality each scene might require more or less bitrate to achieve the quality metric.
ffmpeg -h encoder=av1_qsv might give you info you are looking for.
https://ffmpeg.org/ffmpeg-codecs.html#QSV-Encoders
https://trac.ffmpeg.org/wiki/Hardware/QuickSync
here is some documentation. Might support vbr.
Handbrake might also be what you are looking for. It supports av1 qsv and tdarr.
Crf would be really nice. Ill take a look when im home