Agreed.

Good idea.

Great Idea.

+1

and we should be able to sort the tracks with this flag, so we can easy drag & drop them to the button...

same for partially built overviews

Agreed. Great suggestions.

OK, how do we distinguish between tracks that have no overview and tracks that have an overview built in an earlier version that doesn't have autogain (for example)...

Well, if you store the version information in the track when it's overview has been built, then pick the last trusted previous version that is known to detect as many problem cases and set the cutoff there. Any tracks with overviews built with version before that cutoff should display a warning.

If you don't have version information from the time the overview is built, you have to ask yourself if you trust overviews from previous versions. If not, then start saving version information in the ID3 and make any tracks built with non-versioned ID3s show the warning (this won't make people happy).

The goal here is crash avoidance, so I wouldn't be particularly concerned about whether or not it has autobpm or track gain applied. That can always be done after the fact. The goal here is to *avoid crashes* by educating people. Many djs don't know that they're supposed to build overviews and then their machine crashes. This ultimate gives SSL a bad rep, even though it was the DJs "fault".

Mike

Forgot to add the case, if you the file has an overview built and you don't have version information, then don't mark it as missing it's overview, even if it doesn't have autogain. But this is assuming that you trust all previous versions of SSL to discover corrupt files.

I would also make this warning red... or much more noticeable than the current warnings. This is especially important because these files can cause SSL to crash, which is bad. Heck, those other warning signs should be brighter, too...

got it. nice one. I'll write it up.

+1

that would be great. I would love it if it showed the file was built in a previous version. I fricken hate how some of the DJ pools pre-build the overviews now!!

Why would you hate it if the overview is already built?

I use a different setting then them? It's annoying having to dig through tracks to figure out which ones are pre-built, which ones aren't, etc etc

What setting is that? The only option is whether to have auto-bpm or not. There are no other settings...

db level

bp range

incorrect, db level is only applied when loading the song.

yup.. there's no reason not to use the overviews built by someone else unless a later version of SSL detects errors that the version used to build the overview doesn't.

Autogain values are *always* built into the track, so you have no choice in that matter.

Also, bpm range is not stored in the track either - regardless, either the bpm value is right or wrong.. no rocket science there.

well all I know is most of the tracks I get that are pre-built are messed up for me. Either the BPM's will be off or the db levels are not what they should be.

unless they're using an old version of SSL to build the overviews and autogain isn't set, then the levels used for tracks are dependent on the value that you choose in setup. As for BPMs, they might not even be using SSL to do the BPM count.

Why don't you contact the company to ask them what version of SSL they're using. If they're using an old version, educate them.

That, or just clear the ID3 tags and then build your own overviews. That's what I do and then you know you're starting from a clean slate.