Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace vpx with more specific vp8/vp9 tags #6455

Open
3 of 4 tasks
GodTamIt opened this issue Aug 20, 2021 · 4 comments
Open
3 of 4 tasks

Replace vpx with more specific vp8/vp9 tags #6455

GodTamIt opened this issue Aug 20, 2021 · 4 comments
Labels
confirmed This issue has been reviewed and confirmed
Projects

Comments

@GodTamIt
Copy link
Contributor

GodTamIt commented Aug 20, 2021

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
@Bond-009
Copy link
Member

Is this still an issue?

@jellyfin-bot jellyfin-bot added this to Needs triage in Issue Triage for Main Repo Mar 29, 2023
@GodTamIt
Copy link
Contributor Author

I'll need to check on the last checkpoint. We could remove vpx compatibility now that all clients have been migrated.

@Bond-009 Bond-009 removed this from Needs triage in Issue Triage for Main Repo May 22, 2023
@Bond-009 Bond-009 added this to To do in Cleanup via automation May 22, 2023
@jellyfin-bot
Copy link

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.

@jellyfin-bot jellyfin-bot added the stale Stale and will be closed if no activity occurs label Oct 9, 2023
@jellyfin-bot
Copy link

This issue was closed due to inactivity.

@jellyfin-bot jellyfin-bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 30, 2023
Cleanup automation moved this from To do to Done Oct 30, 2023
@Bond-009 Bond-009 reopened this Nov 14, 2023
Cleanup automation moved this from Done to In progress Nov 14, 2023
@Bond-009 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
confirmed This issue has been reviewed and confirmed
Projects
Cleanup
  
In progress
Archived in project
Development

No branches or pull requests

3 participants