KVR Audio

woodsdenis · Post by **woodsdenis** » Fri Dec 30, 2016 11:24 pm

Orbit-50 wrote:It's a little bit slower for me to load than most, but it's not that bad. 1 to 2 seconds at the most is the norm for me.

same here, not a deal breaker but faster loading times would be better if possible.

magicmusic · Post by **magicmusic** » Sat Dec 31, 2016 12:03 pm

Mirko R. wrote:
magicmusic wrote:
Trice wrote:You need 8x SSD in raid0 to do anything these days.

/s
in windows taskmanager can see, how many mb/sec data is transfer from SSD. when i load caribic sunset show 1,5 MB/sec upto 6.7 MB/sec. so can see only very few data is transfer from SSD. i only have tell that i use a fast ssd so nobody can say access time due to harddrive is too slow. when load a sound a second time then all is in filecache. i have 12 GB RAM in my system and i use 64 bit rapid synth. but load time of sunset is not much faster. so seem CPU. so my question is, if it get much faster with faster cpu that supoort AVX
The reason why presets like "Caribic Sunset" take more time to load than others do, is that they have a lot of multismaples and wavetables included. These are the biggest kind of presets wich have all layers in use. In fact there are 16 oscs running in "Caribic Sunset" and each one have to load a different multisample or wavetable.
This kind of presets are regulary big sequences, polyphon melodies or complete little tracks so they need all the oscs and layers. That's a big reason why I love RAPID! And think about it. How long do a track load, when you load one in your DAW? Maybe a half Minute? Ah and did You notice how fast you can instanciate a RAPID? I think this is really fast for a big synth.

In windows taskmanager can see that there are only maximum 6,7 megabyte /sec load for sound data. really strange what is done all the time. so many parameters to load have the synth not. maybe load can speedup lots easy, when it is check if layers are enable. and when only layer 1-4 is enable(in most patches), play can start after load of layer 4 and so can 2* faster
when have a song in DAW with many tracks and only 260 megabyte of samples need load, it need only 2-3 sec in DAW. slowdown in DAW is when use many plugins, because all plugins have lots of graphical GUI data, sounds to load.

Mirko R. · Post by **Mirko R.** » Tue Jan 03, 2017 10:31 pm

Hey guys (and maybe sime laydies? i don't know...)
I would like to show you an improvisated demo, I build this sound for the new Extension and played a bit with it. Hope you feel the analogie in it.

https://soundcloud.com/mirkoruta

Orbit-50 · Post by **Orbit-50** » Tue Jan 03, 2017 10:52 pm

Nice stuff man! I really like Rapid and I'm glad I made the investment.
BTW, I also have your Alchemy soundset, and always thought it was really cool as well.

Mirko R. · Post by **Mirko R.** » Wed Jan 04, 2017 11:32 am

Orbit-50 wrote:Nice stuff man! I really like Rapid and I'm glad I made the investment.
BTW, I also have your Alchemy soundset, and always thought it was really cool as well.

Thanks and OMG... that was the first soundset I made for vengeance. It should be 6 years ago.

Examigan · Post by **Examigan** » Wed Jan 04, 2017 4:43 pm

Mirko R. wrote:Hey guys (and maybe sime laydies? i don't know...)
I would like to show you an improvisated demo, I build this sound for the new Extension and played a bit with it. Hope you feel the analogie in it.

https://soundcloud.com/mirkoruta

Sounds great!

kontakt · Post by **kontakt** » Thu Jan 05, 2017 8:43 am

I found a bug.

EFFECTS -> BALANCER -> PAN

Pan polarity is reversed.

L is R.
R is L.

parawave · Post by **parawave** » Thu Jan 05, 2017 9:24 pm

kontakt wrote:I found a bug.

EFFECTS -> BALANCER -> PAN

Pan polarity is reversed.

L is R.
R is L.

Um, are you sure it's not your speaker setup? Just look at the meters and double check with DAW meters.

Examigan · Post by **Examigan** » Thu Jan 05, 2017 9:44 pm

parawave wrote:
kontakt wrote:I found a bug.

EFFECTS -> BALANCER -> PAN

Pan polarity is reversed.

L is R.
R is L.
Um, are you sure it's not your speaker setup? Just look at the meters and double check with DAW meters.

Headphones on backwards?

aMUSEd · Post by **aMUSEd** » Thu Jan 05, 2017 9:45 pm

Examigan wrote:
parawave wrote:
kontakt wrote:I found a bug.

EFFECTS -> BALANCER -> PAN

Pan polarity is reversed.

L is R.
R is L.
Um, are you sure it's not your speaker setup? Just look at the meters and double check with DAW meters.
Headphones on backwards?

Or ears

starflakeprj · Post by **starflakeprj** » Thu Jan 05, 2017 10:10 pm

Actually, I think he's right. Getting the same thing.

2017-01-05.jpg

2017-01-05_2.jpg

parawave · Post by **parawave** » Thu Jan 05, 2017 10:54 pm

starflakeprj wrote:Actually, I think he's right. Getting the same thing.
2017-01-05.jpg
2017-01-05_2.jpg

I think you confuse the stereo knob with panning.

Rapid Tooltips wrote: Pan
Change the stereo panning of the output.
(0% = Left, 50% = Center, 100% = Right)

Stereo
Change the stereo field of the output.
(0% = Mono, 50% = Normal, 100% = Widen)

Hope that clears things up. Otherwise, check these things with a vectorscope.

Examigan · Post by **Examigan** » Fri Jan 06, 2017 12:15 am

I just tried it here in Sonar using the same preset and settings in those screenshots, and it shows correctly in all meters: all are panned the same way (to the left). It seems that on his 1st screenshot, unless I am mistaken, for some reason in the DAW's meter looks like it shows as being panned nearly all the way to the right, but it shows it's over to the left in Rapid.

panning.jpg

You can see in my screenshot that it looks like its working ok.

So that seems to be an issue with the panning in your DAW, not in Rapid.

Touch The Universe · Post by **Touch The Universe** » Fri Jan 06, 2017 3:48 am

The panning on the balancer seems okay here too

I am having slight issues with the "Activate License" popping up everytime I start my Daw. One I hit play, the screen goes away. Would be nice if this was updated sometime in the future

starflakeprj · Post by **starflakeprj** » Fri Jan 06, 2017 9:01 am

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.

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