2024-12-03, 02:28 AM
(This post was last modified: 2024-12-03, 02:09 PM by TheDreadPirate. Edited 2 times in total.)
I missed that you had some new posts since my last one. I'm still semi-automated since I'm altering based on what type of media as well as age. The easier media are seasons or shows where you expect a level of consistency.
I don't know what these do so I haven't played with them. I also don't see the -bf parameter in the av1_qsv encoder help. I guess -bf is to set the number of b-frames? I don't really understand what that means.
I don't think so. On the decode side (i.e., option comes before before the file), this would throw extra frames on the device on the front-end. What the advantage is I'm not sure. Possibly faster decoding? The video filter portion (i.e., option after the input file) is for encoding. Based on what you have there, I wonder if look_ahead_depth should match the number of extra frames uploaded to the hw device in my own code...
Code:
-adaptive_i 1 \ # new
-adaptive_b 1 \ #new
-b_strategy 1 \ #new
-bf 39 \ #new
I don't know what these do so I haven't played with them. I also don't see the -bf parameter in the av1_qsv encoder help. I guess -bf is to set the number of b-frames? I don't really understand what that means.
Quote:-extra_hw_frames 40 \ # new to me. the same as -filter:v:0 "hwupload=extra_hw_frames=64 in your command???
I don't think so. On the decode side (i.e., option comes before before the file), this would throw extra frames on the device on the front-end. What the advantage is I'm not sure. Possibly faster decoding? The video filter portion (i.e., option after the input file) is for encoding. Based on what you have there, I wonder if look_ahead_depth should match the number of extra frames uploaded to the hw device in my own code...
Jellyfin 10.10.0 LSIO Docker | Ubuntu 24.04 LTS | i7-13700K | Arc A380 6 GB | 64 GB RAM | 79 TB Storage