NOTE: Please use the search function above before posting to avoid creating duplicate topics.
- Device model MACBOOK PRO M1
- Version of operating system: macOS 15.7.3
- Version of djay (e.g. 5.1.2): 5.6.4
- Hardware/controllers used (e.g. Reloop Mixon 8 Pro): Pioneer DDJ RR
- Hardware firmware version (e.g. 1.0.1): N/A
- Storage: I have tested this across the internal SSD, external SSDs, and a high-speed microSD. The behavior is exactly the same on all of them.
Hi everyone, and @Slak_Jaw. I am opening this thread to report a severe and highly reproducible bug affecting the latest versions of Djay Pro, involving local files, UI rendering, and network timeouts.
The Issue: About 90% of the time, loading a local track causes a massive 10 to 15-second lag before the track actually loads into the deck. Additionally, when scrolling through the Queue or Smart Playlists, the track info and artwork thumbnails completely disappear, leaving blank spaces in the UI.
Troubleshooting & The Trigger: I have tried restarting, rebuilding, and testing thousands of UI combinations (loading from the Apple Music node, navigating directly from Smart Playlists, the queue, etc.). To rule out my FLAC files, I even tested a brand new, clean database with standard MP3s, and the issue persists. My Djay library database file is very healthy and lightweight (around 50 MB).
Here is the critical finding: This is definitely a network/API timeout issue. I currently have both Apple Music and Spotify services linked in Djay Pro. The lag becomes significantly worse when I am connected via a mobile data network compared to my wired LAN.
It appears that Djay Pro is trying to ping external streaming APIs (likely for the āMatchā feature or background checks) when loading a purely local file, and it is completely blocking the main UI and loading thread until the server times out.
This never used to happen prior to the recent updates. I know there is an older thread called āIssues with track loading, playback, and crackling soundā, but there have been no real updates there since 2025, and this seems specifically tied to how the newer builds handle streaming network calls for local files.
Could the dev team please investigate how these API calls are bottlenecking local library performance? Thank you!