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
Currently, vpx is being sent by clients to refer to the VP8/VP9 codecs ambiguously when indicating transcoding jobs. Separate them out so that it specifies the exact codec.
Additionally, the server does not properly support transcoding to VP9 via libvpx-vp9, as it does not disambiguate between the two codecs and instead, falls back on VP8.
Steps
Migrate the server to accept vp8 and vp9 in addition to vpx
Properly support VP9 transcoding for ffmpeg in the server
Migrate clients to send vp8 and vp9 instead of vpx
Deprecate vpx and perhaps remove backwards compatibility once clients are all migrated
The text was updated successfully, but these errors were encountered:
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.
Bond-009
added
confirmed
This issue has been reviewed and confirmed
and removed
stale
Stale and will be closed if no activity occurs
labels
Nov 14, 2023
Currently,
vpx
is being sent by clients to refer to the VP8/VP9 codecs ambiguously when indicating transcoding jobs. Separate them out so that it specifies the exact codec.Additionally, the server does not properly support transcoding to VP9 via
libvpx-vp9
, as it does not disambiguate between the two codecs and instead, falls back on VP8.Steps
vp8
andvp9
in addition tovpx
vp8
andvp9
instead ofvpx
vpx
and perhaps remove backwards compatibility once clients are all migratedThe text was updated successfully, but these errors were encountered: