Here's an odd one... here are the conditions.

In Sonar all software synths respond really well (such as Kontakt, Reaktor etc) with low latency settings, however for this I've tried this with a low and a high ASIO buffer:

The issue is in stand alone but far worse in Sonar Platinum as a VST3.

If I bring up Rapture Pro and the default program, and then glide the mouse up and down the graphical keyboard in RPro reasonably quickly I get a lot of crackles and even drop outs. With other soft synths that have this exact functionality I don't seem to have this at all. Why?


Whilst this isn't something I would generally as a day to day thing, I wonder about day to day operation as far as general performance goes....
 
If anybody else can repro please let me know

Thanks...

No problem here, Alex, as a VST3 in S-Plat.
 
Maybe you need to give Roseberry a call -
 
 
 
  I really crack me up sometimes!

Roseberry? Sorry don't get it - not American...!

You are gliding the mouse up and down the virtual keyboard are you?
 
Hmmm weird what's going on... Looks like a big latency thing, I don't see any CPU issues or issue with output levels, and like I say I see no problem with other soft synths... I don't really have any performance issues...

I might have found something bad. I think it's a memory leak or something.
 
If I move the mouse up/down the keyboard really quickly, and change the parameter on all the filters on all screens (mixer/elements etc), the crackling gets worse until eventually I can get it to completely seize up..

Too much vigorous mousing may cause more than just crackles and dropouts :P :).
 
Seriously ... thinking it through - the virtual keyboard would have to be 'listening' for input and it would likely queue input it could not immediately process (too the point of overload(?)). It may be able to handle the most dextrous fingers but vigorous mousing may be sending thousands of input requests(?)
 
Perhaps devs can include an ignore 'trap' (I'll call it a mouse trap) when input signal overload is recognized(?)
 
The test could be 'Flight of the Bumblebee' ... on virtual keyboard.
 
 

ShellstaX
Too much vigorous mousing may cause more than just crackles and dropouts :P :).
 
Seriously ... thinking it through - the virtual keyboard would have to be 'listening' for input and it would likely queue input it could not immediately process (too the point of overload(?)). It may be able to handle the most dextrous fingers but vigorous mousing may be sending thousands of input requests(?)
 
Perhaps devs can include an ignore 'trap' (I'll call it a mouse trap) when input signal overload is recognized(?)
 
The test could be 'Flight of the Bumblebee' ... on virtual keyboard.

 
Yup I agree (well right now) that the use case isn't exactly common, however getting RP to overload is a little worrying. I don't think I was overloading it with too many KVM messages. There was no delay when responding to my movements. And I managed to get the crackling to happen almost straight away... It appeared to be like a really bad latency issue (that shouldn't happen). I think it might be very possible that the crash I managed to reproduce rapidly in a few minutes may also be reproducible after a couple of hours of using Rapture, tailoring a preset.

Doktor Avalanche
Roseberry? Sorry don't get it - not American...!

I believe he is referring to your back and forth with Jim Roseberry (Studio Cat) about custom verses off the shelf PC's :)

I deny all knowledge ;)

Sometimes it is best, and if we are to learn from our leaders (Politicians) even recommended :)

Can anybody repro #4/#1 ?
 
Thanks.