Repro-5 public beta (Repro V1.1)

[synth_punk]

Nice job Soren. Good luck with the tree, be careful with the chainsaw.

I have just sent over my final small set of patches to team U-He, 12 in total. Not many but I'm too buried in a zillion different projects including a 35 meter (~115 feet) tree that collapse down my garden the other week. Remember the giant willow-like Tree of Souls from Avatar? Okay, twice that amount at least, I swear.

Updated SoundCloud demo of 8 of them:

https://soundcloud.com/luftrum-1/four-patches-repro-5

[braj]

It's a bit more than that. There's material for a whole conspiracy theory unfolding here... hope to have the details soon.

Turns out, just coincidence, as far as I can see. A cracker and a troll just using ISPs/VPNs that point to the same geo location. Nothing worth reading too much into

A cracker means something else in the USA. I was thinking of a guy named Bubba.

A term in Southeastern United States English to describe poor white trash, derived from the Scottish meaning of the verb "to crack," which, in this sense denotes ostentation.

[waltercruz]

I think this thread is doomed. I will go to the office today for a proper computer with a large screen and a mouse and I will spend some time learning how to seperate posts from one thread into another.

I'll also report those who call others "trolls" or "idiots" or "clowns" to the main moderators as these people clearly haven't figured it out. I don't need people who throw name calling and ad hominems to to interact with me and others in a beta testing thread.

Thank you for ruining my Sunday.

Is a second beta planned before final release?

Don't know yet, but it feels enticing to start a new thread once the people I mentioned before have left KVR.

Sad to hear this

Hope you Sunday is better Urs.

I've exchanged some messages with the troll before he revealed himself as a troll, when the user freaked out defending a simple patch that I made and using ad hominem against other users. I didn't support this at all.

Buy hey, time to move on. It's a beautiful rainy afternoon here on Brazil, so, I will play the Repro-5 a bit to relax and welcome the rain

[xx JPRacer xx]

It's a bit more than that. There's material for a whole conspiracy theory unfolding here... hope to have the details soon.

Turns out, just coincidence, as far as I can see. A cracker and a troll just using ISPs/VPNs that point to the same geo location. Nothing worth reading too much into

[Sound Author]

There's material for a whole conspiracy theory unfolding here...

Back and to the left.

Back.

And to the left.

[virtualpt]

@Urs

I am sorry to read that you have had to experience so much negativity in this thread. U-he are a great company, I love Diva & Repro-1. I am really enjoying Repro-5 & am very grateful for your generosity in giving it free to those of us that purchased Repro-1. I have always found U-he to be a very generous company who make fabulous software & treat their customers well. It is a real shame that people feel that it is ok to insult each other in an online synth forum. Hopefully the rest of your Sunday has been better

P

[braj]

I also caved and bought this. It's just too good to pass up for the $99 price.

I bought it for $84! It was my big Black Friday win

[zemoonie]

Quite often reloading a Bitwig project with an instance of Repro-1 will end up with it being totally silent. I usually have to use one of the following workarounds to get it to work again:

* Switch HQ and/or ZZZ on/off
* Switch FX Bypass on/off
* Switch Jaws on/off (for some reason this was the only one working in one project)

[Aspects of Tone]

I've been playing with Repro-5 for several days now. No crashes, glitches or anything. Sounds fantastic. Does smooth, clean, dirty, big, wide, narrow, delicate, chunky. Brilliant.

There were two, very minor, things I came across:

Like someone else reported, To go to preferences I kept clicking on the cog, not the button. Muscle memory is a wonderful thing

I also found a bit of distortion in Lyrebird. I hear this when holding a chord on the TUC Highpasser Pad. After a while you can hear some distortion. I narrowed it down to Lyrebird. It can be mitigated by moving the SoniCon in front and turning down the gain, or turning down the oscillators output in the mixer. Seems like the the power of the Repro-5 is a bit much for the poor bird

A brilliant synth, guys. I would have bought this straight away, only I'm a Repro-1 owner so get it for free. Marvellous and very much appreciated

PS: Running on Win7 64bit, Reaper 5.62/x64, I76700K with 16gb RAM.

[krans]

