(Desktop) Playback issues with local files

[Maria]

We're receiving reports of users experiencing playback issues with local files. This seems to happen specifically on the desktop app, where playback stops at 0 seconds after every song.

[Maria]

Hey guys, 

I've tried out a temporary fix mentioned before and thought I would share it here:

This was mentioned before but I thought I would elaborate with a step by step guide - the 'corrupted' audio files will have a sample rate of 48000, when you want it to be 44100. You can check what the sample rate is by right clicking your file and looking at properties, under 'Details' it will say "Audio Sample Rate" with a number. If it's 48000, write it down because you'll need to change it.

Open up the Audacity software and dump in your corrupted audio files, then immediately hit export (you don't have to do anything yet!) Before you export it will show a couple options on how to export (mp3, mp4, etc) - ignore everything except for the "Sample Rate" section, and select 44100 in the dropdown. 

The file should now work. 
It sucks that we have to resort to these methods but I hope this helps at least a couple people.

Good luck, 
Bloodtraitor

[zondaa]

I thought the issue was caused by the high resolution of local files cover art, so I reduced it, but that didn’t fix anything. The tracks play fine on my phone, but on PC, after 1–3 songs, they get always stuck at 0:00. A month ago, this wasn’t happening. Please fix your app!!

[yezy999]

Plan

Premium

Country

Portugal

Device

(PC)

Operating System

(Windows 11)

My Question or Issue

Whenever I'm playing music on my PC, if the next song on the playlist or queued is a local file, there is a chance it doesn't start playing and just stops the music at all until I skip it, pressing play or pause doesn't do anything. 
I've already reinstalled it, and it only happens on desktop.

[owkle]

I am having this same issue and its on the Windows Store version and the one from the Spotify website it is extremely frustrating especially when I am paying for Spotify and it does not work properly with one of its most important features.

I am on Windows 11

[dani665]

whenever 2 local files play back to back it will just stop at 0 seconds on the second song, i believe this happens because the first song ends about a second before it says, then the next song says its playing in the ui, but wont go past 1 second unless i manually skip forward, ive tried messing with just about every setting and nothing has worked, ive even reinstalled spotify. anyone have a solution? this is also only a problem on my computer and everything works fine when 2 local files play on my phone.

(the image is what it looks like after the first song finishes)

[Deuseph]

Seems that nobody else has found any solution to this yet. I am trying to find if I can contact someone from Spotify's staff to hopefully get this investigated, but for now we still haven't find any good solution to this.

[cloudyincs]

Took me a while to figure something out but the best solution i've come down to is to downgrade to the version 1.2.60.564.gcc6305cb, most versions above that didn't work for me.

[Deuseph]

I didn't know you could even downgrade. It's not a fix nor THE solution Spotify has to give for this issue because this confirms that it is an update's fault, but for now I think it could be the only complete solution so thank you for commenting this. As for the future for a solution that could fix the issue on the current version, an Spotify advisor told me that she created a case about the issue and someone from a specialized team should contact me soon, so I'm telling them about this with everything else that has been known. 

[cloudyincs]

I totally agree, hopefully they get this fixed soon.

[tabonnemokspot]

how can I downgrade, and how can I have it so spotify wont auto update?

nevermind, got it. It's very easy to do both. I'll probably stay on this version too because I don't trust Spotify to be competent and make a proper PC client

[Fear_]

Just throwing a comment in here, downgrading fixed this problem for me too.