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

[shonoob]

1. Open a text editor, type 0.12345 for example.
2. Select and copy the value 0.12345 and it is now in your copy/paste clipboard.
3. Rightclick on any knob/slider in RAPID and choose "Paste..". It will be set to your clipboard value.

t's a workaround, but not the same thing. I find the possibility to enter exact values in numeric fields rather convenient.

You are right. What do you mean, would it satisfy you if there was an "Enter Value.." in the rightclick menu? Or have you another certain method of entering values in mind (notice, the double click is already taken).

ctrl + click would work

[Gregorius]

This also made me think about "Why does this developer don't want me to really test his product?".

I'm not sure you realize how crazy paranoid you sound.

There are developers offering unlimited demo time. All fine. But as soon as I get restricted in any way, I ask myself: why? And often it is because the dev knows that if a customer spends more time with the plugin, he might not buy it because the initial hype is gone and more bugs come up or hidden problems. It is a way to force someone into a quick unconscious buy and I always get suspicious with that. That's all. Probably I'm the only that thinks like that because I worked in advertising and marketing industries and I know what happens behind the scenes There's nothing wrong with that, other devs would also do it like that. Most time it's the customers that are sheeps...

Man you come on a public forum accusing people of all kinds of things, that is not alright and you really do sound paranoid in a sick way. I would seriously go see a doctor if I were you.

Yes Mr. William Alexander Cooper. I wrote my opinion and experience in a public forum. I also came up with obviously assumptions or coincidences which came up in the Avenger thread as well and they luckily got disproved by parawave with a nice explanation. Thanks for that!

[ATS]

This also made me think about "Why does this developer don't want me to really test his product?".

I'm not sure you realize how crazy paranoid you sound.

There are developers offering unlimited demo time. All fine. But as soon as I get restricted in any way, I ask myself: why? And often it is because the dev knows that if a customer spends more time with the plugin, he might not buy it because the initial hype is gone and more bugs come up or hidden problems. It is a way to force someone into a quick unconscious buy and I always get suspicious with that. That's all. Probably I'm the only that thinks like that because I worked in advertising and marketing industries and I know what happens behind the scenes There's nothing wrong with that, other devs would also do it like that. Most time it's the customers that are sheeps...

Man you come on a public forum accusing people of all kinds of things, that is not alright and you really do sound paranoid in a sick way. I would seriously go see a doctor if I were you.

Yes Mr. William Alexander Cooper. I wrote my opinion and experience in a public forum. I also came up with obviously assumptions or coincidences which came up in the Avenger thread as well and they luckily got disproved by parawave with a nice explanation. Thanks for that!

sounds like a chronic problem. hopefully you will get help. good luck.

[Gregorius]

This also made me think about "Why does this developer don't want me to really test his product?".

I'm not sure you realize how crazy paranoid you sound.

There are developers offering unlimited demo time. All fine. But as soon as I get restricted in any way, I ask myself: why? And often it is because the dev knows that if a customer spends more time with the plugin, he might not buy it because the initial hype is gone and more bugs come up or hidden problems. It is a way to force someone into a quick unconscious buy and I always get suspicious with that. That's all. Probably I'm the only that thinks like that because I worked in advertising and marketing industries and I know what happens behind the scenes There's nothing wrong with that, other devs would also do it like that. Most time it's the customers that are sheeps...

Man you come on a public forum accusing people of all kinds of things, that is not alright and you really do sound paranoid in a sick way. I would seriously go see a doctor if I were you.

Yes Mr. William Alexander Cooper. I wrote my opinion and experience in a public forum. I also came up with obviously assumptions or coincidences which came up in the Avenger thread as well and they luckily got disproved by parawave with a nice explanation. Thanks for that!

sounds like a chronic problem. hopefully you will get help. good luck.

Thanks buddy!

[AnalogGuy1]

Can the pitch bend be set to +/-48 notes?

Pitchbend range can be set within +/- 24 semitone. For playability a range of +/- 48 is not really necessary.

As a regularly gigging keyboardist of a classic rock cover band, I respectfully disagree. Many well-known hits we cover like "Safety Dance" have 4 octave bends (in the outro). Ditto for many synth parts of Talking Heads. Now I can't imagine why anyone would want to sweep something like +/-37 semitones, so to avoid cluttering the UI, perhaps let it jump from 1-24 to 36 and 48 cases. But yes, it is very helpful in certain songs to go to 3 or 4 octaves, and including simple features like this will help it stand out from the crowd of synths that don't offer these features.

FWIW, I very much like the UI. I cannot stand complex UI's that are hard to read from my screen while playing on a darkened stage. I could care less if it looks like 2016 or 2007 or 1999; I do care if it is easily-readable while on the job.

[ATS]

at first I actually thought the UI made it look cheap or something, not sure why. But it really grew on me.

[Mirko R.]

Can the pitch bend be set to +/-48 notes?

Pitchbend range can be set within +/- 24 semitone. For playability a range of +/- 48 is not really necessary.

As a regularly gigging keyboardist of a classic rock cover band, I respectfully disagree. Many well-known hits we cover like "Safety Dance" have 4 octave bends (in the outro). Ditto for many synth parts of Talking Heads. Now I can't imagine why anyone would want to sweep something like +/-37 semitones, so to avoid cluttering the UI, perhaps let it jump from 1-24 to 36 and 48 cases. But yes, it is very helpful in certain songs to go to 3 or 4 octaves, and including simple features like this will help it stand out from the crowd of synths that don't offer these features.

FWIW, I very much like the UI. I cannot stand complex UI's that are hard to read from my screen while playing on a darkened stage. I could care less if it looks like 2016 or 2007 or 1999; I do care if it is easily-readable while on the job.

This is really only the direct linked pitchbend. But you can link it by yourself in each layer up to +- 96. That more than enough.

[AnalogGuy1]

When I link R1 on the Layer 1 tab to have Source as Pitch-Wheel and Target as Osc A-Semitone or Pitch-Coarse, and set the amount to +96, it does not seem to affect the behavior of the pitch of Oscillator A any more than if R1 is not deactivated.

How is it possible to make Osc A's pitch vary over a 4 octave range by moving the pitch wheel?

I think I'm doing things correctly because I can use R2 to modulate the equalizer effects cutoff with an LFO.

Edit: It works as expected if I use R1 with the mod wheel as the source in a non-standard way to alter the pitch, so it must just be a buglet that the pitch won't respond over multiple octaves to the pitch wheel. Not a problem. I'm buying.

[Orbit-50]

This also made me think about "Why does this developer don't want me to really test his product?".

I'm not sure you realize how crazy paranoid you sound. you also go on about someone who worked on it accusing them of stuff as well. Man see a doctor seriously.

Honestly. It's a freakin' synth plugin. Where the hell did all the conspiracy theory come from. I bought it and think it's awesome and I'm gonna have loads of fun with this. Rapid totally kicks ass and Rapid is what one makes of it. I have every synth plugin and Rapid makes an excellent addition to my arsenal. There's no comparing it to anything, because it is it's own entity. Thank you Parawave Audio for investing your time and efforts to bring this plugin into the arena. I hope to see more stuff from you guys.

[recursive one]

But I can't be the minority who dislikes the color theme.

I'm not exactly mad about it either. The GUI reminds me on Sylenth, it is clean and easily readable but not exactly an eye-candy. I think i'd prefer white/blue or white/green colour scheme.

But if fact I don't care much about it, there are only two synths which are that ugly so I just can't see myself using them no matter how good they sound and Rapid's GUI is definitely not even close to them.

BIG + 1 for entering the numerical values from keyboard.

[wagtunes]

You know, a manual for this thing would really be nice. I have no clue how these macros work. I have tried everything I know instinctively to use them in the mod matrix, but essentially, the only way to get a macro activated is to manually adjust the control to whatever value you want by hand. At least in Cubase. Maybe it's a bug. Maybe it's how its supposed to work. Or maybe there is some sequence of clicks I need to execute somewhere on the GUI that I'd need to be Houdini to figure out.

The online manual is 90% blank. I get this is version 1.0.0 but how do you release a synth this complex without a manual?

[Touch The Universe]

Just purchased Thanks so much for the lucky bird deal, that's great!

Downloading now and plan to jump in ALL day with it

A most excellent synth for sure, well done parawave!!

Also, about the gui, I think it is okay and has already grown on me a bit, and really do consider adding mseg's -- they are such a powerful tool! I don't see how the step sequencer can really allow me to fine tune amp and envelope curves.

Just a quick and rather important question, I know that users can't import wavetables, but does this also include wave samples?

Yes, at the moment there is no import feature. We are thinking about that and putting it on our planned feature list. If you don't mind, can you further explain how you would imagine such a feature? We don't want to confuse with unnecessary complexity. So I think at first it will be a simple "oneshot" sample import.

I think this is an extremely important feature. I really, really hope you guys implement the ability to import waveforms, especially multi-samples (this would really make this synth specials and stand out even more). At the bare minimum however, a single oneshot would be better than nothing for sure, but why limit to this. Rapid is such a great synth already, it'd be such a shame not to increase its potential with this. When I first saw that it had multi sample ability, my initial thought was that this would be open to all users, which really grabbed my attention that this would be a special synth. Not too many, if not any, synths allow this with a starting point in a synth as good sounding as rapid.

About how to implement this, I'm no developer so I can't really go into too much detail, or know if the ideas i have or easily doable to program, but I'll give it a go. To import, simply use the existing ability to load wavetables in the oscilator window and have an option to import wave/s. If more than one file is selected, have the gui display key ranges for the samples and have the names drag able to whichever key is desired, and have the ability to select its range, ie one octave per sample, etc.

[parawave]

I have no clue how these macros work.

So you want to link one of the three macros in the top bar to control morph for example? There are 3 possible ways, in order of difficulty:
1. You can use the drag & drop icon (+Route) that appears when you hover over a macro knob and drag it to morph, then set the depth in the mod-matrix.
2. You can rightclick on morph, choose "Modulate By.. > Macros > Macro 1", then set the depth in the mod-matrix.
3. Create a mod-matrix entry manually by first choosing the source "Macro 1" and then choosing the target "Oscillator A > Morph", then set the depth in the mod-matrix.

In order to automate the Macro 1 knob, handle it like a standard VST Parameter. The name ist "M-Macro 1". That really depends on your DAW.

Yes, the manual. A forgotten child. I will try to complete it, but the MacOS X users demand their plugin : D

[fmr]

About how to implement this, I'm no developer so I can't really go into too much detail, or know if the ideas i have or easily doable to program, but I'll give it a go. To import, simply use the existing ability to load wavetables in the oscilator window and have an option to import wave/s. If more than one file is selected, have the gui display key ranges for the samples and have the names drag able to whichever key is desired, and have the ability to select its range, ie one octave per sample, etc.

So, you are saying they should include a sample mapping utility

[Touch The Universe]

yeah, that thing