Hey all, I've committed a fix for library searching, specifically how dirty tracks are searched. Dirty tracks are not searched with the same SQL logic as the rest of the library, so sometimes tracks would appear when they shouldn't, or not appear when they should. With this fix, dirty tracks should now respond to all the same semantics as the rest of the library, including field searches ("bpm:120-140", etc)
Let me know if there are any searches that don't behave correctly. cheers, Owen ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel