mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #552] librespot like for Tidal Connect? #349
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#349
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @lealoureiro on GitHub (Dec 17, 2020).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/552
Does somebody knows if possible or exists something like librespot but for Tidal Connect?
Sorry if is not the best place to ask about :)
Regards,
Leandro
@hmelder commented on GitHub (Dec 21, 2020):
I have the official TIDAL Connect NodeJS Source Code. Got it from an unpacked electron asar bundle.
@michaelherger commented on GitHub (Dec 21, 2020):
What is TIDAL Connect? Even though I do have contacts with TIDAL, they haven't responded to me to this question... is it something proprietary? Glorified UPnP?
@sashahilton00 commented on GitHub (Dec 21, 2020):
It’s their version of Spotify connect iirc. Think it exists on Sonos currently
@lealoureiro commented on GitHub (Dec 22, 2020):
Is like Spotify Connect functionality but for Tidal. But not sure if they have public API available to build something like librespot to be able to create remote tidal client/player for linux.
@hmelder commented on GitHub (Dec 22, 2020):
It's a websocket connection with mDNS discovery.
On Tue, 22 Dec 2020, 01:26 Leandro Loureiro, notifications@github.com
wrote:
@lealoureiro commented on GitHub (Dec 22, 2020):
There is any documentation regarding how to use it?
@shawaj commented on GitHub (Jan 2, 2021):
Not sure this is supposed to be publicly available but it's in an open GitHub repo https://github.com/seniorgod/ifi-tidal
@sashahilton00 commented on GitHub (Jan 2, 2021):
Saw that, don't think it's supposed to be public, but regardless a quick look at it and the licenses would suggest that Tidal has also taken steps to prevent people from coming up with their own implementations - looks to be some kind of certificate authentication which I'm sure they can revoke, along with the references to https://github.com/andrivet/ADVobfuscator would suggest that they're not interested in having an open solution. Hopefully someone has spare time on their hands to take a closer look, but I think it probably belongs in a separate project from this one.
@hmelder commented on GitHub (Jan 3, 2021):
I think we should wait until they implement a server in their desktop app. But the nodejs client is neat and has all the certificates (even a readme).
@shawaj commented on GitHub (Jan 3, 2021):
@DerNuntius so the desktop app doesn't support tidal connect yet?
The nodejs client you mention - is that publicly available? Do you have a link?
@sashahilton00 agree it looks like they have intentionally provided a way to be able to shut it down. Whether they would though with a community implementation giving them publicity and promoting paid accounts is another issue though I guess... As from what I understood, librespot is not official and can be shut down too?
As a side note, interestingly that repo is for two products which don't yet exist called iFi ZenStream and NanoStream which are presumably based on ARMv7.
@hmelder commented on GitHub (Jan 3, 2021):
The desktop app can control a tidal connect enabled device and discover
new devices. There’s no server implemented. I’ve unpacked the electron app
you can do that too. I won’t publish the NodeJS package.
On 3. Jan 2021 at 09:50:38, Aaron Shaw notifications@github.com wrote:
@shawaj commented on GitHub (Jan 3, 2021):
Ah so you mean the desktop app is an electron app?
And when you say there is no server implemented you mean that the desktop app doesn't allow that machine to act as a device that displays on connect?
@hmelder commented on GitHub (Jan 3, 2021):
Exactly.
On Sun, 3 Jan 2021, 14:42 Aaron Shaw, notifications@github.com wrote:
@shawaj commented on GitHub (Jan 4, 2021):
@DerNuntius does it have any details about how connect works etc? Or it just ties into their API?
@hmelder commented on GitHub (Jan 4, 2021):
Looks like the client sends the oauth access and refresh token after
establishing connection for the first time. After that the client only
sends Playback requests or asks for the state. The tidal connect server
(device) requests the http stream from the tidal Api
(/v1/playbackinfopostpaywall).
The reason why tidal is obfuscating and securing the server is that there
are raw drm-free http streams requested from the API (and likely licensing).
On Mon, 4 Jan 2021, 03:45 Aaron Shaw, notifications@github.com wrote:
@kingosticks commented on GitHub (Jan 4, 2021):
Do you think it's worth moving this discussion somewhere we wouldn't mind being the victim of a takedown request?
@sashahilton00 commented on GitHub (Jan 19, 2021):
Probably a good idea. Not sure what they'd request was taken down though. Regardless, given that it's all speculative at the moment and doesn't relate to librespot directly, I'm going to close this issue and suggest that discussion moves to the Gitter chat. If headway is made then this issue can be reevaluated.