Browsing from Sample and previewing those Sample should be synced. Even if it’s “only” the CR8 Companion (and to be honest Cosmos should come also as a plugin, common guys watch loopcloud), the workflow experience is not good. We need to have an idea of how will sound the sample (especially the loops) at the previewing stage.
To be able to feel how the sound will fit after loading it in CR8 is a deal breaker to me.
Even if Cosmos on the paper is certainly something very powerful. it fails short to me even as a CR8 companion.
Please add that feature in the next version or update.
This is critical to me. (and i don’t see how it could not be critical for the others to be honest)
i don’t care if indexing take days (i have time, i want to use it, but as it is it’s not the best workflow)
I wrote this feature request because WAVES support told me i’m right on this.
(in short you have to load loops so CR8 then make it synced, but it’s not, at the previewing stage in COSMOS)
This is the only showstopper for me. Cosmos would be awesome and could easily replace Loopcloud, ADSR or even internal DAW browsers if it would support proper tempo-sync while previewing. Tbh I cant understand why they didn’t implement it already… ■■■■■■.
Thanks to Waves to finally add Sync to the DAW and within CR8 Sampler… This plus some great new additions is really a Game Changer to me ! Another room for improvement would be to speed up scanning user folders. Because now it’s adding a sync file for every loops to sync to the DAW it’s a wow moment when you realize how much time it will take… Could be days
The scanning has been sped up actually. There is still a problem that messes us up on Mac systems at least…
If you go navigating through your sample folders manually Cosmos would feel like it needs to sync again when it doesnt have to. This is because the system has updated the invisible .DStore file. It’s the changes invisible system files that trick Cosmos into needing a rescan. The same might also be true on Windows systems.
I reported this issue to Waves and they are NOW aware of the problem, so I imagine a fix is coming at some point. In the meantime I advise to avoid going through your system folders manually in the OS if possible.
hum interesting (good catch). I just thought (as I have a lot of data to scan) plus the fact that it adds for each sample a sync data file (like Ableton do) the process can take a while depending on the data weight…
Even though they’ve thrown in the weight of online server support behind Cosmos to speed up scanning it still can be a bit slow. The more sample data you have, the slower it is as you observed. But I think the real problem lies in those ever changing invisible files I mentioned above.