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

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Locked New Topic

Post

@sircuit:
It mostly depends on the visible tab. Rapid doesn't use OpenGL acceleration, so it's a pure software renderer. The multiband and voicing waveform display have to render quite a few samples (at 60fps). If you want to save some extra CPU you could also test with 30fps settings enabled (better restart after change) and test performance with the envelope tab visible. The complexity of the line drawings is a bit simpler there.

Interesting that you test the GPU performance first. I thought it's all about the DSP performance!? :wink:

Post

docam28 wrote:
noddog wrote:Anyone else have a bug with the tooltips? When I hover over a control all I see is a ghosted rectangle with no tooltip text inside.
kokotte wrote:yes, same here with the tooltips, w 7 64, reaper last update x 64.
Tooltips are working fine for me, using RAPID v1.0.2 (retail), Windows 7 SP1 64-bit, on both REAPER v5.29 x64 and Ableton Live 9 Lite v9.7.1 x64.
Works great for me too, and I'm using Windows 8.1 64-bit and Sonar X3 Producer.

Post

parawave wrote:Just want to inform everyone that RAPID is now finally available for MacOS X !!!

Get the Demo Version !

@Development:
If no sudden bugs appear, I will now have time to work on the implementation of the wavetable import. Be existed! Although it probably won't be released this year.
Congrats! I know a lot people were waiting for this. :)

Post

parawave wrote:@sircuit:
Interesting that you test the GPU performance first. I thought it's all about the DSP performance!? :wink:
It's quite simple: I was sitting in front of my mac, pressing G and adjusting a filter cutoff envelope on a saw when suddenly the fans started spinning heavy-ish. Having Avenger's experience, naturally I've gone to the GPU meter.

Why does GPU usage matters for me: When sitting in a quiet environment, playing a note each 3-4 seconds and adjusting parameters it's not desirable to have the fans blowing like playing a game. Now, when I'm actually in a project and the fans are spinning fast because of the overall load, I don't care too much. But in all honesty, when I'm designing a sound and have a project with single instrument open I don't think is normal to have the fans on. I told this (and not only me, and not only the mac guys, windows people too) to Avenger's devs, I'm telling the same thing to you.

This whole situation makes me very, very grateful to the devs out there that optimized the crap out of the GPU usage. I don't know what's the thing between you and Vengeance, but it looks like both rushed on the market untested extensively and unoptimised plugins, which is really sad.

PS: it's macOS, not MacOS X

Post

sircuit wrote:
parawave wrote:@sircuit:
Interesting that you test the GPU performance first. I thought it's all about the DSP performance!? :wink:
It's quite simple: I was sitting in front of my mac, pressing G and adjusting a filter cutoff envelope on a saw when suddenly the fans started spinning heavy-ish. Having Avenger's experience, naturally I've gone to the GPU meter.

Why does GPU usage matters for me: When sitting in a quiet environment, playing a note each 3-4 seconds and adjusting parameters it's not desirable to have the fans blowing like playing a game. Now, when I'm actually in a project and the fans are spinning fast because of the overall load, I don't care too much. But in all honesty, when I'm designing a sound and have a project with single instrument open I don't think is normal to have the fans on. I told this (and not only me, and not only the mac guys, windows people too) to Avenger's devs, I'm telling the same thing to you.

This whole situation makes me very, very grateful to the devs out there that optimized the crap out of the GPU usage. I don't know what's the thing between you and Vengeance, but it looks like both rushed on the market untested extensively and unoptimised plugins, which is really sad.

PS: it's macOS, not MacOS X
Huh?? Just put it to 30fps....

Post

exmatproton wrote: Huh?? Just put it to 30fps....
Let me make it clear: Logic does nothing, except displaying Rapid's window. For that, it needs over 50% GPU and over 13% CPU. On i7 quad core @ 2.3 GHz.

Image
Image

Post

