Repro-5 public beta (Repro V1.1)

[Echoes in the Attic]

Would be nice if the upper and lower mod wheel ranges were automatable. Same for mod destinations.

[AnX]

Both the osc are slightly out of tune anyway, so need calibrating in the Tweaks page. As someone said, you can use that to tune both osc to each other.

[AnX]

IIt isn't possible get the oscillators absolutely in tune (just like the real thing)

Yes it is, i just did it here (which is how i found are both are not tuned correctly)

[hakey]

Don't think so. You can get close, but they still drift slowly.

And, I can't be sure, but I suspect that the offset is slightly different per voice.

Edit - yeah, each voice is different, at least for the P5 oscillator (just like the real thing).

[Funkybot's Evil Twin]

I was just playing around and thinking it was be cool if the Velocity trimmers in the envelopes could be modulation destinations. Use case: expression at minimum = no velocity sensitivity, expression at max = max velocity sensitivity.

[AnX]

Don't think so. You can get close, but they still drift slowly.

Ok, i made it up.

[clangorous]

Preset author defaults to the last name you used when saving a patch, but you need to start from an init preset. If you start from a preset by another author, it defaults to that author's name.

(if it doesn't work that way... must be a bug... @Tas: check that out?)

This is perfect.

[spacepluk]

If someone dosen't get Repro-1/5 running in KXStudio 14.04 (and possible Ubuntu 14.04) there seem to be some system libs incompatibility issues between those two since there are multiple users having the exact same experience.

I can run all other U-He stuff including previous versions of Repro-1 but the beta is a different creature.. Ardour and Carla as well as Reaper (linux) dosen't succeed scanning the pugin and accept it.. Bitwig is able to make it work but I don't have Bitwig and I am to old for Bitwig style music anyway

more info in the linux public beta thread viewtopic.php?f=31&t=424953&start=1065#p6932909

also i am wondering if one users similar experience with Windows 7 is related..
He can run all other U-he stuff except the latest Repros..
viewtopic.php?f=31&t=494717&start=600#p6932145

I hope we can find the reason for this issue

/Anders

Hmm, if it works on Bitwig then it's not a system lib incompatibility, there must be something else going on... Does it work if you try to load Repro before any other VSTs in an empty Ardour project?

[mholloway]

Preset author defaults to the last name you used when saving a patch, but you need to start from an init preset. If you start from a preset by another author, it defaults to that author's name.

(if it doesn't work that way... must be a bug... @Tas: check that out?)

Urs, this is not how it's behaving for me, unless I've misunderstood you.

My steps:

1. Load RePro five, load the INIT patch.
2. do some programming.
3. save the patch, enter my name in Author field.
4. load a new INIT patch
5. do some programming
6. click save -- the author field is empty

Based on your description, it seems the author field should have had my name in it the second time?
I always select INIT to start every patch from scratch, and this has meant typing my name every time I save a new patch.

-Michael

[Frantz]

Why don't you save a new init patch with your name in it?

[Garrincha]

It's both tuning and phase. It isn't possible get the oscillators absolutely in tune (just like the real thing), which means that they are also out of phase. When they're close, there's an audible phasing effect.

And that is the key for those monumental padsounds the original is known for.

Years ago some VAs used to have OSCs with static start-phase (not free running like a real analog synth) and exact pitch, namely the early Arturia plugins. The static OSCs was one reason for them sounding very digital and lifeless.

[Subarumannen]

If someone dosen't get Repro-1/5 running in KXStudio 14.04 (and possible Ubuntu 14.04) there seem to be some system libs incompatibility issues between those two since there are multiple users having the exact same experience.

I can run all other U-He stuff including previous versions of Repro-1 but the beta is a different creature.. Ardour and Carla as well as Reaper (linux) dosen't succeed scanning the pugin and accept it.. Bitwig is able to make it work but I don't have Bitwig and I am to old for Bitwig style music anyway

more info in the linux public beta thread viewtopic.php?f=31&t=424953&start=1065#p6932909

also i am wondering if one users similar experience with Windows 7 is related..
He can run all other U-he stuff except the latest Repros..
viewtopic.php?f=31&t=494717&start=600#p6932145

I hope we can find the reason for this issue

/Anders

Hmm, if it works on Bitwig then it's not a system lib incompatibility, there must be something else going on... Does it work if you try to load Repro before any other VSTs in an empty Ardour project?

Ardour can not scan the vst correctly since the plugin thows an exception, Repro-1 or 5 will thus never be avaliable to insert on a midi track. Carla will not successfully scan the vst and will not present it as a avaliable plugin. The same goes for Reaper. Renoise (is reported to crash while scanning for vst plugins)
Ubuntu 14.04 is the common denominator here..
/Anders

[Subarumannen]

If someone dosen't get Repro-1/5 running in KXStudio 14.04 (and possible Ubuntu 14.04) there seem to be some system libs incompatibility issues between those two since there are multiple users having the exact same experience.

I can run all other U-He stuff including previous versions of Repro-1 but the beta is a different creature.. Ardour and Carla as well as Reaper (linux) dosen't succeed scanning the pugin and accept it.. Bitwig is able to make it work but I don't have Bitwig and I am to old for Bitwig style music anyway

more info in the linux public beta thread viewtopic.php?f=31&t=424953&start=1065#p6932909

also i am wondering if one users similar experience with Windows 7 is related..
He can run all other U-he stuff except the latest Repros..
viewtopic.php?f=31&t=494717&start=600#p6932145

I hope we can find the reason for this issue

/Anders

Hmm, if it works on Bitwig then it's not a system lib incompatibility, there must be something else going on... Does it work if you try to load Repro before any other VSTs in an empty Ardour project?

According to wise guys (Ardour and Carla devs) that looked into this it indeed seems to be incompability with system libs since none of the other hosts can even scan Repro Beta VST. The plugin throws an exception. The reason it might work in Bitwig could be that Bitwig supposedly doesn't use any C++ by itself...

This is what I have picked up reading the devs trying to debug the issue.

If Ardour, Carla, Renoise and Reaper all runs every U-he plugin just fine except the Beta, it sure seems like the Beta is at least very different to the rest of the U-he plugins. I would guess there is an gcc4/gcc5 ABI issue like falktx suggested.

Disclaimer: I do not code

[mholloway]

Why don't you save a new init patch with your name in it?

Yeah, that’s probably what I’ll do, thanks.

I liked loading the factory init simply because I could do it quickly by right clicking the Preset Name area on the main page and then selecting it (it’s always there, down at the bottom) — this meant I didn’t have to actually switch pages to the preset page and sort through any folders. So it was just fast, but means having to enter my name again.

[twisted-space]

Hi Urs, U-he team.
I have a weird problem with the beta, both Repro-1 and Repro-5 v6634

Repro-1 v5332 works fine, as do all my other U-he plugins.

A first thought, this sounds like you have Repro-1 5332 and the new beta 6634 both installed at the same time. Could this be? Did you maybe install the new beta to a different location than the 1.0 release version of Repro-1?
If so, this might explain the issues you are experiencing. The host and Repro are getting confused about which Repro-1.data folder they should access and then create those issues as a result.
It might be best to write us a mail to support @ u-he, so we can get this sorted.

Nope, only have v6634 installed, though I have installed, uninstalled and re-installed both versions a few times while troubleshooting.
Emailed