Earlier today, I realised that Cosmos had been updated and could be used as a VST, rather than the standalone it once was……so I updated the WUP and went from 13,0 to 16.0
I was eager to try it out, but it’s taken all day to scan 310,000 samples which took just a few hours in Loopmaster, which I unsubbed from. Cosmos sounded like the ideal way to make full use of all those samples, but this is sooooo slooooooow, and I have a great PC with 96gb of ram and a fast processor.
It finally got to 100%, and now it’s started “creating sync files”, which, by the looks of it, is going to take just as long, if not longer, than the first scan.
Waves, this is not good enough. I was supposed to be making music today, but I’ve had to spend my day watching this scan my drive at a snail’s pace.
I just hope it’s not creating a folder with duplicate files, and eating all my drive space as well ?
Hi @2ndMOUSE,
Welcome to the Waves Forum.
I see one of our support representatives already assisted you with the reported issue.
Feel free to share your solution and experience.
It took a while to scan, but I guess a quality scan just takes time, and it’s done right. Modern life has made me somewhat impatient, and that’s more about me than Waves. Apologies.
It did resolve well, and it’s very satisfying dragging the cursor over thousands of individual drum sounds to find the right one, and then just dragging it onto a channel. The one thing I can’t figure out is where all the drum loops are ?
I just scanned one huge folder that has over 400k samples in it, and although Cosmos did a great job separating all of those into categories, I don’t see any drum loops. I’m thinking I’ll have to do an additional scan of the few sub-folders that just contain those drum loops and nothing else ?
Cosmos has been a big help so far. I’ll use it mainly for finding individual kicks, snares and hats. I wonder if I can drag those samples straight onto Algonaut’s amazing Atlas plugin ?
What you need to avoid at the moment, at least on a Mac system, is manually searching through your folders on the desktop. It seems to update some invisible system file, “.DStore” in the case of Mac. The changes to that seems to trigger Cosmos’ unnecessary need to update. It’s quite possible it works the same way on Windows too.
I’ve let tech support know about it a few months back, but I’m unsure whether they’ve addressed this invisible file issue yet.