A possible way to speed up the library search responsiveness?
Just trying 0.7.0rc2 and notice that the library search is much better but it does seem to cause the app to freeze up every now and then.
Freezes seem to occur when searching for three or less characters. For example, if I quickly type in "Bob Marley" then the results come back fast. If I just enter "Bob" then I get 100% CPU usage and Songbird freezes for anything up to a minute.
Could the search only take place for 4 or more characters or would that limit people too much?
Also, I have noticed that the library search also searches the comments field in the ID3 tags - does this slow things down somewhat? Would it not make more sense just to search on Title, Artist, Album, Genre, Year and File Name?
Just some ideas... loving RC2 :)
Freezes seem to occur when searching for three or less characters. For example, if I quickly type in "Bob Marley" then the results come back fast. If I just enter "Bob" then I get 100% CPU usage and Songbird freezes for anything up to a minute.
Could the search only take place for 4 or more characters or would that limit people too much?
Also, I have noticed that the library search also searches the comments field in the ID3 tags - does this slow things down somewhat? Would it not make more sense just to search on Title, Artist, Album, Genre, Year and File Name?
Just some ideas... loving RC2 :)
6
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
-
Inappropriate?Your previous discussion on forum was reported in a Bug #9929 which was a duplicate of another bug.
You can track the comments on this work item by:
1. Going to the "people" box in the upper right hand corner of Bug #9646
2. Add your email in the "add cc" box
3. Scroll down and hit commit.
If you don't have a free bugzilla account, signing up is quick and easy and will allow you to share your feedback directly with the development team -
Inappropriate?Making the search to start after adding 4 letters is not going to help.
We search through a db using FullTextSearch.
This is causing the lock up in a large libraries. -
Inappropriate?Thanks for the reply Boris - I have signed up to bugzilla and added myself to the CC list.
I’m a bugzilla user
-
Inappropriate?Slate8: Good news! We're definitely spending time on our next release to improve searching functionality. It will be a few months before we roll out those changes, but it's in the works. :)
-
Inappropriate?I was thinking, what if songbird only searches when you hit "Enter" and not on every text change? Evolution works that way and is easy to remember after a little.
I mean, doing only a FullTextSearch, instead of many, can help when your library is tooooooooo long, like me.
I’m trying to help
-
Inappropriate?Sorry to dredge up an old one, but I'm still getting this search issue. In fact it never went away and still occurs on 1.0 and the 1.1 nightlies.
I notice Bug #9646 has been marked as fixed - should I append my issues to this bug or file a new one?
Does anyone else still get this?
I’m freezing
1 person thinks
this is one of the best points
-
Inappropriate?Problem persists even with 1.1.1!
-
Inappropriate?Yup - I sill get this with 1.1.1 too... I'm going to try out a few things with my library and see if it's related to the number of tracks or a specific album or file...
-
Inappropriate?The simpliest way to improove search responsobility is to make delay on auto search. Now it's like you can typein 3-5 char before it's stuck, if you make delay about 1 or 1,5 second you can typein 5-10 chars and this make possible to search once and get more adequate results. Delay - it's time from first keypress in search field after focus is set on till auto search will be started.
-
Inappropriate?Why on earth dont you add a "press enter" ability?
This is nuts, Im leaving songbird for good if you dont fix the search, thats the main feature for gods sake.
Loading Profile...






