I have a solution
-
Create a new folder on your desktop (somewhere easy to locate) with a copy of every track in your desired playlist.
-
Create a new user for your mac
-
Sign into your App Store download DJ pro but do not add any music previously stored, do not sign into any streaming platforms etc
-
Using a separate Apple device, I used my iPhone, go into files and locate the new folder containing all of your playlist’s tracks
-
Share/AirDrop folder to your Mac (logged into the new user)
-
In DJ pro select “my files” on the bottom left toggle where usually your streaming platforms would be logged in
-
Click the + and add the new folder
-
Right click the folder which is now added to “my files” and click add to my collection
You will now notice when you start to play your set and hit the match feature, the feature is now limited to tracks from your playlist only.
Sure it’s a slightly tedious process, but the outcome was exactly what everyone seemed to be after. (Yes I am fully aware that this fails after one playlist unless constantly removing/adding tracks from your new folder). But HOPEFULLY BY THEN THE DEVS TEAM AT ALGORIDDIM CAN SORT THEIR ISH OUT 
Thanks again for sharing this @LUCKYMONEY.
Hi everyone, I want to bump this thread and strongly support @DJ_Big_Blender and @djsteve’s proposals. However, I want to add a critical technical angle: the current state of the ‘Match’ feature isn’t just a usability limitation; it is actually causing severe performance bottlenecks.
Running Djay Pro on an M1 Pro (macOS Sequoia), my workflow is strictly local. I use meticulously tagged FLAC files (managed via Mp3tag) running off a high-speed microSD. Despite the powerful hardware, because ‘Match’ currently forces a global search across all connected sources (including Apple Music), loading a local track often triggers a 10-15 second lag.
The app gets stuck trying to ping external APIs to match my custom local tags against massive streaming databases, instead of just looking at my local selected folder. This bottleneck is so severe that it even causes the UI graphics engine to fail, dropping artwork thumbnails in the queue and smart playlists while it waits for the server timeout.
If we could restrict the Match source exclusively to a specific local playlist or folder as requested, it wouldn’t just improve track selection; it would instantly solve these latency and UI caching bugs. This is a stability necessity for live gigs.
@Slak_Jaw, could you please pass this specific performance/lag aspect to the dev team? Thank you!
1 Like
Thanks for the additional input @Albert_Maro. I’ll let the team know.
There are quite a few DJs that use the Comments field to multi tag a track. Mine for example might include
#Disco #House
This means this appears in my smart playlists under both the House and Disco categories
Once I switch genre mid set having the ability to filter my matches by these genres would be invaluable.
2 Likes
Thanks for the additional input @djaluca
Just dropping by to see if there are any updates on this request. Honestly, in its current state, the Match function is almost unusable for a strict local workflow.
It is incredibly frustrating that we still cannot restrict the matching source to a specific local playlist or folder. Because the engine insists on searching globally—often pinging streaming services like Apple Music even when I am playing strictly local FLAC files from my SD card—it renders the feature counterproductive. In fact, this exact behavior of pinging external APIs is causing severe 10-15 second track-loading lags in my setup (which I have reported in a separate bug thread).
We really need Match to be restricted, focused, and optimized for local, offline sources. Is there any news from the dev team on implementing these boundaries?
2 Likes
Thanks for the input @Albert_Maro. We don’t have any updates to share for this suggestion.
1 Like
