Locate track not working

Bug Reports
1
  • mabook pro 16” 2.6. 8 core
  • Version of operating system (e.g. macOS 14.4.1):
  • djay 5.6.1
  • flx4

Hi, locate track very unpredictable, most of the time doestn’t work but when it does it only works for only 1 deck.

Thanks.

3

Hi @Donn, thanks for the video and details. What version of macOS are you using? I was not able to reproduce this on my setup. Thanks

5

Hi Slak_Jaw, I’m using Sonoma 14.8.1

This feature since it came out was always unpredictable. For example, as I mentioned when it did work it would only work for one deck or not at all. Other times especially if you have a song in a nested folder it wouldn’t work at all unless you triggered the command about 4-7 times in a row and then it might locate to the song inside the nested folder.

(actually I recall on rare occasions it did work for both decks when I randomly load a bunch of songs from different playlist (main list, sidebar list, search results, and trigger the Locate command a bunch of times but I couldn’t figure out any pattern to why it worked)

Thanks!

1 Like
6

Thanks for the additional info @Donn

7

Hi again @Donn, our engineers have tested this and everything seems to be working as expected. Please see below for further clarification. Thanks!

  • The locate command will toggle between the visible decks to choose which song to find
  • It won’t find tracks in search results, as they are not part of your library
  • The first locate track command locates the track on Deck 1 in the library. Triggering the command a second time would locate the track on Deck 2 in the library, and so on and so forth. As one track is loaded from search results, which are not covered by the locate file feature, the command would fail every second trigger as it won’t locate the track loaded from search results.
8

Thanks for the reply! In the video i happen to search a song but the exact issue happens without a search and I simply load songs from the main playlist to both decks. It’s random but I’ll try record a video.

9

Okay, thanks @Donn. A video would be super helpful in this case.

10

Here’s another video, this time the deck not working was loaded from the Match list.(video below)

Also in a different testing, when I loaded a song from the search result and used the Locate, it actually did locate the track from the search result deck. It showed the song from the search result in My Collection.

1 Like
11

Thanks for the additional info and videos @Donn

12

Hi @Donn, I discussed this again with engineering and this is still expected behaviour as far as they can tell.

  • Locating a track from Search results will work if the track is also in My Collection
  • Same for Match
13

Hi Slak_Jaw,

Thanks for looking into this. The expected behavior makes sense! If you Locate a track that was loaded from Match or Search it would show in My Collection vs when you Locate a track from a Playlist it would show in that particular playlist you loaded from, so far so good. I was just pointing out the expected behavior is random. Sometimes it doesn’t locate a track that was loaded from a search result, Match, or Playlist. When you trigger the Locate command it doesn’t locate in My Collection or Playlist (as in the first video)

Thanks!

14

Hi @Donn, so you’re saying locate sometimes doesn’t work from Match/Search results even if the exact same track is in My Collection?

15

Yes that’s correct.

All tracks I play are in Djay’s My Collection, (I always import to My Collection and make playlists from there). When Locate works as expected, it finds tracks on deck 1 and 2 no matter where I loaded the track from, Match, Search, Playlist, any tab in the sidebar.

The issue is sometimes it only locates only one deck (and the track on the other deck not being located could’ve been loaded from anywhere, Match, Search, Playlist, sidebar).