Why use streamUrl instead of playbackinfopostpaywall for content download?

[dcdeve]

Hi,

First of all, thank you for sharing this project! I've been going through the code, and I noticed that the implementation uses the streamUrl method for downloading content from TIDAL. I'm curious—why was this approach chosen over playbackinfopostpaywall?

From what I understand, playbackinfopostpaywall provides a more detailed manifest, which could offer greater flexibility and control over content quality and formats. Is there a specific technical or practical reason for this decision?

I’ve already sent you an email offering help with the development.

Thanks in advance, and keep up the great work!

[oskvr37]

Welcome!

the implementation uses the streamUrl method

Do you mean this endpoint?

why was this approach chosen over playbackinfopostpaywall?

I'm not sure if you went through the right repository.

Tiddl is using playbackinfopostpaywall but the endpoint is called playbackinfo (those endpoints provides the same data), there are no streamUrl endpoints used in tiddl.

tiddl/tiddl/api.py

Lines 173 to 182 in dc040ab

	def getTrackStream(self, track_id: str | int, quality: TrackQuality):
	return self.fetch(
	TrackStream,
	f"tracks/{track_id}/playbackinfo",
	{
	"audioquality": quality,
	"playbackmode": "STREAM",
	"assetpresentation": "FULL",
	},
	)