Repro-5 public beta (Repro V1.1)

[Urs]

Don't party too early... it's still a CPU scorching device

And yes. If multicore is enabled then CPU is loaded up to 50% more, then in single core. But Live CPU meter doesn't agree with that and in multicore mode Live decreases meter into half. Kinda strange behaviour.
Is it normal?

Yes, that's a common oddity - but we haven't been able to reproduce this ourselves. So we haven't figured it out yet, but either some hosts or some combinations with the Threads preference may seem more costly than it should.

Have you tried changing the number of threads in the preferences? Does any setting give better results?

We'd be interested to hear what CPU (with or without Hyperthreading) and what version of Live you use, maybe we can reproduce it that way.

[StudioDave]

Greetings,

Linux version lags a few builds behind, we hope to have it ready for you in a few days

"I'll be watching you... I'll be watching you..."

Looking forward to this.

Best,

dp

[D-Fusion]

Does it need 15-30. Min warmup time like the original and tweaking to get the osc pitch in tune with each other afterwards?


Thanks for releasing this and making the Prophet 5 availible to all
My Prophet Rev 2 came on tuesday so now i have all the Prophets i need in SW and HW

We live in amazing times

[Greybox Audio]

F*CK YES!

[ATN69]

Looks like a beauty

[exmatproton]

8 voices playing, with 8 threads enabled, HQ enabled is resulting in 37% of CPU usage (in-DAW, FL Studio x64 12.5) with the first three filters. The 4th filter hits 40%. (cpu: core i7 4790K @ 4 GHz)
Although it is quite high (with HQ enabled and no voice reallocating though), i find this acceptable considering the quality of the sound. Blown away by this thing!

[EvilDragon]

Don't party too early... it's still a CPU scorching device

And yes. If multicore is enabled then CPU is loaded up to 50% more, then in single core. But Live CPU meter doesn't agree with that and in multicore mode Live decreases meter into half. Kinda strange behaviour.
Is it normal?

Yes, because Live's CPU meter doesn't measure actual CPU usage, but time necessary to process a single audio buffer. When you get to 100% or above, you have a buffer underrun (crackles, etc.)

Never use any DAW CPU meter

[beely]

It really sounds great (as expected).

It's too much of a CPU muncher for me though (at least at this stage). I played it in AUHost first, then I was getting crackles/breakup with polyphonic playing (depending on the patch), so went over to Logic. Anything more than a couple of notes (or anything with longer releases) it just pegs a full core more or less permanently and crackles due to CPU breakup (not the demo limitations).

The thread preferences shows no really change in behaviour here, but I don't know if that's Logic's live mode forcing everything onto one core, but one core can't cope reliably here with the kind of sound I want to use a polysynth for.

Edit: Further testing, Multicore on, default 4 threads, does indeed improve performance and makes this playable.

(MBP 2011 i7 2.4 El Cap 16GB Ram, LPX latest)

I can barely look at the "HQ" switch...!

Congrats for hitting the milestone, though!

[zvenx]

I can indeed hear the difference between HQ on and off. Did I read correctly somewhere that the Oversampling with it off was equivalent roughly to Diva in great mode (which is how I use Diva)?
Also how come no zzzz mode?

thanks
rsp

[EvilDragon]

It's too much of a CPU muncher for me though (at least at this stage). I played it in AUHost first, then I was getting crackles/breakup with polyphonic playing (depending on the patch), so went over to Logic. Anything more than a couple of notes (or anything with longer releases) it just pegs a full core more or less permanently and crackles due to CPU breakup (not the demo limitations).

The thread preferences shows no really change in behaviour here, but I don't know if that's Logic's live mode forcing everything onto one core, but one core can't cope reliably here with the kind of sound I want to use a polysynth for.

(MBP 2011 i7 2.4 El Cap 16GB Ram, LPX latest)

2.4 GHz is a bit on the slow side of things these days

IIRC, in Logic, try NOT having the current track (with Repro) selected when playing it, then it spreads the load of the track across all cores, instead of shoving the currently selected track to just one core. Might help?

[Greybox Audio]

HS Cinema Plus & HS Emo Strings instantly put a big fat smile on my face!
Thanks alot Urs & Team for making my day

[lalo]

thanks u-he!!!!!

[synth_punk]

Motorbike Heidi baby! Howard your my hero!!

[beely]

2.4 GHz is a bit on the slow side of things these days

Maybe, but some of us just have to make do with what we have...
But that's why I said it was too CPU-heavy *for me*... and gave my specs as a feedback point.

IIRC, in Logic, try NOT having the current track (with Repro) selected when playing it, then it spreads the load of the track across all cores, instead of shoving the currently selected track to just one core. Might help?

Thanks, yes, I thought my previous post mentioning Logic's live mode would have suggested I was aware of how Logic handles this.

Live mode is specifically for live playing - yes, on MIDI playback only, you can select another track than the instrument (so it's not responding to incoming MIDI and is not in Live mode) and Logic can optimise a bit more and it's less of a problem, but any instrument that is enabled for live playing (selected track, or a record enabled track) that's responding to incoming MIDI is in Live mode, and thus forced onto one core for performance/optimization reasons. It doesn't matter whether the track is selected or non-selected but record-enabled, it's the same behaviour, Logic needs to put that instrument channel into live mode.

Like I say, this isn't Repro's fault or a failing in any way, but it does make it borderline here in terms of usability. It won't stop me having a play and exploring, but I can't use it reliably like my other instruments.

Just one more data point...

[Urs]

I can indeed hear the difference between HQ on and off. Did I read correctly somewhere that the Oversampling with it off was equivalent roughly to Diva in great mode (which is how I use Diva)?

No HQ is pretty much like great/Divine in Diva with 4x oversampling in the filter, whereas HQ is 8x, i.e. better than Diva (but also required due to greater frequency range in CEM 3320 filters).

Also how come no zzzz mode?

It's always on zZz. Otherwise it would suck 40% or so permanently, even when a voice is idle.