Too busy with life right now. Also it's 10 quid a month for a subscription that I'd need to test whether it works, so it's very unlikely I'll ever do it.

Out of interest does the search function is RompR find music from Qobuz? I can't see any reason why it shoudn't.

The search function of Rompr does return things that you have liked/subscribed in Qobuz. Beyond that, no it does not search the Qobuz catalogue.

If you ever have a spare moment or more, let me know..., I could sponsor your Qobuz membership for a couple of months.

OO, so I have no control over what search results the mopidy extension returns. If it only returns those then that's presumably how it's designed to work, or perhaps it's how qobuz's api works. Some extensions work differently depending if you use rompr's default search or if you enable Advanced Search in Romor and search by artist.

I note there are two different qobuz extensions for mopidy, and they have very different search functions. I wonder if the other one works better?

I noted that there were two Qobuz extensions when I was installing Mopidy and made my selection based on the most recent release date.

I will give the other extension a try and respond back. It will probably be a few days before I do that.

Oh, thanks for the reminder about advanced search. I had forgotten about that Rompr capability.

I've had a little look at this.

It looks as though the other mopidy extension no longer works because Qobuz have closed off their API and won't permit extensions like that to be used. (They've even cancelled KODI, for example). The extension you're using appears to work using a horrible hack along the same lines as mopidy-ytmusic.

I'm not all that interested into putting in effort to support backends that are doing things that might well be in violation of the terms of service.

But like I say, if the extension isn't returning useful search results that's not a RompR problem, all I do is display the stuff the backend returns.

Thank you for looking into that further. Hopefully Qobuz has a change of heart regarding their API access policy but I am not holding my breath on that.

I've taken advantage of Qobuz's month's free trial so I've just made a 2.09 release which has some basic support for Qobuz. You can build you collection from your Qobuz Favourite Albums (check the preferences panel). Adding tracks to the Collection by rating or tagging while they are playing is also working.

On mine, search does return things that are not in my favourite albums, but it's patchy and often only a couple of tracks. It seems like the way the search is implemented in the backend or the API isn't very good. You might try increasing the config values for the backend in mopidy:

qobuz/search_album_count: Maximum number of albums returned in search results. Defaults to 10.
qobuz/search_track_count: Maximum number of tracks returned in search results. Defaults to 10.
qobuz/search_artist_count: Maximum number of artists returned in search results. Defaults to 0.

Also it might be worth going to rompr/?setup and seeing if 'Use Mopidy HTTP Interface for Search' is checked. I don't think that'll make any difference in this case but it might be worth trying it on or off and seeing if it makes a difference (on is the preferred option).

The other thing worth mentioning is that I haven't checked whether qobuz track / album URIs are immutable. If they ever change then anything you add to the collection is going to break at some point, and there's nothing I can do about that.