Only recently I noticed that the internal search bar triggers a “beach ball” with a total stall of the UI (while playback continues without any problems) for several minutes before the results are shown.
Admittedly, I have a large library with nearly 100K tracks, but I’ve never had this behaviour before, and it really shouldn’t happen on an M1 processor.
I’ve done all database maintenance steps several times. No change. Whenever I start to type in the search filed, Audirvana goes immediately to “non responding”, blocking an entire core for several minutes.