Hello!
I am a new user of kJams for OSX. I have been able to make the trial version of kJams Lite work with a small test library of mp3+g files. However, after importing my quite large library (100K+ songs) I find that the app locks up regularly. I can see that the import completed and the app reports that it has 100K+ songs available, but I cannot effectively search the library or even sort by artist or track name without locking up the app. Is there a limit on the number of songs in the library that can effectively be managed?
Me: MacBook Pro (~2008, Intel, etc), 4GB ram, OS 10.6
Any assistance would be appreciated. If I can get this all working smoothly, I intend to purchase the app.
erik
edit: When I say "locking up the app" I mean unable to use any app functions for 10+ minutes and requires using force quit to kill it. I don't have the version of the app, but it was downloaded from this site 4 days ago.
New User - Large mp3+g library
Re: New User - Large mp3+g library
1: make sure you have turned OFF "update search results as you type", you should not see it in your prefs in fact. hold the OPTION key while you bring up prefs, then go to "advanced", you'll see it there, make sure it is NOT checked.
2: hide any columns you do not need to search on, see Slow Searching
3: make sure you can see your tasks window. make sure it is NOT overlapped by any other window. when you do a search, you will see the task in there
4: sorting by name, artist and album: these should all automatically pre-sort on startup, so that when you go to sort by them, it is fast. the only reason it would have to re-sort is if you're changing meta data, which you usually do all at once, then stop doing it.
5: having said all that, 100k songs is *a lot*, i expect you have many duplicates.
6: i do plan to re-write the database using SQL, eventually
2: hide any columns you do not need to search on, see Slow Searching
3: make sure you can see your tasks window. make sure it is NOT overlapped by any other window. when you do a search, you will see the task in there
4: sorting by name, artist and album: these should all automatically pre-sort on startup, so that when you go to sort by them, it is fast. the only reason it would have to re-sort is if you're changing meta data, which you usually do all at once, then stop doing it.
5: having said all that, 100k songs is *a lot*, i expect you have many duplicates.
6: i do plan to re-write the database using SQL, eventually
Re: New User - Large mp3+g library
Thanks for the info Dave.
I will try these steps out later tonight and see if performance is positively impacted.
100K is "a lot"
The duplicates, however, are where I have the same song from multiple production houses (SoundChoice vs DK, etc, etc). No duplicates of songs by same house, except where the same song exists on multiple discs by same house.
erik
I will try these steps out later tonight and see if performance is positively impacted.
100K is "a lot"

erik
Re: New User - Large mp3+g library
right, you should get rid of the dupes except in the case where two different publishers both have a high quality version. typically only one version is the clear winner, delete the rest. and by that i mean "edit->trash original files", so they're really, really gone.