Repro-1 (out now)

[Torchlight]

So if I'm understanding this correctly, the LFO can only be assigned to the filter cutoff through the main controls but if you use the two Perform options you can assign it to other things? And there are only two Perform options, so if you assign velocity and aftertouch, you can't assign the LFO? Or am I missing something? Will the modulation options be expanded in the final version?

[Urs]

The LFO can be assigned to Filter Cutoff, Osc A Freq, Osc B Freq, Osc A Pulsewidth, Osc B Pulsewidth.

At the moment I don't think I'd add more modulation options. It would go too far off from what this is about. However, since we added a digital oscillator to Diva once, who am I to rule more modulation options out for Repro-1?

[AnX]

The LFO can be assigned to Filter Cutoff, Osc A Freq, Osc B Freq, Osc A Pulsewidth, Osc B Pulsewidth.

At the moment I don't think I'd add more modulation options. It would go too far off from what this is about. However, since we added a digital oscillator to Diva once, who am I to rule more modulation options out for Repro-1?

Thats a good enought amount, and you can always add an LFO to anything in your host. Win/win really.

[wagtunes]

I'm assuming the intro price will be good until the end of the year when the beta serial number expires?

[AnX]

I'm assuming the intro price will be good until the end of the year when the beta serial number expires?

End of Nov when its released

[sacer]

I have also not the best CPU performance, I own a i7 5800 overclocked to 6* 4Ghz
One instance can grow up from 30 to 60%
Most poly Diva pads take less CPU, is it multicore optimzed ?

[deastman]

I have a 2 year old Dell Inspiron i7 laptop, and most of the presets are maxing out my CPU.

[Urs]

I have also not the best CPU performance, I own a i7 5800 overclocked to 6* 4Ghz
One instance can grow up from 30 to 60%
Most poly Diva pads take less CPU, is it multicore optimzed ?

Some of it is not optimized well yet, as there's still a lot of debug code in the beta (as was said, switching the clock can even stall the system for a moment, due to debug code). It should not go past 25% on your machine in normal use now, and I'm confident we'll bring it down to about 15%, maybe even less.

Jaws and Lyrebird can contribute to CPU hunger a lot though and those two have pretty much reached the end of possible optimisations.

[Urs]

I have a 2 year old Dell Inspiron i7 laptop, and most of the presets are maxing out my CPU.

For real? A single instance?

[davidka]

The beta sounds awesome, tons of good things inside!

However I am a bit behind... Was there any reveal on the filter algos? Which one was chosen eventually?
I'm curious as I've seen so much noise over ZDF filters and such in the last years now and wonder if it's something audible or not.

[beely]

However I am a bit behind... Was there any reveal on the filter algos? Which one was chosen eventually?
I'm curious as I've seen so much noise over ZDF filters and such in the last years now and wonder if it's something audible or not.

Check the first post of the thread!

[wagtunes]

Just bought this. Absolutely loving the gritty sounds this thing can make. As usual, though, all this talk about CPU use is over my head as far as checking it. I don't have any meters in my DAW that tells me how much CPU a synth is using. And only a few synths, like NI stuff, have built in meters. So how can I tell how much CPU this thing is using without having to open up task manager? Or is that my only option?

[e@rs]

^What DAW is that, with no resource usage meter?

[EvilDragon]

The only proper CPU usage result you're gonna get from task manager. Open your DAW and run a single instance, there you have it.

[Cimbasso]

i7-5820k @4.2 GHz here, one instance taking up ~20-30% of RT CPU usage.