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

Media3 #52

Closed
OxygenCobalt opened this issue Oct 27, 2021 · 1 comment
Closed

Media3 #52

OxygenCobalt opened this issue Oct 27, 2021 · 1 comment
Labels
playback Related to music playback rework Requires/Does changes to app architecture

Comments

@OxygenCobalt
Copy link
Owner

OxygenCobalt commented Oct 27, 2021

Google is releasing a new library called media3 that will also become the home of exoplayer eventually. This means I have to migrate much of my internal systems.

Roadmap:

  • [2.X.X] Move over all my exoplayer uses to Media3.
  • [2.X.X] Revamp MediaSessionConnector to use Media3 instead of Media1.
    • Cover loading would become a mess again, as I will likely have to force my async cover loading function to play along with a synchronous getCover call. Why this hasn't become async by default beats me.
  • [2.X.X] Add android auto support using media3. I could do this right now, but I'd rather not have to migrate old media code to the new library.
@OxygenCobalt OxygenCobalt added the rework Requires/Does changes to app architecture label Oct 27, 2021
@OxygenCobalt OxygenCobalt changed the title Media3 migration Media3 Nov 27, 2021
@OxygenCobalt OxygenCobalt added the playback Related to music playback label Mar 8, 2022
@OxygenCobalt
Copy link
Owner Author

Actually, never mind about this for now. Whereas in previous iterations of androidx.media you could sidestep the default behavior and it's insanity, from what I've seen media3 forces you into their busted and inefficient code for "convenience". As if spending 40 hours grokking androidx code to find an undocumented gotcha is "convenient".

All migrating to media3 would do is make Auxio buggier and less functional. I'll keep extending my custom playback engine and only migrate the ExoPlayer portions to media3 in the future.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
playback Related to music playback rework Requires/Does changes to app architecture
Projects
None yet
Development

No branches or pull requests

1 participant