Last night, during my gig, I noticed an issue with the match suggestion feature. I always keep the right-side panel open to display matches, and while it usually works fine—both at home and during live performances—this time, the matches stayed empty most of the time.
For context: I have the match suggestion set to show matches for the active deck. When I tried to refresh it by switching the crossfader back and forth, it still didn’t display any match suggestions.
Is the match functionality dependent on an online database? If so, could that explain the issue, given that my Wi-Fi wasn’t particularly fast during the gig?
Btw;
This issue is also 100% connected to the ticket below, but only nowhere your last message was: We are still reviewing this internally and will reach back out very soon with further information.
However, now it is happening almost constantly. Is there any progress on that ticket? Additionally, could I share some log files or provide other information to help speed up the process?
Thanks for your response! That actually explains a lot about the occasional hiccups in the Match feature. I must say I didn’t expect this to be the case, as I assumed the feature could also work offline because it’s only about locally stored data.
It might be helpful to communicate this dependency more clearly in the app or documentation, as it could prevent confusion for users who experience similar issues. Thanks again for clarifying!
Thinking a bit further about this answer makes me quite curious why the Match feature requires internet access. What exactly does it do online? I am asking because, as far as I know, the input for calculating the best matches can be based on locally stored (meta) data of my own music, isn’t it?