sircuit wrote: Let me make it clear: Logic does nothing, except displaying Rapid's window. For that, it needs over 50% GPU and over 13% CPU. On i7 quad core @ 2.3 GHz.
well...that is a big difference compared to my system for sure...not sure if this is due to optimizing on Windows, but yeah, Rapid is one the most durable, less demanding and stable new plugins (~2015-2016) over here. screen shows 1 Rapid instance in FL Studio with 1 note playing (3 osc's) with all the multiwave displays open and changing/moving due to 3 seperate lfo's to the 3 morph knobs
usage Rapid windows.jpg
You do not have the required permissions to view the files attached to this post.

Post

Yeah, well, it's not uncommon for devs that don't code for mac regularly to blow things out when they finally do...

Post

I don't recall hearing my mac fans come on ever before today.
It's always on a cooler master cooling pad, which I think works sufficiently well until awhile ago.

rsp
sound sculptist

Post

My macbook is getting a bit hot but the fans are still silent....the bad thing i have some cpu spikes (lol, the same as Avenger) here and there and i hear those freaking drop-outs and cracks.
I mean macOS is anyway dead in a few years but i still like Logic :roll:
Maybe i need to buy a windows machine in near future to have better working plug-ins :D

Post

Cinebient wrote:My macbook is getting a bit hot but the fans are still silent....the bad thing i have some cpu spikes (lol, the same as Avenger) here and there and i hear those freaking drop-outs and cracks.
I mean macOS is anyway dead in a few years but i still like Logic :roll:
Maybe i need to buy a windows machine in near future to have better working plug-ins :D
I have a slave computer (VSL) with i7 CPU @ 4GHz and a 6 year-old card (DirectX 10 only), and Avenger crushes that GPU although it's a gaming graphic card in it. It's not the hardware, I think in this particular case was a mindless competition between devs on which one launches first... a arguably barely usable product. One crackles, the other one can't import wavetables, but hey, they have good DSP programming :dog:

Post

sircuit wrote:
Cinebient wrote:My macbook is getting a bit hot but the fans are still silent....the bad thing i have some cpu spikes (lol, the same as Avenger) here and there and i hear those freaking drop-outs and cracks.
I mean macOS is anyway dead in a few years but i still like Logic :roll:
Maybe i need to buy a windows machine in near future to have better working plug-ins :D
I have a slave computer (VSL) with i7 CPU @ 4GHz and a 6 year-old card (DirectX 10 only), and Avenger crushes that GPU although it's a gaming graphic card in it. It's not the hardware, I think in this particular case was a mindless competition between devs on which one launches first... a arguably barely usable product. One crackles, the other one can't import wavetables, but hey, they have good DSP programming :dog:
Now now, don't you forget that the percentage of problematic cases is still very small. Sure, Avenger (and now maybe also the mac version of Rapid) had its problems, but it isn't as if everyone had these problems.

"...arguably barely usable product" is an overstatement for sure. Let's see what Rapid evolves into. Maybe it also a smart idea to e-mail their support, instead of using kvr. KVR is no tech support substitute by any means.

Post

The percentage of problematic cases is allegedly very small. And is not "had" is "have" problems. Big, unsolved problems. I'll not purchase the synth now (with discount) hoping to get better. After it switches to full price I will thing of a purchase if the GPU issue is solved and the WT import is implemented. At the moment I'm fine with a single GPU sucker around (which I purchased without demoing because I wanted it so much and I didn't expected in a 1000 years to have a problem with the bloody GPU - never mind, lesson learned.

I purchased a lot of working software this year and maybe that's why I am so disappointed in these two - they kind of gone way below my expectancy bar right from the start.

Post

sircuit wrote:The percentage of problematic cases is allegedly very small. And is not "had" is "have" problems. Big, unsolved problems. I'll not purchase the synth now (with discount) hoping to get better. After it switches to full price I will thing of a purchase if the GPU issue is solved and the WT import is implemented. At the moment I'm fine with a single GPU sucker around (which I purchased without demoing because I wanted it so much and I didn't expected in a 1000 years to have a problem with the bloody GPU - never mind, lesson learned.

I purchased a lot of working software this year and maybe that's why I am so disappointed in these two - they kind of gone way below my expectancy bar right from the start.
I have a completely different experience with both synths. So "had" is still "had" from my point of view and several (the most) other users. Yes, there are still some users who are complaining about some spikes and some other "small" issues, but that percentage is REALLY low.
Now, Rapids mac versions has just been released and all i am saying is that at this point in time it isn't sure how much of a general issue your issue is.

Again (and you ssem to like to overstate things), "Big, unsolved problems" is a huge overstatement. Maybe for you. So, write to their tech support (if you own a license for the synth) and give them a reason to look into your problem(s).
Last edited by exmatproton on Sat Dec 17, 2016 7:09 pm, edited 1 time in total.

Post

In Logic Pro X touch automation isn't working. Is this due to the demo version or some missing response from Rapid?

Locked

Return to “Instruments”