Jaikoz- Discussion Forum

OK, that´s true, but please think about the update function for MB data. It is not really comfortable to load only 10 or 20% into Jaikoz try to update them and so on.
I also don´t like to see Jaikoz as a Mediaplayer, but for the update process it´s necessary to have the right performance.

Also it takes some weeks or month to have all files really good tagged, because of missing metadata in MB right now.

Paul,

I have been reading over numerous post regarding the running out of memory error. This is one that I have been struggling with for a year. I think if there was a basic "strategy" on how to tackle a HUGE number of files it might help users out.

For instance, my scenario:

Mac 10.5.5 running Jai 2.7.0

1.) I have consolidated three HDD to one 1TB external drive.
2.) 50,000 songs
3.) mostly MP3
4.) Numerous songs duplicated 2-3-4 times

If I do batches of say 1000 on the new drive and DONOT change the base folder nor "fix" the subfolder it works okay.

But if I start to mess with the file name and folder, then if this exists already on the HDD but not loaded then Jai will give you the cannot over write file error.

So i guess if you could come up with a basic "strategy" on how to tackle something like my scenario it would probably help. Just my thoughts. keep up the work, this is the best product I have used for music and continue to be a disciple.

Chuck

Great tip. Been having huge performance issues with my mac while Jaikoz has been running with both the program running out of memory and the whole computer becoming unusable.

I have been trying to load and tag about 20000 songs. I increased the allocated RAM to 4Gb. The program and whole computer are running miles better. It seems the app is only using 1.89Gb, and the rest of the computer is smooth as ever. It also seems to be using less processing power to do the same job faster. It would be awesome if this was a configuration option in the prefs pane so that more users would know about it.