song list

[simpmech]

anyway to "cheat" the amount of songs displayed by a laptop? just seeing if I can help the user to be able to "browse". Some people like to see more options rather than have to "know" the songs they are searching for. any ideas?

[dave]

you can edit the "secret prefs" and set the number as high as you want. Note that a big list will take a long time, and the user may hit "submit" 20 times by then thinking it's not working, and cause your computer to crawl be sure to keep the tasks window open so you know when people are searching.

[simpmech]

ty

[DeusExMachina]

Dave:
FYI, I set mine to almost 700, without any noticeable slow down.

[DeusExMachina]

Large list or small, it takes on average 12 seconds to return results. (Mode average. Sometimes it can take as long as 5 minutes, even with the pref set low. No idea why.)

[dave]

there's something wrong with your LAN

[DeusExMachina]

Pretty sure that isn't the issue. It is not just in server. It is on the host side. The search actually takes that long. Even if I do it locally on my machine.
It often happens when I first start up. Other times, when it will cause maximum disruption, kJams appears to know!

[dave]

hmm, if it really is taking 12 seconds AFTER the search progress bar has finished, ie: it takes ALL that time to transmit the results, then it is either the server or the network. but yes, if you're doing the test on "localhost" you're eliminating the network as a possibility, ergo it must be the server.

if you can reproduce this reliably, i'd like to do some tests. i can put in timers (which will be logged) so you'll get a report of how long each action takes, like this:

search collation: 6.28 seconds
results transmission: 2.13 seconds

or something?

[DeusExMachina]

There is a miscommunication here. It is not the transmission of results that takes 12 seconds, it is the actual search. Transmission of results is essentially instantaneous, even with 700 items returned, a la a search for "Beatles".
Occasionally, however, the actual search can take far longer, on the order of minutes, even when it is the only search. Once the filter is complete, however, results arrive at the remote machine almost immediately.

[dave]

Can those of us "in the know", and we know who we are, please stop beating the already dead horse of "slow searching". Let's just not even mention it or refer to it in a roundabout way. The horse is dead. We're already training Shadowfax. Talking about the old horse is evidently confusing for the poor trainers.

edit: that was an attempt at humor, BTW, which i must simulate, lacking the proper built-in functions. For I, myself, am in fact the "confused, poor trainer".

[DeusExMachina]

Well, no need to call PETA. My point was simply that setting the secret pref to astronomically high values does not appear to affect search times in any appreciable way, nor the time it takes for server to transmit the results.

[dave]

very well. i will likely be lifting the limit with the 'fast search' thing anyway.

[natblend]

Wow.
I've not seen any mention of this. but the last version of Lite makes the search instantaneous.
Well done.
Now the teens waiting to see if I have their song won't think I'm a complete idiot.

Thanks.

[dave]

Nat: well you should know then that it's NOT bug free. please see the list of caveats:

https://karaoke.kjams.com/wiki/Slow_Searching/testing

[natblend]

Here's a screen shot of the error message I get when I move a file from one playlist folder to another.
I like using empty playlists, a,aa, etc.
No crash during all that.
http://members.cox.net/kfva/k1.jpg
Also, I added a new song to the library, it took several seconds, but worked okay.
After all that, When I did a restart during a break, it crashed instead of quitting.
Started up just fine.

So, it's working, just a few minor bugs.