Strange behavior when Spotify tracks are also local

When using Spotify tracks in djay that are also available locally, several issues occur that affect cue points, history, and track source integrity.

Steps to reproduce:

  1. Load a Spotify track that also exists as a local track (track length should be ± the same)
  2. You can see it takes over the Cue Points from the local track
  3. Play the track and observe the history and cue behavior.
  4. Load the same track again.

Observed behavior:

  1. Cue points inherit from the local track are often misaligned.
  2. After playback, Spotify tracks in the history list are replaced by the local versions.
  3. The icon in the history list shows the wrong source (local or iTunes icon instead of Spotify).
  4. Reloading the track originally from Spotify shows local album art and corrects cue points according to the local track, effectively replacing the Spotify track completely.

What I was expecting:

  • Spotify tracks should maintain their own cue points and loops, independent of local versions.
  • History should retain the original Spotify track and source icon.
  • Loading a Spotify track should not replace it with a local version automatically.

Additional:

  • Ideally, Spotify tracks should not inherit cue points or loops from local tracks at all, even if the track exists locally.
  • This is causing unreliable performance and inconsistency when mixing Spotify tracks.

See video:

===
Device: MacBook Pro (16", 2019)
Processor: 2,6 GHz 6-Core Intel Core i7
Operating system: Mac OS / Sequoia 15.6.1 (24G90)
Djay version: Djay Pro 5.5.
Hardware/controllers used: Reloop Mixon Pro 8

Is this expected behaviour @Slak_Jaw ?

Hi @DJ_Big_Blender, I’m still waiting for confirmation from engineering, but I believe this is somewhat expected behaviour due to the way djay identifies songs based on Title/Artist/Length. So if your Spotify song matches that of your local song it will pull the matching metadata from the djayMediaLibrary database. As for the offset, I believe this is also expected behaviour due the different encoding for your local song and the Spotify song.

Hi again @DJ_Big_Blender, I heard back from engineering regarding this. Yes, this is related to titleID matching method that we use. djay currently will always prefer resolving a track to a local file reference rather than to a streaming file reference. We can see this can be a little confusing for the history so we can look at options to tweak this behavior in the future.

For the cue point offsets we are aware of this and are currently looking into solutions. Thanks!

Yes, thanks. It would be helpful when it would be an option to turn that off.

You’re welcome @DJ_Big_Blender