new waves sampler out !!!! and waves sample browser !!!

[Sinisterbr]

I think it sounds really great. Actually, it sounds like there is some kind of (very good) saturation in the sound, making it very "velvety" (no, it's not the filter drive knob). But I just tried the factory presets (and samples) until now, I don't know if imported samples will sound as good.

[Sinisterbr]

And I think it sounds better than Form, but not better than Iris2. IMO

[Synth Master Jedi]

Some people on Mac + Mojave might encounter a Cosmos bug, where it can't connect to the Waves samples database after a restart.

I noticed this issue the day after I installed Cosmos and I wasn't sure if it was just my system or more wider spread because I didn't see anybody else mentioning the issue, but I was on gearslutz earlier and this issue has now been confirmed by multiple people there that are also on Mojave. So I now know it wasn't just me and my specific system.

I guess Waves will become aware of the issue and they'll come with a fix.

[DrFolder]

Cosmos does look nice, unfortunately it wan't that I log into my Waves account but won't do it. In the meaning as it's obviously not doing anything just saying "wrong password or username". Seems to be a common problem, since that it's in the Waves FAQs, their "solutions" are about as helpful as, yea well I can't think of anything as little helpful.

Anyone had this problem before? What can I do? Lay down and cry?

Edit: Nevermind, reboot did the trick. Leaving the comment here anyway. If you have this problem kind stranger, reboot your computer first

I had the same problem and found I was using my email as the username. My username wasn't my email address so I can log in now.

[unbrblncvncfbng]

First Waves instrument I've bought. I like it so far.

[bermudagold]

This gives some idea of the sound quality of the different modes...putting resource usage and business models aside...it looks well executed

by the way Waves rep states "COSMOS does not report any data back to Waves."
Appears you need to be online though....it seems the data sent over internet after opening the app and scanning a folder of only a few kb ( connecting to Waves site to verify the login)...why?

[GaryG]

However, when I add a new sample folder for Cosmos to index, it uses all my CPU cores at about 50% until it completes the scan. Some large folders take a while! And the RAM also takes a big bump up during that process. But after the scan, everything settles down, and I don't observe this during normal use.

I wondered that but it seemed to have completed it's scans. I installed it a couple of days ago and pointed it at a small 'essentials' folder with just a few thousand samples to test. I could search the samples ok so couldn't see any indication it was still scanning but cpu was still ~30%. Bear in mind this is an old laptop but generally handles audio stuff ok.

[Ah_Dziz]

How does this thing do CPU wise (I saw the mentions of big ram usebut I have plenty so that's not a problem)? Just curious if it is as efficient as one would imagine a simple sampler like this would be.
Like an 8 layer sound playing a big chord with all the mod sources engaged would do what to your CPU? For a similar setup (8 voices x 2 left hand notes and four right notes making 48 voices) in kontakt would barely register as anything happening. I like the quick workflow and simple draggable modulation so for quick resampling and sample based synthesis this is totally worth it.

I'm also curious if there's a list of the supported file types as well since they didn't get into that in the videos either.

Also does it have a setting where it just acts like a regular old sampler where it changes the speed and pitch by default. I watched both the videos and I'd pay 10 bucks for this, but I'm curious about those two things. Not particularly interested in the weird browser situation so that's not a factor for myself.

I suppose I can check out the manual and find out some of this.

Really just seeing how the different algorithms sound and if the workflow makes life more fun than using the Bitwig sampler will make up my mind. I can't imagine that I won't blow just ten bucks on it though.

[Sascha Franck]

Some people on Mac + Mojave might encounter a Cosmos bug, where it can't connect to the Waves samples database after a restart.

I noticed this issue the day after I installed Cosmos and I wasn't sure if it was just my system or more wider spread because I didn't see anybody else mentioning the issue, but I was on gearslutz earlier and this issue has now been confirmed by multiple people there that are also on Mojave. So I now know it wasn't just me and my specific system.

I guess Waves will become aware of the issue and they'll come with a fix.

Precisely the issue for me (I'm on Mojave as well), have been in contact with Waves' support ever since it happened for the first time. The supposed fix was to delete some files (WavesLocalServer, WavesPluginServer and Cosmos, IIRC), then reinstall CR8. Which fixed it indeed - but only until the next login/reboot. Tried 3 times by now, 100% reproduceable.

Same thing applies: Great algorithms but pretty much p*ss poor quality assurance.

As said, CR8 could be killler, but with (at least) a whooping 800MB of RAM useage per instance, it clearly has a potential to get in your way. Also, the lack of a voice stealing implementation (alternatively: allow for more voices) is a shame.

With Cosmos it's similar. Absolutely excellent auto-tagging algorithm, at least from my experience, but hasn't been tested properly. I mean, right now there's still plenty of people with 5,1 MPs and with Mojave being the last supported version of macOS on those machines, they should rather test things properly (especially given that Waves claims compatibility).
Add to this the poor sample playback engine in Cosmos - I mean, just compare it to the (free and also most excellent) ADSR Sample Manager. Allows for MIDI input, runs as a plugin, has several options to play back a file, etc. - way easier to find out whether a certain sample will suit your needs.

Unfortunately, I don't think Waves will do much about it, simply because they never do. Gotta wait for whatever general version jump (from V13 to V14 or something).

Oh - whoops, I may eat my words: Noticed there's a Cosmos update available in Waves Central. Now, let's see whether that fixes things. BRB.

[Sascha Franck]

So, back from updating and restarting. Worked straight after updating, once rebooted we're back to square one.
This is quite embarassing for Waves - I mean, in case the update fixes things and just a simple reboot spoils it again, a potential fix must be pretty easy. Just tell the damn thing to not do anything when rebooting.

[Synth Master Jedi]

So, back from updating and restarting. Worked straight after updating, once rebooted we're back to square one.
This is quite embarassing for Waves - I mean, in case the update fixes things and just a simple reboot spoils it again, a potential fix must be pretty easy. Just tell the damn thing to not do anything when rebooting.

After I read your post I opened Waves Central to check, but I didn't see any update for Cosmos there. The version listed still says 13.0.0

Does yours say something else like 13.0.1 or something?

[Sascha Franck]

After I read your post I opened Waves Central to check, but I didn't see any update for Cosmos there. The version listed still says 13.0.0

Does yours say something else like 13.0.1 or something?

Hm, still says 13.0.0 indeed - no idea why it was listed as updateable. Anyhow, just installing it on top fixes the Mojave issue everytime in both standalone mode and as a part of CR8 - until you reboot. Then it's all not working again.
Programmingwise, this is an extremely lousy affair. And I'm actually wondering what kinda userdata-gathering-BS (or whatever it might be) Waves had on their minds this time. I mean, what could possibly be the reason for a program to somewhat check your OS login status and change whatever it might be based on that status changing every once in a while?

Seriously, great algorithms, incredibly bad quality assurance.

[zzz00m]

And I'm actually wondering what kinda userdata-gathering-BS (or whatever it might be) Waves had on their minds this time. I mean, what could possibly be the reason for a program to somewhat check your OS login status and change whatever it might be based on that status changing every once in a while?

I'm wondering why they require you to sign in online with the Cosmos app? However, that appears to be all that they're doing. The WavesLocalServer briefly contacts the Waves registration server. Then disconnects.

So as I test I disabled my wi-fi connection and then was unable to login to Cosmos, after a re-install. It does need a network connection to login a user session. But then the wi-fi can be dropped and Cosmos stays activated.

[Sascha Franck]

I'm wondering why they require you to sign in online with the Cosmos app?

I actually don't exactly have a problem with that. Maybe it's because they're as well preparing a new Loopcloud-kinda content-selling shop or somesuch. Who knows.
Also, they have your details already anyway as you need to log into your account to install anything anyway (using Waves Central).

Personally, I find the reboot-and-everything-fails issue much more concerning. I mean, why on earth would an app that I've closed before watch my reboots?

[ians]

I'm wondering if there is going to be a Pro version of this? More capable & able to download new sounds & patches directly from the server, which is why it needs to dial in. Kinda like the Loopmasters thing or the NI Sounds idea.