KVR Audio

TwoToneshuzz · Post by **TwoToneshuzz** » Fri May 20, 2016 9:34 pm

Thanks for the new update 1.1.0 working fine on my mid 2011 i5 3.1 Ghz iMac..

jackmazzotti · Post by **jackmazzotti** » Sat May 21, 2016 12:11 am

Cinebient · Post by **Cinebient** » Sat May 21, 2016 9:51 am

Works fantastic so far. Just get often sample rate conflict message within Logic while switching patches. But i had that before too.
I'm pleased so far....have to dive in deeper.

Sampleconstruct · Post by **Sampleconstruct** » Sat May 21, 2016 10:14 am

SR conflict warnings in Logic are CPU related.

Cinebient · Post by **Cinebient** » Sat May 21, 2016 10:28 am

Sampleconstruct wrote:SR conflict warnings in Logic are CPU related.

Mmhh, thank´s. Then it seems to be some cpu spikes while switching patches. But it doesn´t break or crash anything really so i can live with it. Logic is indeed a "bitch" last time. Especially with more complex UI´s i have some trouble with several plug-ins and Apple won´t solve several bugs..... but i won´t take the time to learn a new DAW too

Is there a way to turn off those messages and ignore them by default?

Sampleconstruct · Post by **Sampleconstruct** » Sat May 21, 2016 10:32 am

You can't hide SR conflicts warnings, max out your sample buffer and adjust the new settings in the KS prefs, CPU problems should be solved with this update.

Cinebient · Post by **Cinebient** » Sat May 21, 2016 10:36 am

Sampleconstruct wrote:You can't hide SR conflicts warnings, max out your sample buffer and adjust the new settings in the KS prefs, CPU problems should be solved with this update.

I´m already on the max sample buffer. Kaleidoscope is set to auto....or should i set it manually to the highest size. But since Logic just goes to 1024 it doesn´t help...or?

Sampleconstruct · Post by **Sampleconstruct** » Sat May 21, 2016 10:45 am

Auto is good, try setting multithreading to 25 or 50%, adjust the new treshold levels, e.g. -48 dB

Andrew Souter · Post by **Andrew Souter** » Sat May 21, 2016 10:47 am

Cinebient wrote:
Sampleconstruct wrote:You can't hide SR conflicts warnings, max out your sample buffer and adjust the new settings in the KS prefs, CPU problems should be solved with this update.
I´m already on the max sample buffer. Kaleidoscope is set to auto....or should i set it manually to the highest size. But since Logic just goes to 1024 it doesn´t help...or?

No. Keep it set to auto in KS. This matches the host, and will add zero additional latency, and will actually give the best performance. setting it to 64k in KS for realtime will give much WORSE results actually. AND it will make the GUI very unresponsive.

We have considered (are still considering) removing all real-time options except "Auto". But we thought we'd keep them for now to see how they behave on various systems...

feel free to try them of course, maybe we will learn something we don't know. But our current understanding is you should normally always use Auto, and using a much larger setting than the host for realtime will be worse and than using auto.

save the huge buffer sizes for offline bounces. They can speed up render times significantly...

Cinebient · Post by **Cinebient** » Sat May 21, 2016 11:16 am

Galbanum wrote:
Cinebient wrote:
Sampleconstruct wrote:You can't hide SR conflicts warnings, max out your sample buffer and adjust the new settings in the KS prefs, CPU problems should be solved with this update.
I´m already on the max sample buffer. Kaleidoscope is set to auto....or should i set it manually to the highest size. But since Logic just goes to 1024 it doesn´t help...or?
No. Keep it set to auto in KS. This matches the host, and will add zero additional latency, and will actually give the best performance. setting it to 64k in KS for realtime will give much WORSE results actually. AND it will make the GUI very unresponsive.

We have considered (are still considering) removing all real-time options except "Auto". But we thought we'd keep them for now to see how they behave on various systems...

feel free to try them of course, maybe we will learn something we don't know. But our current understanding is you should normally always use Auto, and using a much larger setting than the host for realtime will be worse and than using auto.

save the huge buffer sizes for offline bounces. They can speed up render times significantly...

Thank's. Yep, Auto works best. I tryed it with manually higher buffer but that makes it worse indeed.
Regarding to off line rendering...if the buffer here makes no different for the audio quality and the highest size makes faster rendering...what would offer me auto or even buffer of 64 here for offline?

Andrew Souter · Post by **Andrew Souter** » Sat May 21, 2016 11:41 am

Cinebient wrote:
Galbanum wrote:
Cinebient wrote:
Sampleconstruct wrote:You can't hide SR conflicts warnings, max out your sample buffer and adjust the new settings in the KS prefs, CPU problems should be solved with this update.
I´m already on the max sample buffer. Kaleidoscope is set to auto....or should i set it manually to the highest size. But since Logic just goes to 1024 it doesn´t help...or?
No. Keep it set to auto in KS. This matches the host, and will add zero additional latency, and will actually give the best performance. setting it to 64k in KS for realtime will give much WORSE results actually. AND it will make the GUI very unresponsive.

We have considered (are still considering) removing all real-time options except "Auto". But we thought we'd keep them for now to see how they behave on various systems...

feel free to try them of course, maybe we will learn something we don't know. But our current understanding is you should normally always use Auto, and using a much larger setting than the host for realtime will be worse and than using auto.

save the huge buffer sizes for offline bounces. They can speed up render times significantly...
Thank's. Yep, Auto works best. I tryed it with manually higher buffer but that makes it worse indeed.
Regarding to off line rendering...if the buffer here makes no different for the audio quality and the highest size makes faster rendering...what would offer me auto or even buffer of 64 here for offline?

Use the largest option for Bounces: 65536.

...but really there is very little difference between 16384, 32768, 65536 on the various systems we have tried. 16384 seems to be be "big enough" to get most benefit on all of the systems we have tried... but we have not tried a dual socket xeon system yet, 32k and 64k might have benefit there.

note not all hosts switch settings completely properly between real-time and offline.

Sound Forge for example does not, as there is no way for us to know if the plug is in realtime or bounce state. You can use Force Offline in these cases.

Also Reaper Windows is not using the offline buffer size for some reason. exploring.

Cubase and Logic do indeed switch properly.

Andrew Souter · Post by **Andrew Souter** » Sat May 21, 2016 11:43 am

when in doubt about anything you can always control-click (win) or command-click (OS X) on settings to restore the default values which are what we generally recommend.

Cinebient · Post by **Cinebient** » Sat May 21, 2016 11:52 am

Galbanum wrote:when in doubt about anything you can always control-click (win) or command-click (OS X) on settings to restore the default values which are what we generally recommend.

Lol, thank's....that was my next question. I already made a bit chaos in the settings!
Last one for now...are there any real benefits for 4X oversampling offline. Or must i be a bat to hear it?

Andrew Souter · Post by **Andrew Souter** » Sat May 21, 2016 12:04 pm

at this point there is very little benefit to using oversampling at all in KS. generally you can keep it at 1x for everything. (in the early versions we made some incorrect assumptions about why it was needed which turned out not to be true.

)

It is currently useful only:

1) if mod rate is extremely fast it will help minimize aliasing do to sidebands from the modulation.

2) it will keep harmonics of string resonators more perfectly in tune in some cases (for some nerdy math reasons, I won't bother to explain.

)

it might be more useful in future versions of KS for some things we have planned.

note that if mod rates are not fast (i.e. mod period is something like 1 measure or longer, like it usually is), KS is basically already perfectly alias free. As a synth engine it is one of the cleanest out there... there is zero aliasing at all in the resonators, and they are perfectly clean and precise all the way to half the sample rate.

Cinebient · Post by **Cinebient** » Sat May 21, 2016 12:20 pm

Galbanum wrote:at this point there is very little benefit to using oversampling at all in KS. generally you can keep it at 1x for everything. (in the early versions we made some incorrect assumptions about why it was needed which turned out not to be true. )

It is currently useful only:

1) if mod rate is extremely fast it will help minimize aliasing do to sidebands from the modulation.

2) it will keep harmonics of string resonators more perfectly in tune in some cases (for some nerdy math reasons, I won't bother to explain. )

it might be more useful in future versions of KS for some things we have planned.

note that if mod rates are not fast (i.e. mod period is something like 1 measure or longer, like it usually is), KS is basically already perfectly alias free. As a synth engine it is one of the cleanest out there... there is zero aliasing at all in the resonators, and they are perfectly clean and precise all the way to half the sample rate.

Thank's again...i got it

2CAudio Kaleidoscope | It's A Trip | Latest Update 1.1