You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd love to have a possibility to save a search query as a "view" (like a DB view) to be able to reuse it quickly.
The search bar has a history feature build in, which is great, but when used often, the query I'd like to reuse is practically impossible to use after searching some songs by name, because it is too far down in the drop-down menu.
I'd love to have the option to save queries like bpm:>120 bpm:<130 -genre:blues rating:>3 etc. and be able to access them quickly like playlists or crates in the tree of the media where Playlists, Creates, ... are. Something like Views might be added and under that saved queries which would execute on the Tracks or more universally Viewes under any searchable part of the tree.
The text was updated successfully, but these errors were encountered:
Hi,
I'm working on smarties in my pr #13, if you're able to build Mixxx yourself you can try / test it. It's still a WiP, all the desired features are integrated (as in iTunes but more), now streamlining logic.
You can test it and give me feedback?
Feature Description
I'd love to have a possibility to save a search query as a "view" (like a DB view) to be able to reuse it quickly.
The search bar has a history feature build in, which is great, but when used often, the query I'd like to reuse is practically impossible to use after searching some songs by name, because it is too far down in the drop-down menu.
I'd love to have the option to save queries like
bpm:>120 bpm:<130 -genre:blues rating:>3
etc. and be able to access them quickly like playlists or crates in the tree of the media wherePlaylists
,Creates
, ... are. Something likeViews
might be added and under that saved queries which would execute on theTracks
or more universallyViewes
under any searchable part of the tree.The text was updated successfully, but these errors were encountered: