Comment 4 for bug 956934

I have been using it over the weekend, and the problem actually seems worse. process now runs continuously as soon as it's activated. not at 98% disk IO but at least 50%.

May I ask what it's doing? Shouldn't it take a few seconds to just scan all the filenames and index? Looking at how much disk IO it consumes, seems like it's reading the entire video file, over and over.