Software help archive
sl crashes when analyzing files and rescanning tags
Support
sl crashes when analyzing files and rescanning tags
A read-only archive of old serato.com help threads.
sl crashes when analyzing files and rescanning tags
Product
Scratch Live
Version
2.3.3
Hardware
Rane SL1
Computer
PC
OS
Platform
-
mud_mouthed
10:17 PM - 22 February, 2012
Having some trouble I think it's a bad .Mp3 or .Wav file but I'm not sure. SL keeps crashing, this happens both when I'm analyzing files and when I rescan my library.
I'm running windows 7, using a Core 2 duo 2.4Ghz 3g ram and a 2tb external usb 3.0 hard drive with plenty of space.
Already deleted all the corrupted files that are showing up, please help.
Thanks!
I'm running windows 7, using a Core 2 duo 2.4Ghz 3g ram and a 2tb external usb 3.0 hard drive with plenty of space.
Already deleted all the corrupted files that are showing up, please help.
Thanks!
RafaelM
11:00 PM - 22 February, 2012
Def. looks like more corrupt files :(
If the analizer is crashing, then it cant analyze all the Files and technically you will never know how many corrupt files are remaining.
So first, we need to figure out which files are causing the analizer to crash.
Do this:
Close Scratch Live
Go to the C:/Music/_Serato_ folder and open the OverviewBuilder.Log
Leave this open and set it to the side where it is visible, but only takes up half of your screen.
Open the Scratch Live program and also minimize it so it doesnt take up the whole screen.
You should now have the OverviewBuilder.Log visible to your left and Scratch Live visible to your right.
Hold down the Ctrl Key and at the same time, click on the Analyze Files button in Scratch Live.
This will start to re-analyze all your files.
As you should notice, the OvervieBuilder.Log will start to list every single song that is being analyzed - one by one.
If Scratch Live crashes while analyzing, the OverviewBuilder will still be open and the last song in the list is the corrupt file. Re-open Scratch Live, locate this file, delete it from the ALL Crate and continue.
Repeat untill all songs have been fully analyzed. Stability should return.
If the analizer is crashing, then it cant analyze all the Files and technically you will never know how many corrupt files are remaining.
So first, we need to figure out which files are causing the analizer to crash.
Do this:
Close Scratch Live
Go to the C:/Music/_Serato_ folder and open the OverviewBuilder.Log
Leave this open and set it to the side where it is visible, but only takes up half of your screen.
Open the Scratch Live program and also minimize it so it doesnt take up the whole screen.
You should now have the OverviewBuilder.Log visible to your left and Scratch Live visible to your right.
Hold down the Ctrl Key and at the same time, click on the Analyze Files button in Scratch Live.
This will start to re-analyze all your files.
As you should notice, the OvervieBuilder.Log will start to list every single song that is being analyzed - one by one.
If Scratch Live crashes while analyzing, the OverviewBuilder will still be open and the last song in the list is the corrupt file. Re-open Scratch Live, locate this file, delete it from the ALL Crate and continue.
Repeat untill all songs have been fully analyzed. Stability should return.
mud_mouthed
1:25 AM - 27 February, 2012
OverviewBuilder.Log isn't updating as sl goes through songs. Any ideas why?
RafaelM
5:32 PM - 27 February, 2012
On a Mac I have seen it update as its analyzing. On a Windows machine it will update once Scratch live is closed.
Regardless, try closing Scratch live after it has analyzed and then open the OverViewBuilder. That should do it.
Regardless, try closing Scratch live after it has analyzed and then open the OverViewBuilder. That should do it.
mud_mouthed
7:04 PM - 27 February, 2012
I found a huge amount of corrupt mp3's. Got rid of close to 10g. SL didn't crash and said it completed analyzing all 60,000+ tracks. But I went to rescan tags and it crashed again.
Really confusing.
Really confusing.
RafaelM
7:08 PM - 27 February, 2012
Theres no need to rescan tags after analyzing -- analyzing does this. Analyzing is the most important, if it successfully analyzes - it should play fine.
Play with it and see if it crashes.
Play with it and see if it crashes.