Description:
In this video, I demonstrate a bug where DJay continues to display old (smart) playlists and folders that have already been removed from the iTunes Local Music Library. (Note: they are removed even months ago from iTunes).
Here are the main issues:
Old folders like “Specials” and “Nog Te…” (Still To Do) remain visible in DJay, even though they no longer exist in iTunes.
Duplicate and outdated smart playlists (folders) appear in DJay but are not present in the actual iTunes library (like the Special folder that is even shown 3 times)
So it seems that DJay does not 100% reflect the real-time state of the iTunes library (is it a sort of cache?)
Expected Behavior:
DJay should accurately + only mirror the folders and smart playlists in iTunes, without showing outdated or removed items.
Note:
I assume that Djay uses the new iTunes framework integration?
Could you please investigate and provide a solution? I’m also curious to know if other users are experiencing the same issue.
====
Device: MacBook Pro (16", 2019)
Operating system: Apple Os / Sanoma 14.6.1.
Djay version: Djay Pro 5.2.6
Hardware/controllers used: Reloop Mixon Pro 8
(But Demo just on Laptop)
As an addition to my previous post, I conducted a test by renaming the “Nog te…” playlist folder in iTunes to “1Nog te…”. After refreshing the iTunes Library, this change was reflected in DJay.
However, the issue persists:
The renamed folder appeared in DJay with the new name (“1Nog te…”).
The old “Nog te…” playlist folder also remained in DJay, still displaying the same content and name, even though it no longer exists in iTunes.
This further confirms that DJay retains outdated playlist folders that have been modified or removed in iTunes. It seems like DJay doesn’t fully clear or resynchronize the library data during updates.
Hi @DJ_Big_Blender, thanks for the video and details about the issue - very helpful! I’ve passed this onto engineering to see if they can replicate and offer any suggestions.
Hi @DJ_Big_Blender, I spoke with the team and unfortunately there’s not much that can be done on our end; djay pulls the data directly from the iTunes framework, and there’s no way on our side to distinguish if this is a bogus playlist, as the data looks the same for a valid/bogus playlist. Sorry I couldn’t be of more help here.
I have the same issue.
I do also use other software (e.g. Beatunes), reading out the iTunes (music.app) playlists, that show the correct lists. So it seems to be related to the implementation within Djay.
Hi @Criwo, thanks for the info. I will pass this onto our engineering team, but unfortunately in the meantime there’s not much that can be done on our end; djay pulls the data directly from the iTunes framework, and there’s no way on our side to distinguish if this is a bogus playlist, as the data looks the same for a valid/bogus playlist.
Hi Slak Jaw, just to be sure: it‘s not blank playlists.
It‘s about deleted playlists that should no longer be present in the local ITunes (music.app) library shown by DJay.
I have made a screenshot to show what my problem is.
It’s very annyoing, as it incorporates even worse orientation and visibility in the playlist structure. I would really appreciate, if one could find a workaround or fix.
Is it technically possibly to link Djay from scratch to the music.app (itunes) database?
Also information about my system:
Device: MacBook Pro (16", 2021 - M1 Max)
Operating system: Apple Os / Sanoma 14.5
Djay version: Djay Pro 5.2.8
Thanks @DJ_Big_Blender !
I have made another screenshot of my collection where you can see:
from left to right: DJay Pro (slave), Music.app (Master), Beatunes (slave)
DJay Pro shows the non existing old folders
Djay Pro does’nt allow to open one existing folder
Beatunes, which is also reading out the music.app library shows 100 % the same as the music.app (expected behavior)
For me this is a prove that it somehow is possible to read the music.app database correctly.
Please, algoriddim, don’t get me wrong. I don’t wanna say you are wrong. I just am really annoyed by this “bug” (in my opinion it is a bug) and want to help narrowing things down.
Hi @DJ_Big_Blender, thanks for the follow up. This is a different issue and the engineering team is still working on it. I will report here when this has been addressed. Thanks!
