I have simple example how this issue can be seen on DjPro side.
- For strange reason when moving from spotify to tidal, the “playlist move tool” mapped the same song to several different songs. One example of the song is
https://tidal.com/browse/playlist/4f9b6fd0-2f6e-4fbf-8663-0bde1ffbcb94
-
Now if analyzed the first track and setup the green marker.
-
Loaded the track 2 to another player, the beatgrids aren’t the same, there is a small difference.
- If I remove the cue point marker from the track player 1, it will remove the cue marker on the 2nd player as well.
So what this means is:
A) Tidal has several different files for the “same song”, different files for different quality…
B) DjPro will try to “figure out” if the song is the same based on some metadata artist + track name at least…
What this means is that
-
in worst case I can’t have Descpacito-remix as my local file
=> solution I can use different metadata i.e track name like Despacito-Remix-local-file
=> and analyze twice, edit beatgrids twice -
I can’t change Tidal quality if the “low quality” vs “high quality” if file on tidal side have even small difference on track length (like in example playlist 1-2s).
=> redo analyzis, setting beatgrids etc…
I hoped that Tidal would have been better than Spotify to have only “1 master file” for each track and each quality.
As a software developer I have no idea how this can be fixed easily on djpro.
Altough it would be really good to know if this can’t be fixed or what we can do to avoid these kind of problems while waiting the fix (or at least clear statement that this can’t be fixed in near future 2021).
