Gapless playback between tracks

This is getting really ridiculous. Deezer, wth, gapless has been constantly around since the '80s, it was meant as a way to express/compose music, not a futuristic gimmick. You're killing the feeling. You're disregarding/disrespecting the artists. You're ruining brilliant ideas. You're destroying the mood. You're just stubbornly headbutting music.
You are saying crossfade is your answer for this. You gotta be kidding me. Name one, just one artist, any artist, which says crossfade is fine for their gapless album. You say crossfade is the answer. But you only support crossfade on the web player. Where's your answer for gapless on Android or Windows? How's this called? Hypocrisy?
It cannot be your call how one's music is served to the masses, it has to be the artist's call.
The technology is there for you to use and implement gapless, but you don't. You either have very poor developers or a mediocre project leader with communist mentality. I'm not sorry for being hard on you.
You're releasing features with the speed of a snail, but you're expecting us to pay and pay and pay very quickly. Well, this is not how business is done in the software company I work for. Stop thinking like geek and nerd developers, your products are oriented towards art and people, not robots.
Once and for all, crossfade is not equal to gapless! When are you going to learn this?

@elektroinside I agree. It should be easy to implement gapless. If it's a technical problem I'd be glad to know...I can live with that, but it would be a pity.

If it's a technical problem, they should seek for help from somebody more competent. It's not that easy to implement gapless on all platforms, but not impossible. Others have done it. But they just throw that nonsense reply at us every time, like a call center narator reading the same text over and over: "our solution for gapless is crossfade". Bleah.

Hey everyone, all topics about gapless playback have been moved into this idea so we can keep better track of the demand and everyone can show their support by voting for it to be implemented 🙂

Signed up with trial for high quality music. First album listened = pink Floyd dark side of the moon. I like live music including DJ mixes. Unsubscribed. Remember the same problems with music in the 90s...

@Daniel Pugh
crossfade could help but let’s be honest...gapless playback is the only way 🙂

Can't see a cross-fade on Android and it's a bit pants - again remembering botched gapless implementations from when I was a young lad where "cross-fade" was provided as a holding ploy while developers think long and hard...

Can't see a cross-fade on Android and it's a bit pants - again remembering botched gapless implementations from when I was a young lad where "cross-fade" was provided as a holding ploy while developers think long and hard...

Crossfade (when present, it isn't on Android) only works acceptably well when silence is cut of at the end of the currently playing track and the beginning of the next. If the total silence of both tracks is greater then the configured crossfade time, you won't hear it, making it completely useless.

This means:

1. Somebody at Deezer should decide an acceptable level when the cutting of the silence should occur on both tracks. -20db is usually good enough, but it's a matter of perception and tastes in the end
2. This means the current track needs processing "ahead", the current track should be cached,then analyzed & processed (detect "the end of the track", detect the silence, cutoff from a certain point)
3. The next track should also be cached (and the "next track" can be tricky, depending if the user changes it or automatically played from a temporary list of songs, also depends on how well the internet connection works, format containers etc.)
4. The next track should also be processed "ahead", before the current song is done playing, and before the cutoff kicks in, exactly like the end of the current song
5. For best results, fade-out of the current song and fade-in of the next song (after the cutoff kicks in) is mandatory
6. The playing obviously should occur from the cache, not realtime. This is also difficult to control from a UX pov, as the user expects to hear the song almost immediately when he clicks on "next". So the cache needs to be built dynamically, in small chunks of data, not to hear a big gap between his actions, but cache takes a bit of time to build.
7. And finally, when everything is processed, both pieces (end of the current song, beginning of the next) should play at the same time. This means another cursor, different from the cutoff, and should be equal with the configured crossfade time.

So crossfade is technically even more complicated than gapless. Both can work in certain situations, but they will never work perfectly in "any situation". This has to be something the user understands. Deezer needs to understand that each offer a completely different perception for the user and only one of them is controlled (when allowed) by the artist: gapless. Nothing else is important for the artist.

Considering everything I just said here, gapless should be a much higher priority option and crossfade just a "good to have" feature.

Why isn't there a crossfade function on Android version of Deezer. This would be so cool for "mixing" your playlists ?

There's a crossfade on the Apple version of Deezer so why not on Android ???

Come on Deezer.......get it sorted !

It would be awesome to have a crossfade feature, like Spotify have.