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

[parawave]

How's this? 3D .OBJ (or similar) import for wavetables!

Interesting idea, but we already thought about this
Indeed, it would be a good data source and easier to visualize. Although the immediate question is: "How would objects like cubes and spheres "map" onto a wavetable?"

Let's say we map it like this:
x-axis = time
y-axis = table index
z-axis = amplitude

The thing is: There's only 1 possible value for each axis. This is essentially a projection onto a 2D Plane, which is an image. Resulting in

x-pixel = time;
y-pixel = table index
color = amplitude

So Mirko is right, no improvement.

[kokotte]

That thing could be really helpfull and some spectral fx plus phase modulation, with custom user wave and phase distortion, in the same time could be incredible with the Rapid quality !

[magicmusic]

now load time is good. old version at 2.8 GHZ
energy lead 03 4,9 sec
ambient pad 2 5,7 sec
caribic sunset 13,9 sec

most load now under 1 second

energy lead 03 below 1 sec
ambient pad 2 1.2 sec
caribic sunset 4.2 sec

the installer is now not detect as virus, but because AVG do several times a 15 sec fast test, maybe a thread get timeout. this errors come. read about the installer, there are many psts about false alert.

[38E8:1EC4][2017-08-31T12:07:52]i201: Planned package: RapidPlugin_x86, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[38E8:1EC4][2017-08-31T12:07:52]i201: Planned package: RapidPlugin_x64, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[38E8:1EC4][2017-08-31T12:07:52]i201: Planned package: RapidFactory, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[38E8:1EC4][2017-08-31T12:07:52]i299: Plan complete, result: 0x0
[38E8:1EC4][2017-08-31T12:07:52]i300: Apply begin
[38E8:1EC4][2017-08-31T12:07:52]i010: Launching elevated engine process.
[38E8:1EC4][2017-08-31T12:08:11]i011: Launched elevated engine process.
[38E8:1EC4][2017-08-31T12:08:11]e000: Error 0x800700e8: Failed to wait for child to connect to pipe.
[38E8:1EC4][2017-08-31T12:08:11]e000: Error 0x800700e8: Failed to connect to elevated child process.
[38E8:1EC4][2017-08-31T12:08:11]e000: Error 0x800700e8: Failed to actually elevate.
[38E8:1EC4][2017-08-31T12:08:11]e000: Error 0x800700e8: Failed to elevate.
[38E8:1EC4][2017-08-31T12:08:11]i399: Apply complete, result: 0x800700e8, restart: None, ba requested restart: No

[parawave]

We started a 25% OFF SALE. From NOW until 17. SEPTEMBER !



If you hesitated in the past, now here's a chance to check out one of the RAPID Extensions.

[magicmusic]

To load samples in, i think it is good, when rapid support SFZ file load. this is an open format and more and more support that. or maybe there can write a small helper program that convert a SFZ file into the name format rapid can load in as multisamples. there need no attack etc and filter settings of SFZ support

rapid have 8 layers and so it seem good possible to support keyswitches so sounds can use legato, or mute or diffrent glide settings. sure it is a synthesizer but also with synthesizer sounds can do lots when do sequences that mix legato and staccato play of a sound. that this is selden used, is only because synthesizer(hardware too) not support keyswitches on synth sounds.

can work as this When a defined key is press (for example c1) then Layer 1 and Layer 2 are switch to on, all other Layers to off. And when later c#1 is press then Layer 3 and 4 are switch on all other switch off. So can have with the 8 layers 4 keyswitches to use sounds as legato, mute, glide or bend up and can use 2 layers. because each layer can have 3 osc with 2 layers can do much.

[parawave]

To load samples in, i think it is good, when rapid support SFZ file load.

We thought about .sfz and loaded a few test libraries while implementing the multi-sample importer. The thing is, in most cases the author of a SFZ also puts a note token into the filename of each sample. Most samples are also created or edited with an external editor, which also saves loop points, MIDI unity note and high/low velocity. This data is enough to easily map the samples via drag and drop. All additional SFZ tags are too specific or unnecessary for RAPID, so why bother to add SFZ, if half of functionally is redundant?

Look at this free SFZ for example.

Code: Select all

<group>
lovel=0
hivel=127

<region> trigger=attack  pitch_keycenter=36 lokey=0 hikey=38 sample=BS Glassy Classic-000-036-c2.wav
<region> trigger=attack  pitch_keycenter=40 lokey=39 hikey=42 sample=BS Glassy Classic-000-040-e2.wav
<region> trigger=attack  pitch_keycenter=44 lokey=43 hikey=46 sample=BS Glassy Classic-000-044-g#2.wav

lovel, highvel = redundant
trigger = redundant
pitch_keycenter = redundant

The only necessary parts are the files:
BS Glassy Classic-000-036-c2.wav
BS Glassy Classic-000-040-e2.wav
BS Glassy Classic-000-044-g#2.wav

Which Rapid detects as C2=36, E2=40 and G#2=44
and automatically maps them from 0-38, 39-42, 43-46, with full velocity range from 0-127.

So, I recommend:
Just try to drag & drop all source samples of a SFZ. It's working in most cases.

this is an open format and more and more support that.

It's open - true. And yes, there is a kind-of specification, although it's strange how shattered it seems. Additionally any software / sampler provider does the way they want it, so it fit their needs and it usually doesn't matter if it works properly as stated in the specification. Where does the support for SFZ tags end? Which tags are commonly used, which ones can be ignored? Does it sounds the same in all applications? All of this is a big uncertainty when it comes to considering this format. Just for a "supports SFZ" in the feature list, this is really a burden.

can work as this When a defined key is press (for example c1) then Layer 1 and Layer 2 are switch to on, all other Layers to off. And when later c#1 is press then Layer 3 and 4 are switch on all other switch off. So can have with the 8 layers 4 keyswitches to use sounds as legato, mute, glide or bend up and can use 2 layers. because each layer can have 3 osc with 2 layers can do much.

Not sure if I understand this correctly but I think you can already achieve this by setting different key-ranges for each layer.

[Soundplex]

So, I recommend:
Just try to drag & drop all source samples of a SFZ. It's working in most cases.

Yes, if you have access to the wave files and if everything is mapped & setup that easy. But this isn't the case everytime. Additional the previous version of SFZ (SF2) embedds the data in its file which seems to be the only difference. So why not "kill several birds with one stone" and just implement it? Especially if you already have all the functionality due to normal import

[parawave]

So why not "kill several birds with one stone" and just implement it? Especially if you already have all the functionality due to normal import

Because it's error-prone and any vendor doesn't care about the other. Take the ARIA-specific SFZ opcodes. While useful for all of THEIR products, how would every other implementer accommodate for these differences? It invalidates all SFZ created with it. And that's by far not the only case, there are dozens of minor quirks. Let's say we just implemented the basic SFZ functionality. It just would take an hour and suddenly another user "really needs" this tag , because their current library does "this and that" and soon it will end in an endless spiral of madness and feature requests. No exaggeration!

As always, time can be spend on more "new" useful stuff. No one hinders you from your own small converter tool/script. Shoul be an easy thing, right ?

[magicmusic]

To load samples in, i think it is good, when rapid support SFZ file load.

We thought about .sfz and loaded a few test libraries while implementing the multi-sample importer. The thing is, in most cases the author of a SFZ also puts a note token into the filename of each sample. Most samples are also created or edited with an external editor, which also saves loop points, MIDI unity note and high/low velocity. This data is enough to easily map the samples via drag and drop. All additional SFZ tags are too specific or unnecessary for RAPID, so why bother to add SFZ, if half of functionally is redundant?

Look at this free SFZ for example.

Code: Select all

<group>
lovel=0
hivel=127

<region> trigger=attack  pitch_keycenter=36 lokey=0 hikey=38 sample=BS Glassy Classic-000-036-c2.wav
<region> trigger=attack  pitch_keycenter=40 lokey=39 hikey=42 sample=BS Glassy Classic-000-040-e2.wav
<region> trigger=attack  pitch_keycenter=44 lokey=43 hikey=46 sample=BS Glassy Classic-000-044-g#2.wav

lovel, highvel = redundant
trigger = redundant
pitch_keycenter = redundant

The only necessary parts are the files:
BS Glassy Classic-000-036-c2.wav
BS Glassy Classic-000-040-e2.wav
BS Glassy Classic-000-044-g#2.wav

Which Rapid detects as C2=36, E2=40 and G#2=44
and automatically maps them from 0-38, 39-42, 43-46, with full velocity range from 0-127.

it depend on the sound creator, how he name the wav. it happen often that all samples contain simple numbers and in the additional key words need read what they are. if rapid only read such information and load the samples correct in and map is very usefull and i think it is not much work to program

sample=Piano 2.wav
lokey=24 hikey=29
lovel=64 hivel=95
loop_mode=no_loop
pitch_keycenter=26

[Soundplex]

No one hinders you from your own small converter tool/script. Shoul be an easy thing, right ?

Or from using a synth thats able to deal with it

But you're right, I admit. There's more about it than just implementing it. The more I appreciate there are companies that already made it work fine.
I'd rather see a full ui overhaul, resizable and skinnable. There's the time spent much better on.

[magicmusic]

there is a short video to show what can do with key switches also good for lead synth sounds. but there is much more possible

[LiteOn]

Great news! I have Virus TI wavetables in Serum format and I'd love to use them in Rapid.

Me too.

[LiteOn]

This demo shows a preset where I used the RESYNTHESIS function of RAPID!

https://soundcloud.com/mirkoruta/parawa ... is-results

Hi Mirko,

what sound(s) have you used as the input source? Very nice.

And a huge Thank You for all your videos show-casing what Rapid is able to deliver. Very informative and convincing and very nice tunes!

Cheers,
LiteOn

[Mirko R.]

This demo shows a preset where I used the RESYNTHESIS function of RAPID!

https://soundcloud.com/mirkoruta/parawa ... is-results

Hi Mirko,

what sound(s) have you used as the input source? Very nice.

And a huge Thank You for all your videos show-casing what Rapid is able to deliver. Very informative and convincing and very nice tunes!

Cheers,
LiteOn

Thanks a lot. Uuuh, I just played around and I don't have the source anymore. But if I am not wrong, on Layer 1 it was a violin or a cello. Just record it in a minor chord (C D# G) and once again in a major chord (C E G). Than I imported booth waves in RAPID and choose "Resynthesis". The major chord I set to Osc 1 and the minor chord to Osc 2. With the Macro 1 knob I switch between booth oscs:

MinMaj1.jpg

The output of Layer 1 goes to Layer 2.
In Layer 2 I have another Resynthesis-Sound with a simple "aaah" voice as source. In this case I give all three oscs this Reynth-Multisample with hdiffferente pitches. Osc B is set to +16 Semitones (major) and pitches down to +15 Semitones when the Macro 1 button is on 100%:

MinMaj2.jpg

Now I can play a single note like C and RAPID plays a beatuful heavenly major chord and if I now want to play a nice progression, I can switch the chord from major to minor by using Macro 1.

[Muziksculp]

Some video tutorials showing the new features, and how to use them in version 1.1.0 , and a pdf user manual for the new features in 1.1.0 would be very helpful.

Thanks.