Scratch Live How-Tos

How-to: Troubleshoot Crashes

Crashing Troubleshooter


This troubleshooter guide has some tips to try and solve crashing problems using Scratch Live or ITCH.

The first step is to ensure you're running the most recent version of the Scratch Live or ITCH software. To check what the most recent version is, go to the downloads page:

Scratch Live Download here

ITCH Download here

 

Detecting and removing corrupt files

The most common cause of a crash is having a corrupt file in your music library.
You will need to make sure you have all your files analyzed and remove any files marked as corrupt.

To remove corrupt files: 

1. Disconnect your Scratch Live/ ITCH hardware.

2. Click on 'analyze files' button to analyze your whole library (This can take some time with a large library).

3. Click on your ALL.... crate

2. Click on the first empty box of your library's column header to group files by type.

3. Delete all files marked with the 'corrupt' icon:

 
Corrupt file icon
 

 




NOTE: Make sure you don't re-import these corrupt tracks into your Scratch Live / ITCH music library. It is wise to delete these files from your hard drive. If you want these tracks, you can either re-download, re-rip, or re-encode these tracks and then import these new versions (check these for corruption too).

 

Crash Logs

A useful thing to do if you're getting crashes and can't find a solution is to send Serato a crash log if possible.

NOTE: A crash is when the program shuts itself down and doesn't include program freezes or when you have to force quit the application.



Under Windows XP you need to have Dr Watson enabled to log crash dumps. Read the guide to do that: here.

 

For Windows Vista, read the guide: here.


Under Mac OS X the crash log will be located in:

~/Library/Logs/Crash Reporter/Scratch LIVE.log

or:

~/Library/Logs/Crash Reporter/ITCH.log


Attach any logs to your help request if you have one, or start a new help thread: here.



Your log will help Serato make the software as resistant to crashing as possible.

 

Renaming database.v2

Another possibility is your database file is corrupt. To test that, try renaming it as follows.

To rebuild your Database V2 file, follow the instructions in this article: here.


If this works, it would be helpful to attach your database file to your help thread for Serato for analysis.

Conclusion

If you've tried the processes in this guide and still experience crashing, we want to help. Login to the forum and start a topic in the help forum and support staff from Rane and Serato will assist in finding out what is going wrong.
More Scratch Live How-Tos | Print this How-To