Parawave Rapid Discussion Thread II

[docbot]

That's the reason why developers like u-he win the KVR awards. They are transparent and open about their ongoings/developments, what's next and what to expect (even if takes longer).

Parawave on the other side locks their thread, doesn't reply to emails (mine), and releases an update (while 1.9 should be in the works since 2+ years), without any public communication.
I'm quite sad, since I think the product will maybe die slowly. It's really a good synth in workflow and sound, buts since no further communication means in my eyes, there's no big interest in keeping the community alive and hoping for a release soon.

I mean even Tone2 announces new development updates regularly, even though he is not well and doesn't want to go to the forums anymore. I can fully understand that.

Hopefully Parawave will come back and comment what's up/cooking, if it would mean we have to wait another few months till 1.9 or 2.0 whatever comes out.

this doesn't make sense considering Parawave has a public feature road map on their website. Not every Synth is as popular as Serum, doesn't mean Rapid is abandonware.

[zvenx]

and yep. BF sale is on
https://parawave-audio.com/rapid_synth
rsp

[parawave]

Sorry for not being all that active here. Of course we're aware that continuous communication would be preferable for some very social folks here. But the initial release & feedback phase went stale after a few years.
There was every possible feature request gathered. Some were implemented, like the big granular update. Some are still planned -> MSEG. Some were abandoned, like a Wavetable Editor. To be honest, at this point there isn't much to gain here or to show. On both sides. This showed at the end, when the discussion wasn't constructive anymore.
Under the hood development isn't all that exciting. And there aren't any flashy screenshots or videos to show. These will be created after the release of major versions, like the 1.8 Granular Synthesis showcase. It's just that a big part of Rapids development is reiterating on ideas and designs and experimenting with a good and easy workflow that still offers complexity when desired and guarantees that the performance gets not degraded by bloat.
The MSEG Editor for example is already implemented and working. It's just not fully integrated with the other new systems, because they are still subject to change. It almost made it into this release, but it would be more confusing to change the workflow after that again.

Rapid developers are very quite (on all platforms, facebook, twitter etc) but the synth still works great and sounds great. No regrets here.

No regrets here also so far, but I must say I’m a bit worried that they could close for good, because activations when reinstalling...

And since it’s one of my mainly used synths, this could stop me from doing a fresh new setup if activation isn’t guaranteed to succeed...

Parawave, are you still around please ? Is everything OK ?

I know this is a common problem for game servers, or very old products from "another era". They just stop and users are screwed. But to calm your nerves. There is no reason or incentive to stop the service or compatibility updates. We love our synth and will continue updating it. Even if it's just for our own use.
The recent update was not intended to be flashy but to guarantee exactly this ongoing compatibility and resolve the recently reported issues.

Hope you guys still have fun using it. As always, I would love to see the stuff you create. It's motivating to see users getting inspired or have fun using Rapid

[HcDoom]

Cant wait for MSEGs - I love Rapid and will continue to use it. Great work, Parawave!!!

[coLsky]

Sorry for not being all that active here. Of course we're aware that continuous communication would be preferable for some very social folks here. But the initial release & feedback phase went stale after a few years.
There was every possible feature request gathered. Some were implemented, like the big granular update. Some are still planned -> MSEG. Some were abandoned, like a Wavetable Editor. To be honest, at this point there isn't much to gain here or to show. On both sides. This showed at the end, when the discussion wasn't constructive anymore.
Under the hood development isn't all that exciting. And there aren't any flashy screenshots or videos to show. These will be created after the release of major versions, like the 1.8 Granular Synthesis showcase. It's just that a big part of Rapids development is reiterating on ideas and designs and experimenting with a good and easy workflow that still offers complexity when desired and guarantees that the performance gets not degraded by bloat.
The MSEG Editor for example is already implemented and working. It's just not fully integrated with the other new systems, because they are still subject to change. It almost made it into this release, but it would be more confusing to change the workflow after that again.

Rapid developers are very quite (on all platforms, facebook, twitter etc) but the synth still works great and sounds great. No regrets here.

No regrets here also so far, but I must say I’m a bit worried that they could close for good, because activations when reinstalling...

And since it’s one of my mainly used synths, this could stop me from doing a fresh new setup if activation isn’t guaranteed to succeed...

Parawave, are you still around please ? Is everything OK ?

I know this is a common problem for game servers, or very old products from "another era". They just stop and users are screwed. But to calm your nerves. There is no reason or incentive to stop the service or compatibility updates. We love our synth and will continue updating it. Even if it's just for our own use.
The recent update was not intended to be flashy but to guarantee exactly this ongoing compatibility and resolve the recently reported issues.

Hope you guys still have fun using it. As always, I would love to see the stuff you create. It's motivating to see users getting inspired or have fun using Rapid

Oh, I am so glad to see your post. And now I have question about it.
"I would love to see the stuff you create."

When you guys listen to the sounds produced or sound design demo by using Rapid.
Do you guys never comment what you think about it?

[Caine123]

What sucks is the sample management still sadly... importing samples is so clunky.

I love rapid, it is also so fast and stable. I prefer it in many ways over avenger. But it sucks with some basic stuff i dont get why it wasnt improved/updated so long ago.

I have mixed feelings with it and the communication here but i also get that there isnt much cause well it is what it is and you buy a product like it is so if i wouldnt have liked it i wouldnt have bought it. Still so much wasted potential.

[zvenx]

I for one would also appreciate more Rapid Extensions aka Soundbanks for it.
rsp

[HcDoom]

What sucks is the sample management still sadly... importing samples is so clunky.

Have to agree with this one - as much I love Rapid, importing samples is really pain in the a55. With new MSEGs and fixed sample import, this will probably be my only synth.

[mi-os]

I know this is a common problem for game servers, or very old products from "another era". They just stop and users are screwed. But to calm your nerves. There is no reason or incentive to stop the service or compatibility updates.

I don't know. I did consider Rapid several times but never bought it because of c/r copy protection. I also stopped or slowed buying from other companies because of it. I already have many licences that became useless because the company is dead or product support is pulled (eg NI).

[Gam456]

I know this is a common problem for game servers, or very old products from "another era". They just stop and users are screwed. But to calm your nerves. There is no reason or incentive to stop the service or compatibility updates.

I don't know. I did consider Rapid several times but never bought it because of c/r copy protection. I

What are talking about ?
It's just a serial number, there no iLok, no manager

[chk071]

He probably means the activation process, described in the manual: https://parawave-audio.com/public-downl ... Manual.pdf

You know, the stuff no normal person cares about, but inhabitants of the internet somehow deem vitally important.

[dermage]

I know this is a common problem for game servers, or very old products from "another era". They just stop and users are screwed. But to calm your nerves. There is no reason or incentive to stop the service or compatibility updates.

I don't know. I did consider Rapid several times but never bought it because of c/r copy protection. I

What are talking about ?
It's just a serial number, there no iLok, no manager

Unfortunately it's challenge/response. You enter the serial, then a link to the homepage comes up, where you have to click and download a license file which gets generated for your computer id.
I have to go through the process several times a year, since it self-deactivates after certain Windows updates

To the dev, please consider adding an automatic noise burst when it has auto-deactivated, so I know it has deactivated. It just stays silent, I'm not noticing it straight away, and miss it sometimes. Thanks.

And thanks for coming back and re-emphasizing that you still work on the synth.

[THE INTRANCER]

He probably means the activation process, described in the manual: https://parawave-audio.com/public-downl ... Manual.pdf

You know, the stuff no normal person cares about, but inhabitants of the internet somehow deem vitally important.

It's not the activation process (most plugins require some activation), it's the deactivation of the product you encounter and the pain in the ass it is. I've a ton of plugins and none of them do this.

Given how regular Parawave Rapid deactivates itself. I would advise people not to buy it because of this, even at 50% discount.

Parawave doesn't care about changing this.

[HcDoom]

Never had deactivation issues on Windows…works flawlessly.

[dermage]

Unfortunately he is right about the annoyance of auto-deactivating on Windows. I'm not sure what I'm doing wrong. But it happens on both my computers. Both Win 10 22H2. It's not on each Windows Update, but it happens several times a year.