[Repro-1] Public Beta

[aaron aardvark]

ya'll to young

It was about 1980, I was about 20 years old, and used a computer for the first time ever in a computer class (Fortran). You had to type out a bloody punch card for every command line, turn in your stack of cards, and come back hours later to see what happened (it never worked right the first time). I don't miss those days.

[aaron aardvark]

As of this month, I have owned a real Pro-One for 35 years. I still don't fully understand the modulation section (yes, I've read the manual). Maybe in another 35 years I'll have it totally figured out.

) It's actually described really nice in u-he manual: three modulation sources which can be mixed and routed through two different paths to five modulation targets.

(@EvilDragon: I've followed you advice and read that f**** manual. It was good advice!)

The Repro manual looks pretty identical to the Pro-One manual in regards to the modulation signal flow, though sometimes you flip some switches, move the Pro-One Mod Wheel and the actual sound doesn't respond like you think it might, or you can't hear any difference. The Pro-One was my first synth, so it didn't soak in very fast what was happening. In some regards I never got past the newbie phase. Now that Repro has a memory (for saving good patches), and you can check out other people's patches, I'd be less apprehensive about experimenting.

[Urs]

Repro-1 Library = In the near future

Looking forward to hear what you can do with this synth. It seems to lend itself nicely to the type of sounds you made so far.

+1

[serpentmoon]

so...for what its worth i figured the best way to get to know this synth was to write a track with it.. had about a half hours work and most of the track demoed out. ( using the most recent version of FL studio 12 64bit, my processor is more than adequate as is my ram)

ive found that running multiple instances of Repro cause my daw to freeze and crash. which isnt a problem ive run into in a long time.

since this thing is still in beta i figured you guys might want to know about that... it might be my machine( though i really dont have any issues running multiple instances of other processor/ram intensive vsts or programs) or it could be my daw... but who knows.. figured it could hurt to put my issues out there.

other than the issues ive encountered.. im loving the hell out of this thing and cant wait for the final release.

-Thanks for your time
-VRG

[Urs]

Setting the clock to "key" mode is an interesting feature when the sequencer is in "play" mode. I tried sequencing velocity and assigning velocity to the filter cutoff, to create variations in the sound from note to note.

On second thought, this use case doesn't really make sense. Why wouldn't I just play my notes with different velocities? lol. You can ignore my previous post.

Maybe I don't understand what the clock "key" mode is for. Hooking up an external sequencer to this synthesizer, I guess?

Hehehe... I know I know.

On the real hardware it was common practice to program the sequencer and clock it from an external source. The rimshot of the TR-909 was an infamous example for this: Every time the 909 would play a rimshot, the sequencer would play the next step. Of course using drum machines and other sources, people weren't restricted to sending regular 1/8 or 1/16 notes, they could play any rhythm. It was a thing.

We added the "key" option so people can use any key to advance the Arp/Sequencer, much in a similar way as they used the external trigger source back then.

However, it's the first time we've implemented such a feature, so we're happy to get some feedback and discuss where to take it

[Urs]

ive found that running multiple instances of Repro cause my daw to freeze and crash. which isnt a problem ive run into in a long time.

Yep, we found that changing the Clock rate (I think?) while the sequencer is playing can cause stalls/freezes of up to several seconds. It's something we missed and we're already onto it.

I don't know about crashes though. If you have a track/project for FL we'd happily check it out if you send it to support@u-he.com

[aaron aardvark]

Same behaviour on one Pro-One, self oscillation starts at about 65%. Different on another Pro-One where it starts just above 50%.

The main difference in "knobbage" is, they used kinda cheap pots. The first 10% and last 10% don't do anything on most. Might also be age and stuff, but as far as I can remember, I've seen this on every Pro-One.

This. The knobs and switches were definitely on the cheap side. Not the worst I have seen, but could have been better.

When I first had my Pro-One, I was nervous the switches would break because their operation seemed so rough. 35 years later, they haven't broken yet, though some are a bit dodgy. Though not long after I bought it, I had to get it fixed on warranty because it stopped working properly; I forget the symptoms. The Repro switches are nice and smooth.

[EvilDragon]

(@EvilDragon: I've followed you advice and read that f**** manual. It was good advice!)

No kidding!

[aaron aardvark]

Thanks to those that posted patches. I agree that red stars on red is the not easiest to read.

I have modified the star's pictures for another contrast .

Are you a u-he employee, or a gui tweeker, or that is adjustable, or you photo-shopped that or ?

[aaron aardvark]

when I marked some patches favorites, those stars went away after I re-booted Repro-1

I just checked with Mac VST2 and VST3, doesn't happen here. Do the stars stay/come back if you close the GUI before closing the project or removing/replacing Repro?

Repro locked up with a noted droning away on one occasion.

Did you maybe double-click a note on the GUI keyboard?

There is a good chance my favorite stars disappeared after a note was locked on and I had to force quit Cubase. It's only happened once. Your second question: I'm usually using a real keyboard, though sometimes I use the virtual one. Not sure what the answer is on double-clicking a note. I've only used it a couple of nights.

[Urs]

Thanks to those that posted patches. I agree that red stars on red is the not easiest to read.

I have modified the star's pictures for another contrast .

Are you a u-he employee, or a gui tweeker, or that is adjustable, or you photo-shopped that or ?

I guess it's photoshopped

[aaron aardvark]

Maybe this is because I was doing too much too fast, though Repro locked up with a noted droning away on one occasion. I had to force quit Cubase. Not sure if a panic button is needed.

Hi Aaron, doing things too fast could actually have been the cause. One of the remaining issues we are still working on are some situations where CPU spikes can occur (as real-time peaks in the Cubase ASIO load meter). E.g. if you turn the clock rate control a lot, this can happen. Sometimes those spikes can last several seconds, 'locking up' the synth during this time. But usually, if you wait a short while, the ASIO meter will go back to normal, so you should not need to force quit Cubase in most situations. This will of course be solved in the final version of Repro-1.

Thank you for replying. When I had Mac OSX 10.6.8, it was common my u-he synths (does not include Repro) would lock up the gui, especially when doing various things quickly, during the past year or so. Now that I'm using Mac OSX 10.9 (the past several months), my u-he synths rarely lock up their gui.

[Urs]

lock up their gui.

The current issue is in the debugging code we left in for beta testing. It'll be gone with the final version.

[lentferj]

Tested on Bitwig 1.3.13 and Ardour 5.3.4 on Linux ( Debian 8 ). Works great so far, cpu usage is not a problem (but I have a 12 core Xeon, so I my system might not count as "average"). And oh boy, it sounds so great right out of the box. No extra processing needed. I think I spent almost an hour now only improvising on the "Larger Than A Memory" patch. Urs + guys - great, outstanding work!

PS: When will we see official Linux support (and maybe LV2) btw

[Urs]

PS: When will we see official Linux support (and maybe LV2) btw

Dunno about LV2... but our infrastructure seems to mostly run well enough so that this might be offical on Linux from day one.

It's just that our support team doesn't have that Linux experience. So we need to rely on Abique and the forum thread for Linux specific support issues.