Search refreshes a split second after hitting view to go back to

  • Software or Firmware Version: (1.2, 1.3.1, etc…)

1.4 b2

  • Steps to Reproduce: (Turn on unit, press button X, etc…)

Do a search. Wait a few minutes or play the track. Hit view to go back to search.

  • Expected Result: (ex: It does X…)

The same search list as before.

  • Actual Result: (ex: It does Y…)

For a split second it shows the search results list from before then it refreshes it and this takes time that’s unnecessary.

  • Reproducibility: (ex: Happens 1 out of 10 times.)

8 out of 10 times or so. Doesn’t happen if you hit view quickly.

  • Other Relevant Configuration Info: (ex: Plugged into a Windows 10 laptop.)

  • Operating System & Version (if applicable):

  • Link to Video Repro:




A split second?

I’m surprised that you’ve not given the timing to a few decimal places, since 0.000000000 is really important.

No, dude. It actually shows the ORIGINAL SEARCH for a split second when you later hit view again. I expect the original search to show up and show up immediately, which it actually very briefly does. So the search from the prior track loading is still in memory, but then the unit decides for some odd reason to re-run the search from scratch again, which takes substantially longer than a split second. The split second is just the inadequate time I have to utilize the original search prior to it refreshing, but it’s obviously too short to do anything with.

Bugged me also sometimes since you have to wait a few seconds to load another version of the same search. Logical would be a search runs only when input is changed. Or cleared when pressing the search icon or X. Switching view could just show the search already performed until changes are made

1 Like

If you keep the search up on both decks most of the time, you can actually watch it keep refreshing over and over again strangely. I saw it do this like 4 or 5 times during one pair of tracks playing out together. I had the idea maybe keeping it up on the screen would prevent it… the opposite happened.

1 Like

Yeah experiencing this too. It can become rather nerve-racking too during a gig. : /


I can confirm same behavior on my players as well.

One second I’m looking at where I want to be eg 100bpm tracks , next it jumps back to the top of the list 43bpm region.

Please fix ASAP.

It even does this when looking at tracks in a crate sorted


I have started having this issue as of our most recent update. If I switch to any tab (or view) from the search results, the search results completely reset and it takes another 5-8 seconds for them to appear again.

At least some of the time this might have something to do with the played track highlighting, because sometimes a track that’s been played screws up the list and jumps to the top or bottom. So it could maybe have to do with that. This highlighting certainly shouldn’t be changing the sort order, but I know that sometimes happens. Anyway, half the time the played track highlighting either doesn’t work or doesn’t transmit across link even with its other glitches. Every player should obviously transmit played track info to every other player in the (great) link… RIP René Auberjonois.

I tied it to the track being marked as “played” too.

I found that putting your finger on a highlighted track in the list and without taking your finger off, wiggle it left and right for a few seconds and it doesn’t reset. As long as it’s in motion it wont reset.

It’s frustrating.

I’m not fussed about a moment or two here or there. Wonder if the refresh occur as other decks and layers in the network could modify the tracks in the search list. Like adding hot queues, loops and all.

It actually does it a lot… even if you have the list up on screen the whole time and don’t even go to the HUD and back.

Yeah, it may be other things causing it, too, but really none of these things should be changing the list at all, even the order, let alone it completely re-doing the search or sort from scratch, which is what it seems to be doing, as if the buffer is being cleared or something for lack of memory or something while it’s doing other tasks.

This is how I experience it… Only on the linked deck…

YES. Major issue. If you accidentally touch the screen when it does this, you’re stuck back at 43 bpm