Corrupted track

Hi
Try clearing the app's cache in Settings -> Data and storage -> Delete all (if you have downloaded tracks, you'll need to download them again).
And increase the app's cache in Settings -> Data and storage.

If that doesn't work and technical support needs a video or any other information from you, it's because they can't replicate the problem and need something to help them assist you.

On the other hand, using the music, however you obtained the MP3, in software other than Deezer Apps is illegal and could result in your account being suspended.

Cheers, and enjoy the music!

No, I’ve already tried that.

By the way, it’s not a cache as one normally understands it. Deezer always downloads tracks, and it only uses the cached file for the currently playing track.

You can check that by yourself by moving forward and backward: you’ll see several instances of the same file in the “cache” directory.

They can perfectly replicate the problem since the corrupted file is on their server. That’s what they did last time (after asking for the video a few times).

A video won’t help much since they won’t have the sound. A written description, like the one I did above, is much more helpful. They can replicate the problem in a matter of seconds. I could possibly send the corrupted mp3, as I did before, but I don’t think it’s necessary.

Using the “cached” mp3 in another player isn’t illegal, no. I don’t know where you got that notion. I openly discussed that with them before, and it’s not an issue. For your information, it’s not possible to listen to the Deezer track that way because the audio channels are scrambled. Still, the headers are valid and the file length must match the track length, so measuring that alone is enough.

EDIT: corrections (the editor seems to have eaten some part of the text)

you wrote:
if you take the mp3 file from the cache and load it in another player (Winamp, ...)
and that is not allowed

Terms and Conditions of Use
Chapter 6
https://www.deezer.com/legal/cgu

There’s no chapter 6; those are organized by articles. Deezers forces a French version on me, so that might be the difference. Maybe in your country it’s illegal, though I doubt it. What’s usually illegal is to reverse-engineer and decrypt protected assets or remove the protection, which isn’t what I did to help the support pinpoint the problem.

Please let’s stay on topic. I’m afraid your posts aren’t helping.

It's illegal WORLDWIDE.

But let's focus on your point. I've already played the song here in both quality, MP3 and HiFi, and it's cut off at the end, just like you said. But it's the artists (or their representatives) who upload the songs, and if it was uploaded incorrectly or corrupted when stored on the servers, they have to re-upload it if they want it to be correctly. It's unlikely that support will ask the artist to re-upload the song, but keep trying with them. 

There's nothing more we can do here in the forum because we're users JUST LIKE YOU.

I don’t think it is, but let’s agree to disagree. It’s not necessary to listen to the file, anyway. Just checking the length is enough, and it’s simpler. The first time I had a corrupted track, I did a series of test to narrow down what was happening; I think that sending the file to the support finally made them realize I wasn’t making that up.

It might be a bad upload by the artist, but again, I doubt it. Deezer must protect the tracks themselves, and they must encode it with the different options, which sometimes change when new formats are made available. Usually, artists send an uncompressed media, and the distributor (e.g. Deezer) compresses and protects it.

Finally, I seriously doubt that an artist would upload their tracks without checking that everything went well.

For example, when I first had the problem with another track, the corruption occurred after I had listened to it several times in its uncorrupted version. It got corrupted several months later. It must have been a problem on the server disk, which happens sometimes.

This is most likely what happened with this track, too.

Lastly, I’m not asking to users to fix the problem, obviously. I was hoping someone could either confirm or share if they had had similar problems. Above all, I was hoping that someone of their team took the 20 seconds it requires to do a quick test and report the problem internally. But if the thread gets confusing posts, chances are they won’t.

So thank you very much for your attempt to help, with cherry on top, but please stop posting here. I’ve had this problem before, I’m not a lost user, and I really know what I’m talking about.