Just to state the obvious:
The Repro-5's bitcrusher is the nicest sounding, most musical bitcrusher I have ever come across.
It's almost more of a bitcrystallizer than a crusher. And adjusting it together with Velvet gives such a wide spectre of fuzziness. Adorable!

Also - having played around with the Linux build of Repro-5 for a while now, I have met only joy, no issues so far. It's just such a great synth!

[tasmaniandevil]

Regarding testing, to help get this back on topic, is there specific tests and scenarios that would be helpful for us to do?

Very good question.
Since the new browser got almost all my attention over the last couple of months, it’s possible that there are quite a few undetected bugs lurking in Repro-5.

If you want to test specific things, a few areas of interest might be:
* does the modulation section work, or do unexpected things happen
* does host sync work (e.g. there is an issue with s&h going bananas in FL Studio)
* are there any problems when rendering/bouncing/freezing files in the host (someone reported glitches when rendering in Ableton which I could not reproduce over here)
* do host projects get recalled correctly (there is a report about silence when recalling Bitwig projects)
* are there any issues with host automation
* are there any problems when switching presets with HQ enabled (there is a brief CPU surge when switching presets in order to correctly initialize the new preset, this can lead to some short sound glitches, but otherwise should be ok)

[tasmaniandevil]

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)

Hmm, I tried to reproduce this, but could not find anything going wrong.
Does this always happen, or was it a one-time glitch?
Did the same happen with the previous version of Repro-1 (rev. 5332, the release version)?
Do you have a preset where this always happens?
Or do you maybe even have a very simple Logic project which I could test (with just an instance of Repro-1 in it where the problem happens reliably)?

[Stefken]

I think this thread is doomed. I will go to the office today for a proper computer with a large screen and a mouse and I will spend some time learning how to seperate posts from one thread into another.

I'll also report those who call others "trolls" or "idiots" or "clowns" to the main moderators as these people clearly haven't figured it out. I don't need people who throw name calling and ad hominems to to interact with me and others in a beta testing thread.

Thank you for ruining my Sunday.

Is a second beta planned before final release?

Don't know yet, but it feels enticing to start a new thread once the people I mentioned before have left KVR.

A clean slate and adult conversation = a good choice imo.

[tasmaniandevil]

Quite often reloading a Bitwig project with an instance of Repro-1 will end up with it being totally silent. I usually have to use one of the following workarounds to get it to work again:

* Switch HQ and/or ZZZ on/off
* Switch FX Bypass on/off
* Switch Jaws on/off (for some reason this was the only one working in one project)

Since I could not immediately reproduce this over here, I might need a bit more info.
Are you using Bitwig 1 or Bitwig 2?
On Mac or Win or Linux (and which version of the OS)?
Are you using the VST2 or the VST3 version of Repro-1?
Was this happening with the 1.0 release too or only with the newest version?
Any preset where this happens reliably?
Do you have multiple instances of Repro-1 loaded in the project when this happens or just a single one, and does it happen to all instances or just to a few?

[Garrincha]

After one week of intensive work with this thing I'm still flashed. This ist the best VA ever, period! It feels so organic and it has that signature sound that you can't get anywhere else but with a Prophet!

Some Performance observations in Cubase:
I have a i7 3820, so it's 4 real and 4 virtual cores. I use Cubase in multicore-mode and Repro-5 as well. I've tried different combinations but setting both to "multicore" seems the best option over here. Setting Repro-5 on 8 cores works best, all Settings below that take more CPU.

One thing you probably all know, but just in case:

Cubase has an Option called "ASIO guard". This means basically running the selected track on the nominal latency (as set in your Interfaces Drivers) and all other tracks at a much higher latency. That yields a great performance boost. Not all plugins are compatible with that mode but I'm happy to report Repro-5 IS compatible.

But as a downside you have to make sure the Repro-5 track is NOT selected when in playback mode, so Repro-5 is running with a higher latency and hence at lower CPU-consumption. I ran into this several times while mixing a short song-fragment I just put together. Everytime I got dropouts I always had the Repro-track selected.

As I said, you probably knew that already, but just in case somebody with Cubase is wondering why a project with Repro-5 doesn't work as well as the night before