[FFmpeg-trac] #9336(undetermined:new): -cpu-used 9 does not work with libaom's realtime mode

[FFmpeg]

#9336: -cpu-used 9 does not work with libaom's realtime mode
-------------------------------------+-------------------------------------
             Reporter:  veikk0       |                    Owner:  (none)
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  git-master   |               Resolution:
             Keywords:  libaom       |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Comment (by veikk0):

 Within libaom, cpu-used values higher than 6 are just mapped to 6 in the
 "good" usage mode (with the exception of 10, which seems to fail with an
 out of range error, at least when I try it with aomenc... so it's not
 consistent even within libaom itself).

 If someone wants to implement and maintain the logic of the allowed values
 (which have changed over time with the various libaom versions, so
 compatibility would also need to be considered), then sure, I guess
 warnings could be a thing on FFmpeg's side. I don't see that as the best
 idea, seeing as this issue has been open for a while. It'd be less effort
 to just pass the value to libaom and let it handle things rather than
 building a lot of logic for working around libaom's quirks.

 There's also the "allintra" usage mode, which I have no experience with
 and thus have no idea if it has its own allowed value range or mappings.
 So if additional messages/limitations were implemented, that would also
 need to be looked into.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/9336#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker