Introducing NewPlayer
Dear NewPipers, I give to you the fruit of my labor for the last three months that I worked for the [NewPipe Association](https://newpipe-ev.de): NewPipe's (hopefully) next player: NewPlayer. But let's start from the beginning. NewPipe's current player implementation isn't very good. Its code is ugly, and it is based on the outdated ExoPlayer 2. So because of the ongoing refactoring process, I decided to rewrite the player and tackle the pain points we currently have with it. <p align="center"> <img src="https://github.com/user-attachments/assets/d631a306-7d0a-49c8-839f-d2d4551e409f"> </p> <h2 align="center"><b>NewPlayer</b></h3> <h3 align="center">NewPipe's next media player framework</h3> <br> <br> <i>Icon by <a href="https://jaim3.com">Jaime López</a></i> <br> ### So what is NewPlayer then? NewPlayer is a media framework independent of NewPipe itself. I decided to make it independent, because one of the big issues we have with the current player is that it is deeply integrated into NewPipe. Therefore, I wanted to make NewPlayer a separate module in order to enforce that the interface between NewPipe and the player is only as big as necessary. This also has the advantage that NewPlayer can be used independently of NewPipe itself, which means it can be used in other apps too. ### Let me give you a Profile about NewPlayer: - It is a module, separate from NewPipe and can be used as an independent player framework - It is based on the [Media3](https://developer.androi
Posted by theScrabi on Oct 8, 2024, 1:59 PM
Tags
Related issues
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
github (E-commerce)
proposal: cmd/cgo: cgo without a C toolchain
Replace PowerToys Run with Command Palette
VPS with a vRack leg
Possibility of Portal 1 Code Inclusion
Introducing NewPlayer
Metrics for PRs are never expiring ("memory leak")
ship even more of the compiler in source form
Flatpak Application TRACKING ISSUE
Introducing NewPlayer
Dear NewPipers, I give to you the fruit of my labor for the last three months that I worked for the [NewPipe Association](https://newpipe-ev.de): NewPipe's (hopefully) next player: NewPlayer. But let's start from the beginning. NewPipe's current player implementation isn't very good. Its code is ugly, and it is based on the outdated ExoPlayer 2. So because of the ongoing refactoring process, I decided to rewrite the player and tackle the pain points we currently have with it. <p align="center"> <img src="https://github.com/user-attachments/assets/d631a306-7d0a-49c8-839f-d2d4551e409f"> </p> <h2 align="center"><b>NewPlayer</b></h3> <h3 align="center">NewPipe's next media player framework</h3> <br> <br> <i>Icon by <a href="https://jaim3.com">Jaime López</a></i> <br> ### So what is NewPlayer then? NewPlayer is a media framework independent of NewPipe itself. I decided to make it independent, because one of the big issues we have with the current player is that it is deeply integrated into NewPipe. Therefore, I wanted to make NewPlayer a separate module in order to enforce that the interface between NewPipe and the player is only as big as necessary. This also has the advantage that NewPlayer can be used independently of NewPipe itself, which means it can be used in other apps too. ### Let me give you a Profile about NewPlayer: - It is a module, separate from NewPipe and can be used as an independent player framework - It is based on the [Media3](https://developer.androi
Comments (0)
No comments yet. Start the discussion.