05-05-2020, 12:45 PM
I've already pushed a PR to Tim's repo with a revised build-from-sources recipe for upmpdcli 1.4.7.
Don't hold your breath that this will be the answer to a maiden's prayer. It does include lots of bug fixes, refactoring, and even a few new features, for example a Spotify plugin (which I haven't explored yet).
The Tidal plugin is working fine.
The Qobuz plugin however is effectively dead, not because of any versioning issue of upmpdcli but because of Qobuz's actions. Right from the home page of JFD's upmpdcli website is this news from last fall:
I won't repeat all the other words Francois has to say about the situation, you can read his docs for yourself.
It isn't clear to me what will happen to the Google Music plugin with time either, especially with Google consistently saying it will retire Google Music in favor of YouTube Music.
Regards,
Kent
Don't hold your breath that this will be the answer to a maiden's prayer. It does include lots of bug fixes, refactoring, and even a few new features, for example a Spotify plugin (which I haven't explored yet).
The Tidal plugin is working fine.
The Qobuz plugin however is effectively dead, not because of any versioning issue of upmpdcli but because of Qobuz's actions. Right from the home page of JFD's upmpdcli website is this news from last fall:
Quote:2019-10-06
Qobuz access was revoked: If you were using Qobuz and it's not working any more, don't pull your hair, the Qobuz plugin stopped working (either through the Media Server or with OHCredentials). Qobuz revoked the app_id, and also deleted the API documentation on Github. If you are a hardware integrator/manufacturer using upmpdcli to support Qobuz access (I know there are some), I made a modification to the Qobuz plugin so that the app_id/secret can be stored externally instead of being embedded in the source. This means that, if you can convince Qobuz to supply you with the appropriate pair, you can easily restore function, without having to support a modified module. Of course, this supposes that the API itself does not change.
I won't repeat all the other words Francois has to say about the situation, you can read his docs for yourself.
It isn't clear to me what will happen to the Google Music plugin with time either, especially with Google consistently saying it will retire Google Music in favor of YouTube Music.
Regards,
Kent
