Software help archive

Support
dropouts online overview building
A read-only archive of old serato.com help threads.

dropouts online overview building

Product
Scratch Live
Version
1.9.2
Hardware
Rane TTM 57SL
Computer
PC
OS
Platform
-
Technocrate 11:08 PM - 12 March, 2010
Product: scratchlive
Version: 1.9.2
Hardware: rane-ttm57sl
Computer: pc
OS Version: xp
---

Hi I am getting a dropout every 10 secs when the file loaded does not have an overview built. 1.9.2 XP sp3

Ok i'm using an athlon.. this could be a problem, although i don't see why.

Tracks with overviews built do not cause dropouts.. It's either the online overview builder itself or the process that updates the waveform display. That is, each time it shows that a bit of the overview has been built, i get a dropout in sync with the display update.

turning off autofill overviews only reduces the rate at which the dropouts occur.
Technocrate 11:11 PM - 12 March, 2010
Otherwise it's been working great.. another solid release.. looking forward to 2.0!!!
djdannyd 2:11 AM - 13 March, 2010
You should build overviews on "ALL" tracks. That's what's probably causing your problem with drop-outs. When a track is loaded as your spinning without the overviews built, it is also trying to scan it at the same time, therefore using more CPU power and probably over loading the usb port being used. There are a couple more benefits overbuilding your tracks like detecting the song's bpm and showing you corrupted files (to be deleted from your library).

Does it makes sense? I think I confused myself a little...
Serato, Forum Moderator
Michael R 11:39 PM - 14 March, 2010
Hi Technocrate,

djdannyd is correct - if your files aren't analyzed, Scratch Live will do it while you play. This uses extra CPU and can cause dropouts. If you analyze your new files once you've added them to your library you'll be able to avoid this issue :)
Technocrate 8:57 AM - 15 March, 2010
ah thanks.. i'm a bit rusty..
Serato, Forum Moderator
Michael R 9:12 PM - 15 March, 2010
No worries at all :)

Issue resolved, thread closed.