Welcome to Deemix Remastered Discussions!

[DRAZY]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[alex5908]

Hi everybody,

Andre, your commitments to users is just unbelievable!
Thank you so much for creating the field for discussions of the merits of your Creature, named by Deemix Remastered.
Actually to me that's absolutely different app you're working on.
It's not a Deemix anymore and long time ago. The features you have created can't be even compared with the old Deemix. Not even close.
I remember I was asking about small changes in the app from a previous developer of Deemix but in the best scenario received response that it's not important but in most cases I did not receive any answers at all.
Andre, you, on the contrary, fulfilled all my wishes/desires. I don't even understand what more could be improved but you come with more and more new features and enhancements.
Gob bless you, Andre.
With your permission I will post the address for this Chat in my Public enhancement features request.

[alex5908]

Hi Andre,
I am trying your new feature which is Qobuz dn.
Thank you very much for this feature. I thought that would be considered by early next year but... Here you are. To me that request was made a couple of days ago and now I am using it.
Now about the new feature. To me it's much slower compared with Deezer dn. I started to dn a pl of 1K tracks about 8 hrs ago and it's still 75%. Is it about the specific pl I am downloading or some limitations on Qobuz side?

P.S.

For the sake of experiment I will download the same playlist in Deezer. Well, just to compare as I might be wrong about the Qobuz downloading speed.

[DRAZY]

Hi Alex — thanks for the detailed speed report, and for running the Deezer comparison. Your timing was perfect: it led straight to a real inefficiency, which is fixed in the v2.1.2 build now on the Releases page.

What was found and fixed: the Qobuz download path was re-downloading the album cover for every track (the Deezer path has always cached it per album). With Artwork Size set above 600px that meant the full-resolution original scan — often several MB — once per track. Across your 1,000-track playlist, that's potentially gigabytes of redundant transfer. Covers are now fetched once per album and shared across its tracks. Grab the re-rolled 2.1.2 build to pick this up.

The other big factor is honest physics: if you're downloading at FLAC quality, Qobuz delivers true hi-res — a 24-bit/192 kHz track can be 100–200 MB, versus ~10 MB for a Deezer MP3-320 or ~30 MB for CD-quality FLAC. Same connection, many times the bytes, so hi-res will always take meaningfully longer per track. The quality chip on each completed download shows the tier actually delivered, so you can see exactly what came down.

Two speed levers worth checking:

• Settings → Downloads → Concurrent Downloads — applies to Qobuz too.
• Natural Download Pacing — if you enabled Balanced/Cautious (it's off by default), it deliberately adds gaps between download starts; that compounds over a 1,000-track run.

I've also queued two further optimizations for the next feature release: skipping a redundant per-track metadata call on album/playlist runs (#112), and smoother UI with very large queues (#113). If the new build still feels disproportionately slow on your connection after the update, tell me the delivered tiers you're seeing and I'll dig further.

[alex5908]

Just wow!!!!!!!
With the app's latest version the Qobuz download speed is faster than that of Deezer. In just 5 minutes it's 10% of 853 tracks!
Unbelievable! Thank you, Andre.
Final thought.
484 Qobuz tracks for 27 minutes. Just great!

[alex5908]

Guys,
I think I am still not awake in full but I guess I saw the loudness preview in the app. Can we listen to songs before downloading?
I tried my best but can't find it anywhere now.

[cisko99za]

wonderful app, but:

1. i've start a download with deezer arl, saved file in flac. but discvover my download it's an album, not single track, i've stop the download but download continue to the end of all tracks. just close the app stop the download
2. added qobuz token i get Qobuz reject token but the token is valid, added to another app i can download

i talk about portable win version of latest 2.20 deemix version

[cisko99za]

also: why need spotify client and secret if i can add just one track link and this app download from deezer??

[DRAZY]

Hi cisko99za, thanks for the detailed report. In order:

1) Stopping a download doesn't stop it. That's a real bug and you're the first to catch it. Removing a row from the queue currently only removes it from the screen; the server keeps downloading the rest of the album in the background, and closing the app is the only thing that kills it. I've confirmed the cause in the code and opened #118 to track the fix, so canceling a row will genuinely halt its remaining tracks server-side.

2) "Qobuz rejected this token" on a token that works elsewhere. Qobuz ties auth tokens to the app_id they were issued under. Deemix Remastered validates your token against the official Qobuz web player's credentials, so a token generated under a different app's credentials gets rejected for us even though it's valid in the app that created it. Two things would help me pin this down: which app or tool did the token come from, and if you log into play.qobuz.com in your browser and pull a token from there, does that one connect? If the mismatch is confirmed I'll make the error message say exactly that instead of the generic "rejected."

3) Spotify client/secret. Optional, and only used for Spotify link conversion: paste a Spotify playlist or track link and the app reads its metadata through Spotify's API (which requires those credentials), then finds the matching tracks on Deezer. If you don't use Spotify links you can ignore that section completely.

[DRAZY]

@cisko99za v2.2.1 is out with the fix for your first point: canceling a download now genuinely stops it, including mid-track. Grab the new build from the Releases page.

On your Spotify question, here's the full picture. The app downloads only from Deezer and Qobuz; Spotify is never a download source. The client ID and secret exist for one optional convenience: link conversion. Paste a Spotify playlist or track link and the app asks Spotify's API what songs it contains (titles, artists, ISRCs), then finds those same songs on Deezer and downloads them from there. Spotify's API refuses to answer that question without registered credentials, which is why those fields exist even though no audio ever comes from Spotify. A plain Deezer track link never touches any of this: the link already identifies the song on Deezer, so there is nothing to convert. If you never paste Spotify links, leave the Spotify section empty; nothing else in the app depends on it.

And still interested in your answers on the token question above when you get a chance: which app the token came from, and whether a token from play.qobuz.com connects.

[cisko99za]

Many thanks for your thorough replies, as well as for the new version 2.2.2 that fixes the first problem. I'll try it as soon as possible.
Regarding Spotify, I understand what I'd already understood: tracks aren't downloaded from Spotify itself, but from Deezer. Now you've clarified that without credentials, the API won't respond even to a simple link to a song, and therefore it's not possible to search for it on Deezer. At this point, I'll use a fake account to obtain the client/secret credentials to enter in your download app (I prefer not to use my official ones so as not to potentially compromise my real account).
about qobuz token it's ... from the sky ... I'm sure you'll understand what i mean. So if that's the case, I don't think I'll be able to use your app to download from Qobuz.... the only thing i can do if you give me your email or something i could share my token with you so you could test it personally. surely can't post it here publicly. let me know

edit: tested just now the new 2.2.2 version. and now work fine. first issue now solved. thanks

[cisko99za]

another stuff: from the home page of your app i see many album, but now way to download just some tracks, but only i can download all tracks... Is there a way to download just some tracks from an album or just the full album?
the old deemix (I known it for a long time and have used it for years) allow to choose from each album which track to download, or download the whole album

[DRAZY]

Glad 2.2.2 sorted the cancel problem, and your read on Spotify is right.

First, the easy one — yes, you can download just some tracks from an album. On the album page, click Select Tracks (top right, next to the download button). Checkboxes appear on every track; tick the ones you want and hit Download N tracks. The plain Download button still grabs the whole album, so you have both.

On Spotify — one heads-up before you set up a throwaway account, because it'll save you the trouble: a fake free Spotify account won't work either. Spotify recently changed their API so the account that owns the Client ID/Secret has to have active Spotify Premium — a free account gets rejected on every request (another user just hit exactly this). Your instinct to keep your real account out of it is sound, but the throwaway would need Premium to function. And if what you ultimately want is just the songs, you can skip Spotify entirely: search the track or album directly in the app and download it from Deezer — same music, no credentials needed at all. The Spotify link is only a shortcut for importing a playlist you've already built there.

On the Qobuz token — that thread's still open from your first report (rejected here, but worked in another app). If you can tell me which app or tool you got the token from, I can check whether it's an app-ID mismatch on our side. Qobuz ties each token to the app it was issued under, so that detail is the key to it.

[DRAZY]

@alex5908 — circling back to your question from a few days ago (sorry it slipped past me): yes, you can preview tracks before downloading. Every track row has a small play icon — click it and you'll hear about a 30-second sample of the song. It works in search results and on album and playlist pages, anywhere a track is listed. In the newer builds the preview also jumps to a representative part of the song instead of starting cold at 0:00, so it's a better gut-check before you commit to the full download.

[DRAZY]

On the Qobuz token — I appreciate the offer, but let's not do that. I don't want you sharing a private token with me by email or anywhere else. Credentials should only ever live in your own copy of the app, never handed to another person, and I'd give any user the same advice.

Here's the likely answer anyway, given it's "from the sky": Qobuz ties every token to the specific app it was minted under, and this app checks tokens against the official Qobuz web player. A token from some other source almost certainly carries a different app ID, so Qobuz rejects it here even though it works wherever it came from. The reliable way to get a token this app accepts is to use the normal Qobuz login in Settings, or paste a token pulled from play.qobuz.com in your own browser. If you go that route and it still fails, tell me and I'll dig in.

[cisko99za]

understood. so forget qobuz.
Regarding the download of the single song I only see Get for each album.
I do not see anywhere the list of tracks that the album contains

about spotify and download from deezer that's what I'm looking for. I'm full of apps that allow you to download from any Tidal Apple deezer and qobuz service but with all of them I have to search for the song get the link and then download
what I need from your app and the full congruence between add a Spotify album/track/playlist link and downloading from Deezer, this would be very useful for me. understand need prem account to create a dev app, what you could do is modify your app so that it doesn't ask client & secret but load Premium cookies of an account or even just add sp_dc value which is the key to manage Spotify API, like Orpheus does

[DRAZY]

[DRAZY]

Alex, thanks for the two screenshots and especially for the follow-up saying it fails on your own playlist too. That second message is what made this solvable, because it ruled out the explanation I would otherwise have reached for.

Nothing is wrong with your setup, and your credentials are fine. This is Spotify changing their API out from under the app.

Here is what happened. In February 2026 Spotify renamed the fields in the playlist response. What used to be tracks is now called items, and the nesting inside it changed the same way. The app still asks for tracks, which doesn't exist any more, and the moment it tries to count how many songs are in there it hits nothing and throws the "Cannot read properties of undefined" message you're seeing. That error is the app failing to read a field that got renamed, which is why it looks like gibberish rather than a normal "playlist not found" message.

The reason you're hitting it and most people aren't is that these rules arrived for Development Mode apps, the kind you get when you create your own client ID and secret. Existing ones were moved over on 9 March 2026. So your app is on the new response format while others are still being served the old one. It isn't anything you did.

There is a second part worth knowing now rather than later, because it will shape what's possible even after I fix the reading side. Under the same change, Spotify only returns the actual contents of a playlist for playlists the signed in user owns or collaborates on. For anything else it returns the name and the artwork and the description, but not the songs. The app authenticates with just a client ID and secret and no user login, so I need to test carefully what that means in practice for playlists you own versus ones you don't. I'd rather tell you upfront that some playlists may end up readable and others not, than have it look like a new bug later.

I'm going to work through the migration to the new field names. That's a real piece of work rather than a one line patch, since the old shape is read in several places, so give me a little time on it.

One thing that would help, if you don't mind. In your Spotify developer dashboard, could you confirm whether your app shows as being in Development Mode, and roughly when you created it? That tells me exactly which format you're being served, so I can build against the right one instead of guessing.

Sorry you hit this. You've now found two real ones for me, and the detail you put into the reports makes them much faster to chase down.

[alex5908]

In your Spotify developer dashboard, could you confirm whether your app shows as being in Development Mode, and roughly when you created it?

Yes, I am in Development mode. I have created the app today.
You should not be sorry, but on the contrary, you should only be proud of yourself as you do the tremendous work for the society.

[DRAZY]

Alex, 2.5.7 is out with the fix: https://github.com/DRAZY/deemix-remastered/releases/tag/v2.5.7

The app now reads both the old and the new field names, so it works whether Spotify sends your app the format it used before February or the one it's sending you now. Your Development Mode answer is what made that possible to build with any confidence, because it told me exactly which format you were getting instead of leaving me guessing.

Would you mind trying it and telling me what happens? I want to be straight with you about why I'm asking. I can't reproduce your failure here. My own Spotify app was registered before the change, so it still gets served the old format no matter what I do, and I confirmed that by pulling both of the playlists you linked through it. They both came back fine, 291 tracks and 5 tracks, which is how I know the playlists themselves are healthy and the problem was only ever the format your app receives. That means your machine is the only place the new path can actually be proven. I tested it against a simulated new-format response and it passes, but simulated is not the same as real and I'd rather you heard that from me.

One thing to expect so it doesn't look like a new bug. For playlists you don't own, Spotify may now send the name and the artwork but not the songs. That's the same February change, and it's a deliberate restriction on their side rather than something the app can work around. When it happens you'll get a short explanation saying so instead of the error you saw before. Playlists you created yourself shouldn't be affected.

If it still fails, the error message should be readable this time rather than that "Cannot read properties of undefined" line, so whatever it says will tell us a lot. Send it over and I'll keep going.

[alex5908]

Would you mind trying it and telling me what happens?

Thank you for the app update.
I get this now.
"Spotify sent the playlist details but not the songs in it. Since February 2026 a developer app only receives the contents of playlists owned by the account that authorised it, and returns name and artwork only for everything else. Nothing is wrong with your credentials. Copying the tracks into a playlist on your own account and using that one is the reliable way around it."

Does it mean that the workaround is copying the songs list from somebody else's PLs into my own PL will fix the problem?

[alex5908]

Unfortunately this workaround does not work either.
I created my own PL and it reads the same thing as above about February 26 changes.
https://open.spotify.com/playlist/0kFalUlcdyd6y8Zzglzpar?si=2EaPNZYMTbauLtX_SZA2Lg

[DRAZY]

You're right, and my advice was wrong. Sorry for sending you off to build a playlist for nothing.

To answer your question directly: no, copying songs into your own playlist will not fix it, and you proved that faster than I could. I pulled the playlist you just made through my own setup to be sure the playlist itself was fine, and it is. "Alex's AOR", 1516 tracks, reads perfectly here. So there's nothing wrong with what you built.

Here's what I got wrong. Spotify's rule says a developer app only gets the songs for playlists belonging to the account that authorised it. I wrote that message thinking "your own playlist" would satisfy it. It doesn't, because this app signs in with just a Client ID and Secret and no personal Spotify login. There's no account doing the authorising at all, so nothing qualifies as yours from Spotify's point of view, and it withholds the songs for every playlist including ones you created a minute ago. That's why you saw the same message twice.

One thing worth knowing while you're weighing what to do. This only bites credentials created recently. Apps registered before February are still being served the songs, which is why it works for most people and why I couldn't reproduce your problem on my machine.

(Edited twice, and this is the settled version. The paragraph originally claimed Spotify Premium had nothing to do with this. I had no basis for saying it, so I pulled it and asked instead. Alex confirmed on 18 August that the account behind his developer app does have Premium, which rules it out as the cause. So the original claim turned out to be correct, but I had no grounds for making it at the time. The accurate statement is: Premium is required for Development Mode Client IDs created after 11 February, his is in good standing, and it is not what is withholding the songs.)

The one thing that would actually fix it today is on Spotify's side rather than mine. In the Spotify Developer Dashboard you can request extended access for your app, which takes it out of Development Mode. I have not been through that process myself so I can't tell you how long it takes or how likely approval is, and I'd rather say that than guess.

I've corrected the message in the app so nobody else loses an evening on that workaround. It now explains why no playlist qualifies and points at extended access instead, and I fixed a second message that was giving the same bad advice for Spotify's own editorial playlists.

One thing to flag about how that reaches you. Since it's only wording and nothing about how the app behaves, I'm not burning a new version number on it. It'll go out as an updated 2.5.7 download rather than 2.5.8, so the version you're on won't change and you won't be able to tell by looking. Nothing you need to do, and there's no benefit to reinstalling for it since you already know what the message should have said. I'll mention here when it's up.

I'm also looking at whether the app could support signing in with your own Spotify account, which is the thing that would make your playlists work properly. No promises on that yet, I want to understand it before I commit to it.

Thanks for testing it so quickly and for coming back with a clear result. That's the second time this week your report has been more useful than my assumption.

[DRAZY]

Alex, a question, and a correction to what I told you earlier.

Does the Spotify account that created your developer app have Spotify Premium?

I told you above that Premium had nothing to do with this. I've gone back and edited that, because I had no basis for saying it. What I did was reason backwards: your app was returning playlist names and artwork, so I assumed it must be working fine and therefore Premium must be satisfied. That was a guess dressed up as a fact.

Reading Spotify's February announcement properly, Premium is one of four restrictions that apply to Development Mode Client IDs created after 11 February, and yours was created this week. The others are one Client ID per developer, a cap of five authorized users, and a reduced set of available endpoints. Spotify does not document anywhere what actually happens to an app whose owner does not have Premium, so "it returns some data, therefore Premium is fine" was never a safe conclusion.

So your answer genuinely changes the picture. If you do have Premium, then my explanation stands and the problem is that the app signs in without a personal Spotify login, which extended access would address. If you do not, then the simpler explanation is that your app has never been fully working, and I would have sent you off to request extended access for the wrong reason.

While I'm here, the corrected 2.5.7 download is up. The version number hasn't changed, so nothing for you to chase, and it won't make the playlists readable either way. It only fixes the wording.

Sorry to come back with a question rather than an answer. I'd rather ask than have you act on another confident guess of mine.

[alex5908]

"Does the Spotify account that created your developer app have Spotify Premium?"
Yes, it's Spotify Premium.

[DRAZY]

Thanks, that's the answer I needed and it rules Premium out cleanly.

So where that leaves things: your app is in Development Mode, Premium is in good standing, and Spotify still sends the playlist details without the songs. That removes the last alternative explanation I had, and leaves the one in the app's message. Deemix signs in with a Client ID and Secret and no personal Spotify login, so from Spotify's side there is no account doing the authorising, and their February rule only releases the songs for playlists belonging to that account. With no such account, nothing qualifies, which is why your own playlist behaved exactly like everybody else's.

I've also gone back and tidied my earlier correction above, since it said I didn't know whether Premium mattered and now we do. Worth being straight about the sequence: I first told you Premium was irrelevant, then realised I had no basis for saying so and pulled it, and your answer has now shown the original claim was right. Right conclusion, bad reasoning, and I'd rather you saw both than just the tidy version.

The way forward I can point at today is on Spotify's side rather than mine. Requesting extended access in the Spotify Developer Dashboard takes your app out of Development Mode, which should restore normal playlist reading. I still have not been through that process myself, so I can't tell you the odds or how long it takes, and I'd rather say that than invent a number.

If you do try extended access, I'd still like to hear how it goes. You'd be the first data point I have on it.

[cisko99za]

hi folks, just for test i have update to latest 257 version, added alex playlist above, and this is my result (me too have premium spotify account with dev app data). and same from my another personal playlist

[alex5908]

Yeah, yesterday I tried about 20 of different sizes playlists... Received the same note. Unfortunately.
And unfortunately Spoti has the number of playlists which can't be compared to any other platforms of the kind. Not even close.
If you search for Country 2026 at spoti you will get a thousand. At other sources maximum 200. Simple maths- 5 times as much to say the least.

[DRAZY]

Cisko, thanks for testing. Getting the same failure on your machine is what confirmed it.

It comes down to when you registered the Client ID.

My app is also Development Mode, also Premium, and it just read all 291 tracks of a playlist that isn't even Alex's. So it's not the mode, not Premium, and not who owns the playlist.

Spotify restricted new Development Mode Client IDs on 11 February. Existing ones were due to get the same treatment on 9 March, but they postponed the endpoint changes for existing apps. Those endpoint changes are what strips the songs out. Mine was registered well before all that. Yours are both from this month.

I also have to take back what I said about requesting extended access. I went and read the actual requirements. Since May 2025 Spotify only accepts applications from organizations, not individuals, and you need a registered business with a launched service and at least 250,000 monthly active users. None of us can apply for that, so put it out of your mind.

So there's no fix on my end, and mine only keeps working until Spotify lifts the postponement.

One other thing I floated that I'm not doing: Spotify login. It'd only give you back your own playlists, not the ones you're actually after.

[cisko99za]

so you're saying that an app, and therefore a client id, created after February 11th won't work with your app, while if I use a client id created before February 11th it will work with your app. right ?

[DRAZY]

Right, that's the pattern. Two catches though.

You can't create a pre-February Client ID now. If you already registered a Spotify app before 11 February then that one should work. If you don't have one, there's no way to make one, so this isn't really a workaround you can go and use.

And it's a reprieve rather than a permanent difference. Spotify postponed the endpoint change for existing apps after community pushback, they didn't cancel it. Whenever they lift that, older Client IDs including mine will do exactly what yours does now.

[cisko99za]

An alternative could be load premium cookies without the app's developer credentials....
but this solution, already mentioned above, you don't want to follow, even if it would be a temporary solution while waiting for Spotify's revocation.
but as mentioned above, this isn't an option you're interested in, so let's leave it alone. sin because your app at the moment was the only one that recognized spotify link and converted it into a deezer or qobuz link, which is amazing for me. Spotify, it's my favorite streaming service and right now isn't possible to download from Spotify.
but well i've exported my plist from spotify to deezer and download it with your app. simply and easy.

[DRAZY]

That export trick is smart. Going Spotify to Deezer and downloading from there sidesteps the whole thing.

