Thank you! The "black" skin is awesome - feels so much more like a Prophet-5 than the factory color. Now, how do I get the silver ring on the knobs...?Funkybot's Evil Twin wrote:EDIT - UPDATED: Now 3 skins: 2 for RePro-5 and 1 for RePro-1.
Here's a few skins that take the brownish hue of both GUI's and makes them 1) gray, or 2) almost black. This is basically the same thing I did with RePro-1 (previously called Warmer Gray). This will also act as an update for RePro-1 to show the new browser (currently if you were using the old skin, the old browser was showing up).
Anyway, here's the first RePro-1+5 set of skins:
https://www.dropbox.com/s/cyqj10ir40ve2 ... s.zip?dl=0
Let me know if there's any trouble downloading.
Repro-5 public beta (Repro V1.1)
-
- KVRist
- 438 posts since 15 Oct, 2001 from Santa Fe, NM
-
- Banned
- 35 posts since 18 Nov, 2017
Well, ME80 V2 is also SynthEdit, I believe he didn't re-code it in C++, not even for the second version, yet it's the best software CS-80 to date. Must be he didn't put as much effort in his Memorymoog and Prophet-5 attempts.Nothing but a bog standard synth edit creation from a bygone age. Certainly nothing like a Memorymoog. It's not even close.
And regarding another vintage analogue synth emulation from u-he... Don't set your hopes high. It will take quite a few years until Urs gets back to the subject, as he's already mentioned. And I believe there's one Jupiter model he's not really impressed with, was it 4 or 6, I can't quite remember.
- KVRAF
- 12522 posts since 21 Mar, 2008 from Hannover, Germany
U-He Diva alraedy includes Jupiter 6 modules:V0RT3X wrote: I'd love to see them do a Jupiter 6 emulation next if they did another vintage.
- The "Dual VCO" Osc module is a combination of the Jupiter 8 and 6.
- Like in the Jupiter 6 you have buttons for the waveforms (opposing to waveform knobs in the Jupiter 8 ) to use multiple waveforms at once (like it is also possible in the Prophet 5 ).
- The "Multimode" filter module is the multimode filter of the Jupiter 6 (while the "Cascade" filter is the Jupiter 8 ).
- The "digital" envelope module seems to be from the Jupiter 6 (while the "analogue" envelope seems to be from Jupiter 8 )
- The "HPF pre" module seems to be from Jupiter 8 but is usable for both Jupiters
Due to this I doubt that Urs would do another emulation of the Jupiter 6.
If it would be possible and/or necessary to improve the corresponding modules in Diva somehow he might do that sometimes in the future.
-
Last edited by Ingonator on Sat Nov 25, 2017 7:40 am, edited 4 times in total.
Ingo Weidner
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
- KVRAF
- 1593 posts since 2 Oct, 2016 from Planet X-19
So? They're two different synths. One obviously a lot better at doing what it tried to.Greggers wrote: Well, ME80 V2 is also SynthEdit
Did you ask for opinions just to ignore them, or something?
- KVRAF
- 24404 posts since 7 Jan, 2009 from Croatia
Bottom left corner of Repro-5 GUI, there's the FX button which globally disables FX, for all patches. Might wanna use itKazrog wrote:Of course! I'm sure most will consider them basic and obvious, but for me this sort of sound is why the P5 is such a great synth - it doesn't need any fancy seasoning to sound incredible.
- KVRAF
- 12522 posts since 21 Mar, 2008 from Hannover, Germany
While so far having used the 64-bit VST2 in Live 9.7.5 64-bit I finally found some time to check the 64-bit AAX plugin in Windows 10 64-bit and Pro Tools 12.8.1.
So far the AAX plugin seems to load an work properly and also the LFO host sync seems to work (which in the past sometimes is a problem with certain other AAX plugins).
I tried saving and loading patches and also saving and re-loading a host project in PT 12.8.1 and both seems to be OK so far.
So far the AAX plugin seems to load an work properly and also the LFO host sync seems to work (which in the past sometimes is a problem with certain other AAX plugins).
I tried saving and loading patches and also saving and re-loading a host project in PT 12.8.1 and both seems to be OK so far.
Ingo Weidner
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
- KVRAF
- 9096 posts since 5 Feb, 2004
I have an aging i7 3440 8 core machine, what is the best number of cores to use for Repro-5? The default 4 cores gliches in some presets, my own patches it seems to like better, maybe they are simply simpler. Should I go up or down in number? I'm running in the latest version of Reaper.
Ah, I think I have just been missing turning on the MC button, I don't see a way to turn that on by default, I thought the 4 core setting in the preferences had that covered, but apparently not. I have Repro-5 singing sweetly without a glitch now.
Ah, I think I have just been missing turning on the MC button, I don't see a way to turn that on by default, I thought the 4 core setting in the preferences had that covered, but apparently not. I have Repro-5 singing sweetly without a glitch now.
If you have requests for Korg VST features or changes, they are listening at https://support.korguser.net/hc/en-us/requests/new
- u-he
- Topic Starter
- 30179 posts since 8 Aug, 2002 from Berlin
Regarding CPU and spikes: The current beta does contain some extra debug code. It isn't overly much, but the final should indeed be a tad better.
We also have a few improvements going in the Multicore area.
Coming back to "multicore on by default" feature request... Once it is enabled, the overall CPU usuage *increases* by 20-30% due to the overhead of multithreading, with occasional spikes in-between. Latter seem more pronounces in some DAWs which do their own multithreading. We reckon that, the more audio is in competition for cores, the more likely a Repro-5 instance is forced to compute all its voices on a single core yet again, when there simply isn't a free core for the OS to schedule a thread on. In a worst case, the main rendering core has to wait idle while one other core is doing the heavy lifting.
We have therefore started to implemented a new scheme which should reduce the overhead, and at the same time make sure that the main core isn't ever in an idle waiting status. We'll see how that pans out
We also have a few improvements going in the Multicore area.
Coming back to "multicore on by default" feature request... Once it is enabled, the overall CPU usuage *increases* by 20-30% due to the overhead of multithreading, with occasional spikes in-between. Latter seem more pronounces in some DAWs which do their own multithreading. We reckon that, the more audio is in competition for cores, the more likely a Repro-5 instance is forced to compute all its voices on a single core yet again, when there simply isn't a free core for the OS to schedule a thread on. In a worst case, the main rendering core has to wait idle while one other core is doing the heavy lifting.
We have therefore started to implemented a new scheme which should reduce the overhead, and at the same time make sure that the main core isn't ever in an idle waiting status. We'll see how that pans out
- u-he
- Topic Starter
- 30179 posts since 8 Aug, 2002 from Berlin
GUI: Basti has desaturated and darkened the panel by a notch. This improves the contrast greatly, yet is still pleasant to look at.
-
- KVRer
- 11 posts since 18 May, 2016
Thanks Urs. Either way, you've produced a synth with its own unique texture and playability and that's what a great synth should be.Urs wrote:We have therefore started to implemented a new scheme which should reduce the overhead, and at the same time make sure that the main core isn't ever in an idle waiting status. We'll see how that pans out
-
Arrested Developer Arrested Developer https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=278287
- KVRian
- 677 posts since 8 Apr, 2012
I'm having a strange issue with Repro 1 (in Logic 10.3.2, Sierra):
When i start the sequencer before the region, everything play back correctly.
However, when i start from somewhere where the pattern is already playing, Repro constantly plays f#3 instead of the used notes. (Repro is not in demo mode btw)
When i start the sequencer before the region, everything play back correctly.
However, when i start from somewhere where the pattern is already playing, Repro constantly plays f#3 instead of the used notes. (Repro is not in demo mode btw)
-
- Banned
- 35 posts since 18 Nov, 2017
You dismissed Memorymoog attempt not only on the basis it is a lackluster effort, but chose a "synth edit creation from a bygone age" reasoning as well. "SynthEdit creation from a bygone age" or not, for that matter, can't be considered a valid point, because in ME-80 case SE proved sufficient. It's just a "bog-standard" effort, regardless. If your statement is true. I take it you had a chance to compare it to HW before making such claims.So? They're two different synths. One obviously a lot better at doing what it tried to.Did you ask for opinions just to ignore them, or something?
- u-he
- Topic Starter
- 30179 posts since 8 Aug, 2002 from Berlin
I got mine for 1$ a few years ago, but I had to promise to the previous owner to never do an emulation of it. He disliked it this much. While it does have a lot of perks after full restauration at Lintronics, it simply isn't a polyphonic Minimoog.Aliens wrote:And you've never been tempted to give it the U-he treatment?Urs wrote:I have a Memorymoog, but never tried any emulation of it...Garrincha wrote:Maybe Urs can chime in as he has a Memorymoog I think.
