Yep, could be handy.

an easy way to do this would be to piggyback the prepare section.

My laptop is good, but chugging on a fresh batch of 50 new songs takes some time. I have a much more robust desktop PC that I'm thinking about loading SSL onto and having it do to the batch work.

How about a seperate program to run the MP3 batching?

why a seperate app? you don't need, in fact can't have, the box plugged in while batch building overviews anyway.

Thought that might be a touch of an infringement to have multiple copies in use. But hell with it - Josh said it was OK.

heh

fine with me KaGeN!

cool.

And I hope a new button will appear in futur version : Rebuild overviews.

So, in fact :

Build overviews :
Click on it : it build all files (of collection) that aren't already built.
Drag files/folders/crates on it : it build selected files (or files of selected folders/crates) that aren't already built.

Rebuild overviews :
Click on it : it rebuild all files (of collection) even if they are already built.
Drag files/folders/crates on it : it rebuild selected files (or files of selected folders/crates) even if they are already built.

I agree with Couin...

Do you need a function to make overviews for a subset of files? Isn't this only a problem until you have built all the overviews for your existing library? (granted, this will take a while if you have a big library). Once you have gone through your library, isn't just a matter of building overviews for new files as you add them?
Or, to put it another way, why would you not want the overviews built for your entire library?

mmm when i try to build overviews for new files, SSL reads the old ones again. at least, it reads a bunch of them (dont know why).

this issue makes building overview for new tracks really annonying...

Ok, I'm now about 12 hrs deep into building my overviews. I have about 42 gigs of music stored on my laptop and I add music just about daily. I can't go through this every time I add new songs. There simply aren't enough hours in the day. There has to be a function to build overviews only for tracks that don't already have them.

you'll only have to do this once for the new overviews (they've changed in the most recent release) once they're saved it will only build overviews for tracks which don't have them...

word - thats whats up. I was getting mixed information from other posts about this topic.