Scratch Live Articles
How-to: Troubleshoot Crashes by Josh Lloyd, Serato
Crashing Troubleshooter
This troubleshooter guide has some tips to try and solve crashing problems using Scratch Live, ITCH or Serato DJ Intro.
The first step is to ensure you're running the most recent version of your Serato DJ software. To check what the most recent version is, go to the downloads page:
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:
- Disconnect your Scratch Live/ ITCH/Serato DJ Intro hardware.
- Click on 'analyze files' button to analyze your whole library (This can take some time with a large library).
- Click on your ALL.... crate
- Click on the first empty box of your library's column header to group files by type.
- Delete all files marked with the 'corrupt' icon:
NOTE: Make sure you don't re-import these corrupt tracks into your Scratch Live / ITCH / Serato DJ Intro 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 NOT when the program freezes or when you have to force quit the application.
Crash logs can be found here:
- Under Windows XP you need to have Dr Watson enabled to log crash dumps. Read the guide to do that: here.
- For Windows Vista and Windows 7, read the guide: here.
- Under Mac OS X, read the guide: here.
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.If this works, it would be helpful to attach your corrupt database file to your help thread for Serato for analysis.
