WiMP / Tidal support about mopidy HOT 29 CLOSED

I would love this! Especially if both spotify and wimp backends can be used at the same time for search and playback.

from mopidy.

Two years later, and there is still no public API from WiMP. According to https://www.facebook.com/wimpnorge/posts/516006585091493 from August 2012 interested parties may contact them about API access.

I have my doubts about WiMP giving an open source project access to their non-public API, but it would be cool to hear their thoughts anyway. Anyone up for contacting them and potentially work on a WiMP backend?

from mopidy.

If anyone contacts WiMP and gets a positive response, please reopen this issue. Until then, WiMP in Mopidy isn't going to happen.

from mopidy.

Well, I open this up now and will try to report back when I get an answer. Just contacted wimp per mail so now I just cross my fingers :)

from mopidy.

Have you heard anything back from WIMP?

from mopidy.

Still no response from them, I'll try again today :)

from mopidy.

Closing this again, feel free to reopen if they ever reply :-)

from mopidy.

I'll just add that someone over at the XBMC forums managed to get an answer from WiMP and I guess it doesn't bode well for WiMP support in Mopidy.

from mopidy.

You can use this API https://github.com/oleander/wimp-rb
It uses thrift, so Python code can be generated.

from mopidy.

Takoi over at the xbmc forum built a WiMP Plugin for XBMC (http://forum.xbmc.org/showthread.php?tid=200555) with the help of oleander's API. So, it can be done and it would be really nice to have in mopidy!

from mopidy.

Actually working lib here: https://github.com/tamland/wimpy Uses rest api, not thrift. Requires rtmp support for playback.

from mopidy.

@tamland What do you mean "actually"? Mine works just fine.

from mopidy.

@oleander Sorry, I meant as in being python an usable for mopidy as is. Streaming is not implemented and doesn't work with basic accounts either.

from mopidy.

I take it no one has worked to getting TIDAL support yet? There is a fully working KODI add-on already created and working, so their API works, and people have figured it out. If I can get mopidy to work in openwrt I can try and take a crack at it with my zero-to-nil programming abilities...

from mopidy.

if you are still interested in Tidal integration I've written a plugin...
It is my first attempt at writing python code and mopidy plugin so feel free to improve it if needed!!
The plugin uses tamland's api to interact with Tidal, thank you @tamland
Repo here

from mopidy.

Since there is apparently an API available, shouldn't this request be reopened?

from mopidy.

@landroni: Since this would be handled by a Mopidy extension, no reason to open an issue for that in Mopidy itself.

from mopidy.

What @tkem said, and the extension already exists: https://github.com/mones88/mopidy-tidal

from mopidy.

Oh, thank you, I wasn't aware of this.

I actually had a similar request for Qobuz support... Is there an extension for this as well? Should I open a separate ticket for this?

from mopidy.

In general, there is no point opening new issues for extensions you'd like to see as there is nothing actionable in Mopidy. The APIs exist, someone just needs to come along and make use of them.

EDIT: no point

from mopidy.

@landroni: Such questions should better be placed on Mopidy's discussion forum: https://discuss.mopidy.com/.
Even we don't know all extensions that exist out there, or are in development..

from mopidy.

Will Mopidy-tidal become an official plugin? If my company wanted to help contribute to mopidy development of Qobuz plugin what is best way to do that?

from mopidy.

@shawaj: Please post general questions to http://discuss.mopidy.org.
@jodal: Should we lock conversations on this issue (and maybe other extensions related core issues, too?)

from mopidy.

@tkem - the questions aren't general questions. They relate to this thread. Can you not just answer here? Or maybe via email

from mopidy.

@shawaj: This thread was closed, because this is not a Mopidy core issue. Tidal-specific questions should be placed on mopidy-tidal's issue tracker, where people involved with Mopidy-Tidal will see it. As for Qobuz, there's already a thread here: https://discuss.mopidy.com/t/qobuz-backend-plugin-for-mopidy/1145

from mopidy.

Ok sorry, didn't mean to annoy you or anything but just wanted to know if
this would be pulled into mopidy as an official plugin or not?

What makes the difference between an unofficial plugin and am officially
supported one under the mopidy repos?

Thanks again

On 3 Sep 2016 12:49 pm, "Thomas Kemmer" [email protected] wrote:

@shawaj https://github.com/shawaj: This thread was closed, because this
is not a Mopidy core issue. Tidal-specific questions should be placed on
mopidy-tidal's issue tracker, where people involved with Mopidy-Tidal will
see it. As for Qobuz, there's already a thread here:
https://discuss.mopidy.com/t/qobuz-backend-plugin-for-mopidy/1145

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#48 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADNCuoQFG3EY4jJ7bw7MvhhEgkFOvN_Tks5qmV7fgaJpZM4AP9h9
.

from mopidy.

@shawaj: No offense meant, we're just trying to keep people from commenting on closed issues that nobody will look at any more ;-)
Posting on discuss.mopidy.com might also attract the attention of "third-party" extension developers which are not members of the mopidy org.
Extensions in the mopidy repos are generally maintained by Mopidy's core developers. Sometimes extensions which have been abandoned by their original maintainers are also moved here (look for "Maintainer Wanted" signs). Whether this makes them more "official" than others I don't know.

from mopidy.

Cool :-) thanks so much.

Do you accept contributions from developers employed by companies just to
do this?

As we're looking to put a full time developer on supporting existing open
source projects and creating new ones in the SBC and audio space
(predominantly to support projects we're working on - by way of full
transparency)... and possibly more devs as our company expands (we're a
hardware company and we rely on a lot of open source software so keen to
give back!)

Mopidy/PiMusicBox is one we love and use every day and are building
products around so want to help grow it - for us and for everyone :-)

On 3 Sep 2016 6:08 pm, "Thomas Kemmer" [email protected] wrote:

@shawaj https://github.com/shawaj: No offense meant, we're just trying
to keep people from commenting on closed issues that nobody will look at
any more ;-)
Posting on discuss.mopidy.com might also attract the attention of
"third-party" extension developers which are not members of the mopidy org.
Extensions in the mopidy repos are generally maintained by Mopidy's core
developers. Sometimes extensions which have been abandoned by their
original maintainers are also moved here (look for "Maintainer Wanted"
signs). Whether this makes them more "official" than others I don't know.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#48 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADNCuuJ0oBL8nAQ9NBAd4akUmL1yne-qks5qmampgaJpZM4AP9h9
.

from mopidy.

I don't think there'll be any objections to contribution from people who get actually paid for working on Mopidy, but I guesz @jodal and/or @adamcik should have the final word on that.
However, as I anticipated, this discussion should be continued on discuss.mopidy.org!!!

from mopidy.