[PROBLEM] Qobuz support

[TheOldPresbyope]

Thanks Kent, that's what I had read as well, I just wanted to check. At present, I use Airplay.  As a Qobuz customer, I guess I've nothing to lose by asking them for my own App ID, if they oblige, where should this info be stored and how should it be formatted?

Edit:

I found this file:
/usr/share/upmpdcli/cdplugins/qobuz/api/raw.py

In it, it contains two entries:
self.appid = '<hidden>'  # XBMC
...
s3b = '<hidden>'

Should these entries be edited?

[Sorry for my now deleted reply. Too late, I realized I had taken two reasonable thoughts and mushed them into one unreasonable answer.]

What you are asking about is moOde's current codebase which includes upmpdli v1.2.16. AFAICT what you suggest is correct.

In this version of upmpdcli, these entries are hidden in raw.py. In the current version (v1.4.7), the Session class definition has been changed in session.py in the following way

Code:

FROM

class Session(object):
   def __init__(self):
       self.api = None
       self.user = None

   def login(self, username, password):

TO

class Session(object):
    def __init__(self):
        self.api = None
        self.user = None

    def login(self, username, password, appid, cfvalue):

So the requisite credentials are passed in from outside the upmpdcli code. I haven't looked at the implication for moOde's use of the new code.

Regards,
Kent

PS - Yes, moOde is behind the current release but apparently it's not a drop-in replacement and will need developer time to make changes mutatis mutandis and test the result.