Ah, interestingHoward wrote:Interesting. I'll ask the guys...
Asked
Permanently running all 5 filters at once would have pushed the CPU a bit too hard, so the filter models were split into two groups (3 in one, 2 in the other) instead. The CPU hit still isn't an indicator of code complexity.
[ANN] Repro-1
- KVRAF
- 3391 posts since 25 Apr, 2011
-
david.beholder david.beholder https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=159839
- KVRAF
- 1914 posts since 13 Sep, 2007
1-3-4 and 2-5 ?Howard wrote:filter models were split into two groups (3 in one, 2 in the other) instead.
Murderous duck!
- KVRAF
- 4197 posts since 23 May, 2004 from Bad Vilbel, Germany
-
david.beholder david.beholder https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=159839
- KVRAF
- 1914 posts since 13 Sep, 2007
I kinda have. You could try my experiment on previous page which is showing different filter groups behavior under certain circumstances.Howard wrote:No idea.
Murderous duck!
- KVRAF
- 3391 posts since 25 Apr, 2011
My guess is 1-2-5 and 3-4. Doesn't say anything though...david.beholder wrote:1-3-4 and 2-5 ?Howard wrote:filter models were split into two groups (3 in one, 2 in the other) instead.
-
david.beholder david.beholder https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=159839
- KVRAF
- 1914 posts since 13 Sep, 2007
Your guess is wrong: it could be only 1-4; 2-3-5 or 1-3-4; 2-5.exmatproton wrote: My guess is 1-2-5 and 3-4. Doesn't say anything though...
Try experiment described on prev page it's clearly showing filters behavior pattern.
Murderous duck!
- KVRAF
- 3391 posts since 25 Apr, 2011
Your experiment resulted in 3 groups, not two.david.beholder wrote:Your guess is wrong: it could be only 1-4; 2-3-5 or 1-3-4; 2-5.exmatproton wrote: My guess is 1-2-5 and 3-4. Doesn't say anything though...
Try experiment described on prev page it's clearly showing filters behavior pattern.
I am not saying you are wrong, but 1-2-5 use less CPU, compared to 3-4.
That's all i am saying. I don't know how they grouped it. And i don't care really. Was wondering about filters 3-4 using more CPU.
- u-he
- Topic Starter
- 30188 posts since 8 Aug, 2002 from Berlin
you are taking this extremely serious 
Unfortunately my computer couldn't run all at once. So I split them up in groups.
Unfortunately my computer couldn't run all at once. So I split them up in groups.
-
david.beholder david.beholder https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=159839
- KVRAF
- 1914 posts since 13 Sep, 2007

Murderous duck!
- KVRAF
- 3391 posts since 25 Apr, 2011
-
Funkybot's Evil Twin Funkybot's Evil Twin https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=116627
- KVRAF
- 12443 posts since 16 Aug, 2006
One thing I love about RePro-1 compared to say DIVA is how well [read: easy] it maps to a keyboard controller. Being so small and specialized, mapping this to a controller works very well and is a ton of fun. I love DIVA but I can't stand how the controls are named because it makes mapping a nightmare. This, in turn, makes DIVA a lot less fun to play than it really should be. RePro-1 keeps the fun level high.
I'm not sure it's possible, but I really wish DIVA used more common names between common parameters to improve mapping. For instance, if the Minimoog osc section is selected just call them Osc1Waveform, Osc2Waveform, etc. Then when I go to Dual VCO or ECO, Oscillators 1 and 2 would have the same parameter names and my automation would work the same way. Or maybe even develop a layer on top of the parameters so users could map the different osc 1s to Parameter 1 for instance. Anyway, I know it's common complaint and there's probably no good answer, but not being able to find a good way to get a tactile response out of DIVA kinda sucks and RePro-1 just reminded me how much it sucks.
I'm not sure it's possible, but I really wish DIVA used more common names between common parameters to improve mapping. For instance, if the Minimoog osc section is selected just call them Osc1Waveform, Osc2Waveform, etc. Then when I go to Dual VCO or ECO, Oscillators 1 and 2 would have the same parameter names and my automation would work the same way. Or maybe even develop a layer on top of the parameters so users could map the different osc 1s to Parameter 1 for instance. Anyway, I know it's common complaint and there's probably no good answer, but not being able to find a good way to get a tactile response out of DIVA kinda sucks and RePro-1 just reminded me how much it sucks.
-
- KVRian
- 628 posts since 18 May, 2010
I've got no idea which filter sounds more analog. I did notice that w.r.t. resonance 1 and 4 seem to form one group, and 2, 3 and 5 another: the peak for 1 and 4 is a bit higher than for 2, 3 and 5 when cutoff is low and resonance high; 1 seems to have a somewhat flatter response, and 4 a sharper peak. But still no idea about the original question, not about which one sounds better.
-
- Banned
- 511 posts since 5 Jul, 2014
Is there an estimated price point for RePro?
I was thinking a bit about this. On one hand, a simple monophonic VST synth (even if it has interchangeable modules depending on the intended Pro One revision being emulated, its architecture at any one time is bound to be fairly simple and 'accurate' towards how a real Pro One would be) implies a good chance to have a somewhat 'budget' oriented product. On the other hand, if RePro ends up going the extra mile to try and be a faithful emulation of all the different Pro One revisions, and offers lots of esoteric customization, it will also reasonably require more development time and a higher price point. It also depends on whether a dedicated FX section is included, as this increases the feature set (IMO, please don't include an FX section. It's so nice to flip through synth presets and just hear a bunch of gorgeous dry synth sounds. Partly an appeal of Monark).
In my opinion a budget conscious price is a good idea for a product like this, but I'd be interested to hear Urs (and others) thoughts on it. I think it's a good opportunity and way to get RePro to stick out in the u-he product line, since if it's quite expensive I suspect many people will be turned off towards it (especially if they own Diva or Ace, which serve most peoples VA needs). The market for a great sounding, extensive Pro One VST emulation at a premium price point is probably much smaller than the general market of a great sounding monophonic VST with an appealing price point. IDK how many people would be convinced on a high price point that the Pro One sound is the exact thing they're missing and paying a premium for it is worth it. Most VST customers probably haven't used a Pro One before and it's a much less well known brand then say, Moog.
Any thoughts? I'm just spitballing here, be interested to hear what Urs is thinking.
I was thinking a bit about this. On one hand, a simple monophonic VST synth (even if it has interchangeable modules depending on the intended Pro One revision being emulated, its architecture at any one time is bound to be fairly simple and 'accurate' towards how a real Pro One would be) implies a good chance to have a somewhat 'budget' oriented product. On the other hand, if RePro ends up going the extra mile to try and be a faithful emulation of all the different Pro One revisions, and offers lots of esoteric customization, it will also reasonably require more development time and a higher price point. It also depends on whether a dedicated FX section is included, as this increases the feature set (IMO, please don't include an FX section. It's so nice to flip through synth presets and just hear a bunch of gorgeous dry synth sounds. Partly an appeal of Monark).
In my opinion a budget conscious price is a good idea for a product like this, but I'd be interested to hear Urs (and others) thoughts on it. I think it's a good opportunity and way to get RePro to stick out in the u-he product line, since if it's quite expensive I suspect many people will be turned off towards it (especially if they own Diva or Ace, which serve most peoples VA needs). The market for a great sounding, extensive Pro One VST emulation at a premium price point is probably much smaller than the general market of a great sounding monophonic VST with an appealing price point. IDK how many people would be convinced on a high price point that the Pro One sound is the exact thing they're missing and paying a premium for it is worth it. Most VST customers probably haven't used a Pro One before and it's a much less well known brand then say, Moog.
Any thoughts? I'm just spitballing here, be interested to hear what Urs is thinking.
- u-he
- Topic Starter
- 30188 posts since 8 Aug, 2002 from Berlin
Too cheap isn't good, and neither is too expensive.
There won't be anything esoteric about it. It's very likely going to be a Pro-One "as is", and maybe a small assortment of different calibrations and parts with varied tolerances, e.g. ADSR chips with "overshooting Sustain bug", alternative filter chips with squelchier-than-normal resonance, VCO chips with off-symmetric triangle, the kind of stuff one would expect from different Pro-Ones sitting next to each other.
However, we have also developed a rather ambitious concept of add-ons, which we won't talk about until we have tried and tested them. This is related to the idea of developing a product family and making use of i/o connectivity for CV and audio routings.
There won't be anything esoteric about it. It's very likely going to be a Pro-One "as is", and maybe a small assortment of different calibrations and parts with varied tolerances, e.g. ADSR chips with "overshooting Sustain bug", alternative filter chips with squelchier-than-normal resonance, VCO chips with off-symmetric triangle, the kind of stuff one would expect from different Pro-Ones sitting next to each other.
However, we have also developed a rather ambitious concept of add-ons, which we won't talk about until we have tried and tested them. This is related to the idea of developing a product family and making use of i/o connectivity for CV and audio routings.
-
david.beholder david.beholder https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=159839
- KVRAF
- 1914 posts since 13 Sep, 2007
Yes and yes.Funkybot's Evil Twin wrote:One thing I love about RePro-1 compared to say DIVA is how well [read: easy] it maps to a keyboard controller. Being so small and specialized, mapping this to a controller works very well and is a ton of fun. I love DIVA but I can't stand how the controls are named because it makes mapping a nightmare. This, in turn, makes DIVA a lot less fun to play than it really should be. RePro-1 keeps the fun level high.
Especially things like: 3-osc mode has 3 levels, 2-osc section has O1/O2 crossfader and no-level etc
Murderous duck!
