u-he Repro (Repro-1 & Repro-5) released
- KVRAF
- 5488 posts since 15 Dec, 2011 from Bucharest, Romania
-
AdamWysokinski AdamWysokinski https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=393916
- KVRist
- 243 posts since 16 Feb, 2017
I really miss Diva's "Offline Acc" option. U-he, add it to Bazille and Repro, please..e@rs wrote:It's an old one, C2D E6750. But my point is that I can use multiple instances of Diva or Bazille in middle quality, but not Repro-5, because no such option exists for this one.EvilDragon wrote:What's your CPU?
-
fluffy_little_something fluffy_little_something https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=281847
- Banned
- 12880 posts since 5 Jun, 2012
Why not? 2 is multie@rs wrote:Only 2 cores here, so no MC for me.
-
- KVRAF
- 2642 posts since 23 Jun, 2006 from Hungary
Like Repro-5. I've found 1-2 piano sounds that are super cool
Youtube channel: https://youtube.com/@SoftSynthPortal
- KVRAF
- 21196 posts since 8 Oct, 2014
Is it possible that with some hosts, multi core simply doesn't work right? I haven't tried it in Cubase yet but in MuLab it's a train wreck with volume cutting out constantly.noiseboyuk wrote:Don't know what your system is but CPU is actually very reasonable for me in Cubase with MC turned on - drops by 75% when I do that.e@rs wrote:Sounds delicious, but the CPU usage is brutal. Can only use maximum 4 voices.
- KVRAF
- 5488 posts since 15 Dec, 2011 from Bucharest, Romania
I think it has to be more than 2 cores for MC to have a beneficial effect. For me it definitely doesn't help enabling it.fluffy_little_something wrote:Why not? 2 is multie@rs wrote:Only 2 cores here, so no MC for me.
-
fluffy_little_something fluffy_little_something https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=281847
- Banned
- 12880 posts since 5 Jun, 2012
Jesus, Reaper is the least intuitive DAW I ever tried. I can't even get a single sound out of it (it says output not connected, but there is nothing to connect in the dropdown menu), so much for trying to find out whether Mulab is the bottleneck...
-
fluffy_little_something fluffy_little_something https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=281847
- Banned
- 12880 posts since 5 Jun, 2012
On my system the multi-core support works fine with Repro (unlike with Diva), so I suppose it is not Mulab's fault.wagtunes wrote:Is it possible that with some hosts, multi core simply doesn't work right? I haven't tried it in Cubase yet but in MuLab it's a train wreck with volume cutting out constantly.noiseboyuk wrote:Don't know what your system is but CPU is actually very reasonable for me in Cubase with MC turned on - drops by 75% when I do that.e@rs wrote:Sounds delicious, but the CPU usage is brutal. Can only use maximum 4 voices.
-
Funkybot's Evil Twin Funkybot's Evil Twin https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=116627
- KVRAF
- 11527 posts since 16 Aug, 2006
Let's keep a few things in mind on CPU usage:
1. Different buffer settings will have a huge impact. Someone who enters notes in a PRV and is operating at a 1024 buffer will report a very different experience than someone running 64 samples.
2. Different hosts CPU meters will calculate CPU differently. Reaper I believe shows the average usage between all cores. So one instance of RePro-5 in Reaper will look very differently than in Studio One which shows the maximum core usage even with all other variables being the same.
3. A host with an ASIO guard like functionality or "Dual-Buffer/Lot Latency Monitoring" setup will also be a misleading on CPU usage. For instance, realtime recording at 64 sample buffer might show much higher CPU usage than playback. So what are you measuring? Realtime CPU usage with monitoring enabled or playback CPU usage?
4. Different hosts will balance CPU usage between cores differently. This will become even more important as you add effects, busses, multiple instances, etc.
5. The different Multi-Core performance from host to host and CPU to CPU is why U-he didn't build an option to turn it on by default. They wanted users to proactively decide in what scenarios they wanted to turn MC on because the impact of it varied so much.
1. Different buffer settings will have a huge impact. Someone who enters notes in a PRV and is operating at a 1024 buffer will report a very different experience than someone running 64 samples.
2. Different hosts CPU meters will calculate CPU differently. Reaper I believe shows the average usage between all cores. So one instance of RePro-5 in Reaper will look very differently than in Studio One which shows the maximum core usage even with all other variables being the same.
3. A host with an ASIO guard like functionality or "Dual-Buffer/Lot Latency Monitoring" setup will also be a misleading on CPU usage. For instance, realtime recording at 64 sample buffer might show much higher CPU usage than playback. So what are you measuring? Realtime CPU usage with monitoring enabled or playback CPU usage?
4. Different hosts will balance CPU usage between cores differently. This will become even more important as you add effects, busses, multiple instances, etc.
5. The different Multi-Core performance from host to host and CPU to CPU is why U-he didn't build an option to turn it on by default. They wanted users to proactively decide in what scenarios they wanted to turn MC on because the impact of it varied so much.
Last edited by Funkybot's Evil Twin on Sun Dec 17, 2017 7:44 pm, edited 1 time in total.
-
midi_transmission midi_transmission https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=298730
- KVRian
- 989 posts since 13 Feb, 2013
Just one question... I really like the sound from the repo-5. Well done. The string patches sounds really perfect on this thing. But the CPU load is pretty high. Even my i7 4ghz has about 10% load for complrex chords. It maybe great when you want to have the last 10% sound, but I'm wondering what you think about it as a bread and butter subtractive synth that you use a lot in your projects? Maybe that's not the role from this thing?
- KVRAF
- 2946 posts since 31 Jan, 2003 from Ghent, Belgium
CPU usage of Repro5 is a lot better than I expected it to be. With most presets it's about 50% CPU usage (Cubase ASIO performance meter) with 8 notes held. My CPU = i5-2410M (dual core, 4 threads, 2,3 Ghz).
The worst CPU-hungry plugin I have is Kaivo: 4 voices = maximum = 80% CPU
The worst CPU-hungry plugin I have is Kaivo: 4 voices = maximum = 80% CPU
- KVRAF
- 21196 posts since 8 Oct, 2014
Unless you've got a space age rig, I doubt you're using too many instances of this unless you do a part and then freeze the track and keep doing this as you go along.midi_transmission wrote:Just one question... I really like the sound from the repo-5. Well done. The string patches sounds really perfect on this thing. But the CPU load is pretty high. Even my i7 4ghz has about 10% load for complrex chords. It maybe great when you want to have the last 10% sound, but I'm wondering what you think about it as a bread and butter subtractive synth that you use a lot in the project? Maybe that's not the role from this thing?
-
fluffy_little_something fluffy_little_something https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=281847
- Banned
- 12880 posts since 5 Jun, 2012
I had done that the first time it launched.chk071 wrote:Sounds like you need to set up your audio device.
Well, I managed to make it sound by now.
But I don't know how to reopen the Repro GUI (I had closed it), there is no button.
Compared to Mulab, Reaper seems a total failure in terms of user friendliness.
-
- KVRAF
- 5627 posts since 23 Mar, 2006 from pendeLondonmonium
Click on the green 'FX' button.
This got me too when I first tried reaper...not use friendly at all. I know.
This got me too when I first tried reaper...not use friendly at all. I know.