Closed carrieroent closed 1 year ago
Thank you, but I am going to leave the name. I do not want people to think I am associated with Qobuz and the player can potentially support other services so it may not always be just a Qobuz-based application.
hifi is short for "high fidelity". It's to highlight the high resolution capabilities of the player.
Sorry if I'm being rude, but I think it would be best if this were broken down into the following parts:
It pretty much already exists in that form.
qobuz-api
is what you're calling libqobuz
. The TUI and the CLI are just in the same codebase. I don't see a need toe split those at this point.
librespot
is more than just an api client as it provides audio playback functionality as well.
qobuz-api is what you're calling libqobuz. The TUI and the CLI are just in the same codebase. I don't see a need toe split those at this point.
Yes, but split these to separate repositories is better experience for library users. However, you're right that perhaps at this point there is no need to do this yet.
librespot is more than just an api client as it provides audio playback functionality as well.
Of course we should bring the corresponding features to here. Don't we support playback?
And I still think there is a demand for a dedicated Qobuz CLI client. Bringing Qobuz support to CLI, general music players is pretty trivial once we have the library.
Of course we should bring the corresponding features to here. Don't we support playback?
Yes. That is my point. This already does a lot of things you're asking about.
Just a suggestion, rename this to qobuz-tui or other qobuz-something. It would be easier to remember. What is the purpose of hifi-rs (hifi rust?)?