You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After enabling the debugging, I saw [INFO] level information relayed during in-progress crf-search which I found quite useful and helpful and would like to see it relayed in an optimal way during normal progress.
The debug info in scope:
[2024-09-04T23:12:21Z INFO ab_av1::command::sample_encode] encoding sample 10/16 crf 18
Desired in-progress extra info: encoding sample 10/16 crf 18
It is useful to see how many samples were generated, in my case I use just --sample-every.
It is useful to see the sample progress (10/16) for a given crf value, sort of like a secondary progress indicator.
The text was updated successfully, but these errors were encountered:
Yes I think this would be useful. You can see this info already using ab-av1 sample-encode, crf-search and auto-encode are built on top and didn't have quite as easy access to the info relevant to the sample-encode bit. But it is possible for that to be shared and to add simple info to the other higher level commands.
After enabling the debugging, I saw
[INFO]
level information relayed during in-progresscrf-search
which I found quite useful and helpful and would like to see it relayed in an optimal way during normal progress.The debug info in scope:
[2024-09-04T23:12:21Z INFO ab_av1::command::sample_encode] encoding sample 10/16 crf 18
Desired in-progress extra info:
encoding sample 10/16 crf 18
--sample-every
.10/16
) for a givencrf
value, sort of like a secondary progress indicator.The text was updated successfully, but these errors were encountered: