KVR Audio

fluffy_little_something · Sat Dec 30, 2017 9:01 pm

I know, but it is half price as the moment and they are working on bigger interfaces according to their recent press release. So I think it is worth getting now

By the way, I got new glasses a few months ago, so my vision is fine again now

I recommend the same to you

Cinebient · Post by **Cinebient** » Sat Dec 30, 2017 9:09 pm

Sacrilege....

wagtunes · Post by **wagtunes** » Sat Dec 30, 2017 9:12 pm

fluffy_little_something wrote:I know, but it is half price as the moment and they are working on bigger interfaces according to their recent press release. So I think it is worth getting now

Well, between you and me how long it's taken for them to get this far, I think we've got a very long wait before we see bigger GUIs for KLC. I'd be stunned if it happened in 2018. I think we're looking at 2019 or even 2020.

Whatever you do, don't hold your breath.

fluffy_little_something · Sat Dec 30, 2017 9:39 pm

Well, again, with my new glasses, small GUI size is more of a comfort issue, not a deal breaker. I have actually set my display resolution back to the recommended maximum one, and yet I can read almost anything now

So, even if they don't improve their GUI's anytime soon, no problem. And if they really do, even better

Compared to the display of the hardware, any software GUI is superior

noiseboyuk · Post by **noiseboyuk** » Sat Dec 30, 2017 9:48 pm

Funkybot's Evil Twin wrote:This has been discussed quite a bit already, the reason it's not a preference is that there are circumstances in busy projects where the multi-core will actually harm performance. Turning it on actually adds a bit of overhead to one of the cores, so if you're running a few instances in a project with lots of other stuff (where your DAW is already doing a decent job distributing CPU load across the multiple cores), the multi-core option in RePro-5 could actually degrade performance. They don't want users forgetting about it and instead want them to make a conscious effort to turn it on or off. Hence why it's not a preference.

Yes, this was much discussed in the beta. I didn't buy the explanation then and don't buy it now. Once you know how your system reacts to Repro 5, that's how your system reacts to it. I just can't see any logic for needing to change it every time.

EvilDragon · Post by **EvilDragon** » Sat Dec 30, 2017 9:53 pm

You don't have to "buy it", that doesn't mean the explanation is any less valid (especially since it's "from the horse's mouth").

Also, there IS a point at which having too many instances with MC enabled WILL start fighting for resources, at which you arrive at diminishing returns.

noiseboyuk · Post by **noiseboyuk** » Sat Dec 30, 2017 9:56 pm

EvilDragon wrote:You don't have to "buy it", that doesn't mean the explanation is any less valid (especially since it's "from the horse's mouth").

Also, there IS a point at which having too many instances with MC enabled WILL start fighting for resources, at which you arrive at diminishing returns.

But the point is - if one or a few instances are better for me with MC on, then I'd prefer it to default to on. Then in the rare cases where I have tons of them which causes problems I can turn it off, as opposed to manually switch it on every single time. It seems a bit daft to suggest people use DAW-based workarounds for something that could just be put into the plugin itself and be done.

But hey, it is what it is, 1st world problems etc

Funkybot's Evil Twin · Sat Dec 30, 2017 10:03 pm

noiseboyuk wrote:
Funkybot's Evil Twin wrote:This has been discussed quite a bit already, the reason it's not a preference is that there are circumstances in busy projects where the multi-core will actually harm performance. Turning it on actually adds a bit of overhead to one of the cores, so if you're running a few instances in a project with lots of other stuff (where your DAW is already doing a decent job distributing CPU load across the multiple cores), the multi-core option in RePro-5 could actually degrade performance. They don't want users forgetting about it and instead want them to make a conscious effort to turn it on or off. Hence why it's not a preference.
Yes, this was much discussed in the beta. I didn't buy the explanation then and don't buy it now. Once you know how your system reacts to Repro 5, that's how your system reacts to it. I just can't see any logic for needing to change it every time.

It's not about how your system reacts, it's about how Multicore will react per-project. Here's an example:

1. One instance of RePro-5 eats up 80% of one core
2. You have 8 cores
3. You turn on Multicore

Result: Success! Now Repro-5 only uses up 17% of core 1, and 10% of cores 2-8. Why more on Core 1? Because Multicore adds some CPU overhead and is less efficient overall, while also being wildly more efficient per core. Now, let's play this out further...

4. You start adding RePro-5's with Multi-core on
5. You eventually have a project that uses 8 RePro-5's, each using the same CPU as example 1.

Result: With Multicore on, you've maxed out one or more of the cores because of the additional CPU requirements of Multicore (where one core always works a bit harder).

6. You turn Multicore off on some instances.

Result: Overall CPU actually starts to DROP!

7. You turn Multicore off on all instances...

Result: You get the most efficient CPU performance as the DAW load balances each instance of RePro-5 on one of your 8 cores. Each core now has 20% headroom.

Multicore on requires additional CPU power on the whole, so it's only more efficient in some scenarios. Having a preference would be problematic for those reasons. And that's before we add projects with other effects, instruments, the various DAWs, and different OS/hardware combinations into the mix.

Unless I wildly misunderstood what Urs has said about how Multicore works, these types of scenarios are exactly why it's not a preference. Even if it's more efficient with Multicore on in your system, once you start building up projects you may need to turn Multicore off on all or some instances to get more efficient behavior. Hope that makes sense and isn't entirely inaccurate (Urs will always pop in and let everyone wrong if so - which is always welcome).

fluffy_little_something · Sat Dec 30, 2017 10:13 pm

In Reaper my unison bass patch uses 6% without MC support and 10% with MC support. And when the negative impact of MC support even increases with an increasing number of instances, I suppose it makes sense for me to always leave it turned off.

noiseboyuk · Post by **noiseboyuk** » Sat Dec 30, 2017 10:15 pm

(Funkybot - see my reply to ED above, fwiw.)

EnGee · Post by **EnGee** » Sat Dec 30, 2017 10:17 pm

Isn't the task of handling multi cores programs is for the OS to decide? I thought there are three layers of handling the multi-cores, the plugin, the DAW, then the OS.

Anyway, I might be wrong and it is all the plugin developer's responsibility! But that makes plugin development a 'hell'!

Hardock · Post by **Hardock** » Sat Dec 30, 2017 11:12 pm

Hi,

i'm a preset guy

That just sold me:

TUC One hundret fog horns (open the MW!

)

HS Countdown (:oops: sounds so alive)

HS Polyfinx (such a bouncy/snappy filter, i dont know how to put it)

TUC Drone one (just a sweet analog string)

...

+ lots of other just sweet sounding sounds.

Well done

Greetings
Hardock

pdxindy · Post by **pdxindy** » Sat Dec 30, 2017 11:15 pm

noiseboyuk wrote:
But hey, it is what it is, 1st world problems etc

hehehe... not even that...

jbarish · Post by **jbarish** » Sun Dec 31, 2017 10:58 pm

is there an option somewhere in Repro-1 to make it polyphonic?? I couldn't find one. If not, that would be a welcome addition.

fluffy_little_something · Sun Dec 31, 2017 11:01 pm

I have both demo versions and frankly, I hardly ever open Repro 1 as I don't like monophonic synths. Repro 5 even has the oscillators of Repro 1 on the tweaks page if necessary. Set the voices parameter to 1 and it is monophonic as well.

u-he Repro (Repro-1 & Repro-5) released