Repro-5 public beta (Repro V1.1)

[Funkybot's Evil Twin]

I updated my prior post with 3 RePro skins in case anyone wants to re-download it:

https://www.dropbox.com/s/cyqj10ir40ve2 ... s.zip?dl=0

There's 2 RePro-5 skins: grey, and an almost black, and my updated RePro-1 skin.

[irr]

I took my favorite self-made patches from my Prophet 8 and tried to replicate them on the Repro-5. Sometimes I had to check twice to see if I didn't record the same synth twice - they sounded that similar! On other patches I struggled a bit more to get them to sound the same, since the unique character of the two synths started to show.

I can't believe how good Repro-5 sounds! I remember getting totally psyched by Diva about 5 years ago, and now it happens all over again.

The first synth is always the Prophet 8 (download for uncompressed audio):
https://soundcloud.com/eivind-engedal/d ... -5-patches

NICE!

[glokraw]

Is the Repro 5 MC setting strictly for cores, or are threads
also counted? I have an i7 with 4 cores and 8 threads,
and chose 6 in Repro5 for one instance, in case it's counting threads.

If a daw app has a different setting, is there a conflict that will
cost cpu cycles and or audio quality? In my case, Reaper
'auto-detects' needing 8 'audio reading/processing threads.'
Will matching the daw and plugin settings be needed?
Cheers

[clangorous]

If a daw app has a different setting, is there a conflict that will
cost cpu cycles and or audio quality? In my case, Reaper
'auto-detects' needing 8 'audio reading/processing threads.'
Will matching the daw and plugin settings be needed?
Cheers

Page 4 of the manual talks about that. I assume it applies to Linux version as well:
"Note: Some hosts already offer optional multicore support, and this can
lead to poorer performance for Repro-5. In such cases, please switch one of them off."

[Frantz]

Just bought this. It sounds great!

I would prefer if the LEDs on the LFO gradually went from off to on to indicate where in the cycle they currently are.

[24dB]

sorry if this has already been answered, but when I install R5 on my PC Im not getting any .NKS presets.
(besides the .init file)
There are for R1, just not R5. Should there be any?

Thanks!

[Funkybot's Evil Twin]

sorry if this has already been answered, but when I install R5 on my PC Im not getting any .NKS presets.
(besides the .init file)
There are for R1, just not R5. Should there be any?

Thanks!

The R5 patches haven't been tagged yet and are still WIP.

[dangayle]

Here is a weird bug: The Repro-1 manual opens correctly in Mac Preview v9 (OS 10.12) but the Repro-5 manual shows just the first few pages, and the rest of the pages are blank, and then freezes Preview when you try to quit. Repro-5 manual opens correctly in Adobe Reader. It's repeatable. And a little annoying, because Preview is my default reader. Time to switch to Adobe?

That's actually a bug that Apple introduced when they 'fixed' pdf problems in Sierra.
Try downloading the Repro-5 manual from the first post of page 1 of this thread. If I remember it correctly, Howard saved that version with Adobe Reader, so it should work correctly (I hope).

If you’re on a Mac, get PDF Expert. Fantastic app.

[aMUSEd]

Here is a weird bug: The Repro-1 manual opens correctly in Mac Preview v9 (OS 10.12) but the Repro-5 manual shows just the first few pages, and the rest of the pages are blank, and then freezes Preview when you try to quit. Repro-5 manual opens correctly in Adobe Reader. It's repeatable. And a little annoying, because Preview is my default reader. Time to switch to Adobe?

That's actually a bug that Apple introduced when they 'fixed' pdf problems in Sierra.
Try downloading the Repro-5 manual from the first post of page 1 of this thread. If I remember it correctly, Howard saved that version with Adobe Reader, so it should work correctly (I hope).

If you’re on a Mac, get PDF Expert. Fantastic app.

Or Skim - which is lightweight and free and doesn't rely on Apple pdf tech

[glokraw]

If a daw app has a different setting, is there a conflict that will
cost cpu cycles and or audio quality? In my case, Reaper
'auto-detects' needing 8 'audio reading/processing threads.'
Will matching the daw and plugin settings be needed?
Cheers

Page 4 of the manual talks about that. I assume it applies to Linux version as well:
"Note: Some hosts already offer optional multicore support, and this can
lead to poorer performance for Repro-5. In such cases, please switch one of them off."

Not being a coder, I have a hard time understanding
how daw and plugin support for multi-core could be
the 'same thing'. Different gates, different gatekeepers.
If they were the same, and configs were matched,
what need would there be to turn one off?
They should be smart enough to team up, rather than do battle.
The manual fails to specify whether MC is counting cores, or counting threads,
which is why I ask here. Now that the words mingle,

'Counting Cores' might be a good name for a band
cheers

[Elektronisch]

I took my favorite self-made patches from my Prophet 8 and tried to replicate them on the Repro-5. Sometimes I had to check twice to see if I didn't record the same synth twice - they sounded that similar! On other patches I struggled a bit more to get them to sound the same, since the unique character of the two synths started to show.

I can't believe how good Repro-5 sounds! I remember getting totally psyched by Diva about 5 years ago, and now it happens all over again.

The first synth is always the Prophet 8 (download for uncompressed audio):
https://soundcloud.com/eivind-engedal/d ... -5-patches

Wow indeed, just wow!

[Urs]

Multicore for plug-ins will always be experimental to a degree, since plug-in formats weren't designed with modern CPUs in mind. Back when VST2/3/AU/AAX(RTAS) were originally conceived, a two core machine was a rare occurrance. Everyone expected that CPUs would double in GHz some day, but not in number of cores.

The situation today is that there are as many concepts for multithreading as there are DAWs and plug-ins which do this. We went for a "nice" approach in that we run our threads at the same priority as our plug-in's render function. A DAW could however reserve a CPU core or two by running threads at higher priority. I have no idea what's happening then or how that affects our implementation. This and probably a gazillion of other circumstances (drivers...) can have conflicting effects on the overall performance. Which I guess is why we see so many different experiences.

Anyway, the dev in charge of R5's multithreading might have found a performance bottleneck in our implementation which we might be able to remove before final release. Fingers crossed, but don't expect wonders.

[Howard]

Patch gurus already tweaking some presets? Can anyone help me out with "One of my terns"? I like what Howard did, yet I can't get a nice short percussive chord stub at "day after day" and "night after night" lyrics. Playing with filter and amplifier release and making it shorter definitely helped, but not quite there yet.

So, KVR wizards, how do I really make that sticky hard sync stab? Donno if sticky is the right word, but can't think of a better

I had a go - see attachment. The percussiveness of this version kind of ruins the softness of the original as used at the beginning of "One of My Turns", but hey. I guess they tweaked the Prophet while recording that song.

[mevla]

Hmmm... Since the presets are currently stored in a 'Factory Beta' folder then the host will not be able to find the sounds in recorded sessions when the final release will be out and the folder name will have changed, isn't it ?

Cheers.

[EvilDragon]

Nope. Presets loaded into plugin instances are stored into the DAW project file, not searched from the disk.