Replies: 2 comments 8 replies
-
|
This likely would be out of scope, but proposing for sake of discussion (potentially this suggestion needs to be moved into #364 or be it's own discussion):
Within the context of #364 where the desire is to set a "playback sink", I wonder if it would be instead more simple to create a sort of "navidrome satellite" which would be a copy of this web player paired up with something like mpv (with its |
Beta Was this translation helpful? Give feedback.
-
|
If we go this route I'd be happy to split out the mpv player component for Supersonic into its own repo so it can be used as a base for this. (It dynamically links against libmpv.) But maybe a different/better(?) idea is to implement DLNA and/or Chromecast as a sink so the Navidrome web UI can cast to existing smart speakers, Chromecast devices, etc, and leverage existing projects like this for the Raspberry PI case. |
Beta Was this translation helpful? Give feedback.
-
|
It's highly preferential, but I'd vote to prioritize simpler playback (with exclusive for sample rate switching) above integration with smart devices. This would allow all peripheral speakers to be utilized rather than a specific ecosystem. |
Beta Was this translation helpful? Give feedback.
-
|
Were you envisioning the "Navidrome satellite" being deployed on different hardware than the Navidrome server? It's definitely a cool idea but I think it would have to advertise itself on the LAN so the server and/or device running the web client can be aware of its existence, at which point you're basically re-inventing uPnP/DLNA, which is why I'd mentioned the idea of using an existing standard. Jukebox mode is certainly the easiest path forward, with the remote playback node being part of the server itself (and you'd need to deploy the server on the same device connected to your audio system) Hmm though I guess you could have the remote playback node be configured with the server's connection details, and have an always-open connection to the server, and the server could then relay control messages from the web client. |
Beta Was this translation helpful? Give feedback.
-
Yes, so it's a bit more/different than #364 in its current form.
Instead of it being a "sink" like uPnP/DLNA, I'd thought of it more as a slim client that just pulls the common portions from the navidrome codebase so you have a similar look and feel. Instead of playing to the browser though it would play to some locally configured playback device (I'd assume default to mpv). This would be to hit the "headless playback" use cases that the community of people using mpd where they typically want to play via an external DAC and play "bit perfect" (e.g. switching sample rate, PCM, DSD).
Maybe it's simpler to do something like this where instead of trying to be compliant with uPnP/DLNA you just make a small mpv+shim that can be deployed someplace and registered as a player with the navidrome server. The main goal in my suggestion is:
|
Beta Was this translation helpful? Give feedback.
-
|
You guys are the best. I found a couple of Raspberry Pi Zeroes on my desk and I was wondering if there was something out there like this. Google brought me to a 2-year-old Reddit thread, which brought me to an already-closed issue about Jukebox mode, which brought me here :) I would love to have something that would run on my RPi Zeroes that would:
It could even pull the web app from some Navidrome-adjacent location so that I never have to touch the RPis again. @andrewgdunn, I think we're almost describing the same thing. Basically, I want somebody (a guest in my house, perhaps) to be able to pick up a tablet that I have on my coffee table, open the PWA for this web client, and be able to play music on my stereo by way of the RPiZero where this client is running. I think this is a bit beyond the scope of the new web-player component discussion though :) |
Beta Was this translation helpful? Give feedback.
-
|
Would this player suit the bill (mostly)? https://cookpete.com/react-player/ |
Beta Was this translation helpful? Give feedback.
-
|
I tested https://coderadio-admin-v2.freecodecamp.org/listen/coderadio/radio.mp3 and did not show the title |
Beta Was this translation helpful? Give feedback.
-
|
That's because it's playing straight in your browser. ;-) Check the test things on that page, or even better, read the GitHub link at the bottom to learn how to use it. |
Beta Was this translation helpful? Give feedback.
-
|
You seem to suggest that after reading the link and not playing music straight in the browser, it will be able to show its title and address item 2.6. Given this is meant to replace Navidrome's player, where should I load this player if not in a browser? |
Beta Was this translation helpful? Give feedback.
-
Navidrome Web Player Requirements
Introduction
In light of the deprecation of the React Music Player, it has become necessary to find a new solution for Navidrome's music player. This requirements document aims to outline the essential components needed for developing a new web player that will address long-standing issues and provide better overall functionality. The new player should be built on a React/Material-UI framework, compatible with most browsers and media formats, and easily extensible.
1. Background
Navidrome is currently using its own fork of the React Music Player with a couple of bug fixes applied to it. The decision has been made to develop a new player to better suit the needs of the project. Some previous discussions about this can be found on our Discord (ex: https://discord.com/channels/671335427726114836/704303730660737113/861006516315881522)
2. Requirements
The new music player should meet the following criteria:
2.1. Written in React/Material-UI
The player must be developed using the React/Material-UI framework to seamlessly blend into Navidrome's existing UI and support theming.
2.2. Browser and Format Compatibility
The player must be compatible with most, if not all, browsers and support the main media formats. It should be based on the HTML5 Media Player.
2.3. Gapless Playback
The player must support gapless playback, as described in issue #745.
2.4. Normalization/ReplayGain Support
The player must include normalization and ReplayGain support, as discussed in issue #233.
2.5. Remote API Control
The player must have the capability to control the remote API for Jukebox, as described in issue #364.
2.6. Internet Radio Integration
The player should integrate well with the Internet Radio feature, displaying the current song being played if the information is available.
2.7. Extensibility
The player's UI should be easy to extend, allowing for the addition of more options in the future.
2.8. Internationalization
The player must support internationalization, allowing for translations and localization to cater to users from different regions and languages.
2.9. Accessibility
The player should be designed with accessibility in mind, ensuring that it is usable by individuals with disabilities.
2.8. Separation as an Independent Project
The player may be developed as a separate project, if necessary.
3. Implementation Details
The initial idea is to create a React player using the useAudioPlayer library, which allows the specification of an audio provider. This would enable an HTML5 audio provider for playback in the browser and a remote audio provider for controlling the Jukebox. However, it is unclear if the useAudioPlayer library supports gapless playback. If not, a workaround could involve creating a new provider that wraps the Stitches library.
4. Conclusion
This requirements document outlines the necessary components for the development of a new Navidrome music player. The player should be built using the React/Material-UI framework and be compatible with most browsers and media formats. It must support gapless playback, normalization, ReplayGain, remote API control, Internet Radio integration, extensibility, accessibility, and internationalization. Implementation using the useAudioPlayer library is proposed, with a potential workaround for gapless playback using the Stitches library if needed.
Beta Was this translation helpful? Give feedback.
All reactions