RAPID Synthesizer | Rapid 1.8.0 released | Free "SP - Granular Elements"

[Klinke1]

Ok, I did some further testing, and this is really strange.

Tested in the following DAWs:

Studio One v3.x
Bitwig Studio 1.3.x
FL Studio 12.x
Reaper 5.x
Renoise 3

The only one I got the panning correct in was FL Studio. It didn't take a rocket scientist to suspect the ASIO drivers, rather than the DAW, as it was working in FL Studio (which is running it's own ASIO drivers).

I changed the audio drivers in Studio One (which I use primarily) to the FL Studio ASIO drivers, and the panning was OK again. Also tested the ordinary Windows drivers (built-in motherbaord soundcard), and the panning was working OK with that driver too. So something with the ASIO drivers for my Roland UA-55 QUAD-CAPTURE.

However, Rapid is the first synth acting like this. Even the Oscillator balancer knob is swapped.

Other working synths are:

Aalto
Absynth
ACE
Arcsyn
Factory
Falcon
Hybrid3
KarmaFX Synth
LuSH-101
Predator
Serum
...
...
To be honest, every synth plugin I've tested where I could find a balance knob quickly.

So even if the ASIO driver is a part of it, it could rather as well be fixed in Rapid too.

Same here with Cubase8.5 and Maschine2:
The Osc balance/pan + BalanceFX pan is wrong
The dual delay settings: Turn up left feedback and the right feedback is adjusted.
(right is left..left is right)
The Rapid pingpong is also R->L and classic pingpong is L->R.

----------------------------------------------------
2. The first step of the Seq should also be smooth. (as set with the "smooth" parameter and like the rest of the steps.) .. It's not.

win10-64bit - Rapid 1.0.2.9

[v1o]

No more activities from Parawave website concerning RAPID Synthesizer (Windows) since long time, staying at v1.0.2, ignored sustain pedal remains unfixed..

Updates are still in development. I'm not a fan of daily/weekly updates. It's annoying for us AND customers. The next version will include cool new stuff. As long as there is no public announcement that development is discontinued, don't worry. Research, planning and testing just takes time.

Since TWO MONTHS you can't implement sustain pedal support? really is it a joke????
Is it too difficult to add "On/Off" checkbox from "Preferences" page? - oups, no "Preferences" page too... to enable or disable the sustain pedal, one of important feature like Modwheel and Pitchbend.

I don't mean about daily/weekly updates, but for a VSTi not updated since two months!

Also, where is the "MIDI Learn" feature? can't assign "Macro" potentiometers to my MIDI controller!!!! perhaps it's possible, but without user manual (and crystal ball)...

Be sure I regret to have bought this synth, for now I consider I'm a betrayed client.

I'm not a user but browsing this thread, a particulary uber rude customer with an insane sense of entitlement has caught my attention.

Why the hell didn't you demo this synth and check if sustain pedal input was working before you bought it? Did someone hold a gun to your head and force you buy it? Besides that this is a synth not a piano, you have much more options for control, why don't you route your sustain pedal to the mod wheel, aftertouch or any other of the numerous midi parameters available?

Since the use of a sustain pedal is pretty much a universal given and updating a product to fascilitate it's use should be a priority, I think the users frustration quite justifiable. Sustain pedals are very important when playing pad sounds on synths.

Sustain pedals are a niche thing with synth users. It is not uncommon at all to not have support, at least initially on release. What is universal is the pitch bend and the modulation wheels because the majority of synths and midi controllers have those. This is a very new synth on the market, it's up to Parawave to decide what to prioritise in their schedule and not for you to dictate because honestly it comes across as rude. If the synth was buggy, broken and didn't work as advertised then I would understand. But crying for a feature that is not yet implemented I don't get that.

[v1o]

Since the use of a sustain pedal is pretty much a universal given and updating a product to fascilitate it's use should be a priority, I think the users frustration quite justifiable. Sustain pedals are very important when playing pad sounds on synths.

I would be really surprised to learn that many KVR users owed a sustain pedal.

Keyscape target audience, perhaps so. Rapid less so.

Personally have only ever used them with pianos and organs .

[aMUSEd]

No more activities from Parawave website concerning RAPID Synthesizer (Windows) since long time, staying at v1.0.2, ignored sustain pedal remains unfixed..

Updates are still in development. I'm not a fan of daily/weekly updates. It's annoying for us AND customers. The next version will include cool new stuff. As long as there is no public announcement that development is discontinued, don't worry. Research, planning and testing just takes time.

Since TWO MONTHS you can't implement sustain pedal support? really is it a joke????
Is it too difficult to add "On/Off" checkbox from "Preferences" page? - oups, no "Preferences" page too... to enable or disable the sustain pedal, one of important feature like Modwheel and Pitchbend.

I don't mean about daily/weekly updates, but for a VSTi not updated since two months!

Also, where is the "MIDI Learn" feature? can't assign "Macro" potentiometers to my MIDI controller!!!! perhaps it's possible, but without user manual (and crystal ball)...

Be sure I regret to have bought this synth, for now I consider I'm a betrayed client.

I'm not a user but browsing this thread, a particulary uber rude customer with an insane sense of entitlement has caught my attention.

Why the hell didn't you demo this synth and check if sustain pedal input was working before you bought it? Did someone hold a gun to your head and force you buy it? Besides that this is a synth not a piano, you have much more options for control, why don't you route your sustain pedal to the mod wheel, aftertouch or any other of the numerous midi parameters available?

Since the use of a sustain pedal is pretty much a universal given and updating a product to fascilitate it's use should be a priority, I think the users frustration quite justifiable. Sustain pedals are very important when playing pad sounds on synths.

Sustain pedals are a niche thing with synth users.

Nonsense, it's a basic part of playing a keyboard. It may be a niche thing with mouse based DAW users but not synth playing musicians.

[exmatproton]

Not again the sustain pedal discussion.........

[Spitfire31]

Sustain pedals are a niche thing with synth users.

Nonsense, it's a basic part of playing a keyboard. It may be a niche thing with mouse based DAW users but not synth playing musicians.

/Joachim

[exmatproton]

quite a nice read

http://bedroomproducersblog.com/2017/02 ... er-review/

[Falconex]

What's with the automation record in Logic Pro X ? It's very annoying bug. Any news ?

[bite_me]

Bug in Bitwig, too.

[ravasb]

Any word on updates, especially loading your own wavetables?

[studjo]

Any word on updates, especially loading your own wavetables?

+1

[parawave]

Any word on updates, especially loading your own wavetables?

The next update 1.1.0 will probably include the following things:

1. Sizeable GUI (100%, 150%, 200% etc)
Likely settable in 10% increments. The graphics and sliders will dynamically adjust to these sizes. So everything stays sharp without blurry bitmap rescale.

2. Alternative design schemes
Planned is at least a "dark theme", as this was requested the most.
Additionally a few coloured ones. I think people expect a blue one.

3. Minor Features
Sustain Pedal, After Touch, additional modulation stuff.

The decision to improve the GUI before implementing the wavetable import was made because this way Rapid will reach a wider audience. More people disliked the GUI than the missing import feature.
It's definitely a bigger update, that's the reason it takes a while. But it will be cool, I think with the new enhanced visuals (ready for all screen sizes) it will also be easier/quicker to introduce new modules.

After this is done, the next thing will be the wavetable import.

[exmatproton]

1.1.0 ftw!

[MirkoVanHauten]

Sounds good. I hope we'll not get a beta but a good tested release

[Examigan]

Any word on updates, especially loading your own wavetables?

The next update 1.1.0 will probably include the following things:

1. Sizeable GUI (100%, 150%, 200% etc)
Likely settable in 10% increments. The graphics and sliders will dynamically adjust to these sizes. So everything stays sharp without blurry bitmap rescale.

2. Alternative design schemes
Planned is at least a "dark theme", as this was requested the most.
Additionally a few coloured ones. I think people expect a blue one.

3. Minor Features
Sustain Pedal, After Touch, additional modulation stuff.

The decision to improve the GUI before implementing the wavetable import was made because this way Rapid will reach a wider audience. More people disliked the GUI than the missing import feature.
It's definitely a bigger update, that's the reason it takes a while. But it will be cool, I think with the new enhanced visuals (ready for all screen sizes) it will also be easier/quicker to introduce new modules.

After this is done, the next thing will be the wavetable import.

Sounds great! Maybe MIDI Learn also at some point? I know you can assign MIDI CC's to the modulation section at the bottom, but I meant easy MIDI learn for each control.