Alex, worth a try given how many playlists you've been through.

One thing I can't test from here: the February change was specifically about playlist contents. Do single track and album links still convert for you? Mine do, but my credentials are old so that tells me nothing about yours.

[cisko99za]

again you're right: with spotify dev credential from Link analyzer (with new fresh credential, after February) work fine for single track and also work for album. just playlist is forbidden

[alex5908]

Alex, worth a try given how many playlists you've been through.

What shall I try?

[cisko99za]

find an easy solution to get all url's from playlist. with url's we can add single url to Link analyzer
go to https://www.chosic.com/spotify-playlist-exporter/ (no login required, but work only with public playlist, no private)
this site extract track id and also ISCR. the final url is https://open.spotify.com/track/track_id
now you can add this url on Link analyzer and start download

another is https://exportify.app/ but this required spotify login with your account to load your playlist. The advantage of this other service is that you get url list instead just track ID (or ISCR)

[alex5908]

with url's we can add single url to Link analyzer

Do you mean to download song by song from a playlist? What if a playlist contains 5K songs?

[alex5908]

https://exportify.app/

Does Deemix-remastered take .csv files?
And even if it does there are no playlists links in csv files.

[DRAZY]

No, it doesn't take CSV files, and you're right that it wouldn't help if it did. The exports from TuneMyMusic and Exportify give you titles, artists and albums, not Spotify links, so there'd be nothing in the file for the analyzer to work with.

Cisko's snippet is a different thing worth not mixing up. It saves a .txt of actual track URLs straight off the playlist page, which is why it works at all. Scroll to the bottom of the playlist before running it or you'll only get the rows Spotify has drawn.

One thing those CSVs usually do carry is an ISRC column, and the app already looks tracks up by ISRC. So a CSV could feed a different kind of import that matches by recording instead of by link. That's a bigger piece of work and I'm not starting it, but it's the version of the idea that would actually go somewhere.

[cisko99za]

plist with 5K songs .... well its hard work! i mean my plist is 30-50 songs only
find just some plist about 400 tracks, but after listening all songs i created my personal playlist with 100 tracks only and so the work is doable!
with big plist like your the best way is tunemymusic or soundiiz and transfer spoty plist into deezer plist and download from deezer

about csv no, Deemix-remastered dont allow csv, but you can open with some online service like https://csv-viewer.online/
track URI is track_id

spotify:track:4iAYo83eWlktjw97oebIal
the track link is https://open.spotify.com/track/track_URI
then https://open.spotify.com/track/4iAYo83eWlktjw97oebIal

chosic.com is better: not required spotify login and show on window browser the track id to get the track url. also you can export as csv or txt file

[cisko99za]

ooohhh NEW GREAT SOLUTION (thanks to Gemini)
open dev tool from ur browser (mouse right click - Inspect)
go to console and paste:

const links = [...document.querySelectorAll('a[href*="/track/"]')].map(e => e.href.split('?')[0]);
const text = [...new Set(links)].join('\n');
const a = document.createElement('a');
a.href = URL.createObjectURL(new Blob([text]));
a.download = 'playlist.txt';
a.click();

this save file as playlist.txt with url like https://open.spotify.com/track/1ZIwFSsqtIP74qvNS7VjdU

[cisko99za]

@DRAZY
your app on Link analyzer allow 1 link only. because we can find a way to get all urls from plist, a new wonderful suff is for next rel add multi links, not 1 only. thanks

[DRAZY]

That snippet is a proper find, and it works because it never touches the API at all. It's reading the page you're already signed into, so none of the February Client ID business applies. Alex, this is worth a look.

One catch to save you both some confusion: Spotify only renders the rows that are on screen, so on a long playlist you'll want to scroll all the way to the bottom before running it. Otherwise you'll get a clean-looking file with maybe the first fifty tracks in it and no sign that anything is missing.

On multi-link input, I agree, and it's the obvious next step now that getting a list of URLs is easy. The batch download path already exists internally, so it's mostly a question of the analyzer accepting a list and showing you results per line. No promises on which release, but it's on the list.

[cisko99za]

deezer arl It has a short life, so i often have to update ARL. Every time i need to update ARL, I have to go to Settings, but even though i close the profiles, appearance, languages ​​panels, when i try to add the new Deezer ARL, when i reopen the app, the panels are open again. That is, it doesn't keep the panel closing setting. you can edit the app to keep those panels that aren't relevant closed? thanks