[Repro-1] Released!

[Urs]

is there a also chance of a ReproFX version, like ZebraFX or Korgs MS-20FX?

A version that substitutes OSC1 with an audio-Input from the host? maybe, just maybe also in ... ...stereo?

We've been working on a version that has multiple inputs and outputs (4 in, 8 out), but getting this thing to work would have postponed the release way too long. We ran into a lot of problems with a lot of hosts with this. There doesn't seem to be an easy way to get this going smoothly, but we will give it another shot next year or so. (Actually, the code changes to make this work are also required to bring Uhbik up to date for surround stuff)

Nevertheless, this version was merely supposed to allow for interfacing with, say, Eurorack stuff and modular hosts. It wasn't suppsoed to have any stomp box effects built in.

We'll see...

[EvilDragon]

Is there documentation anywhere on how to create a proper skin? I'd ideally like to make this variation a proper option versus just overwriting the current skin. If I could figure that out, I'd share this in car anyone else happened to prefer it.

Create a subfolder with the name of your skin in Repro-1.data/Support/Themes. Make sure that the main skin .txt file is named Repro-1.txt (not Repro-1_orig.txt). Keep the folder structure as it were in the Data folder (Fonts, Images, Scripts).

You don't need to put all files in here, only files that are different vs the original skin. The plugin will use the missing files from the default skin, AFAIK.

[el-bo (formerly ebow)]

Didn't think I liked the brown until I saw it without.

It's not a huge difference but I prefer the gray version. That's what I love about easily skinnable products like this. Find something you don't like on the UI? Personalize it

Absolutely! I normally prefer something, erm...less brown, but in this case it seems to lose so much 'warmth'

[The Sarge!]

Is there documentation anywhere on how to create a proper skin? I'd ideally like to make this variation a proper option versus just overwriting the current skin. If I could figure that out, I'd share this in car anyone else happened to prefer it.

Create a subfolder with the name of your skin in Repro-1.data/Support/Themes. Make sure that the main skin .txt file is named Repro-1.txt (not Repro-1_orig.txt). Keep the folder structure as it were in the Data folder (Fonts, Images, Scripts).

You don't need to put all files in here, only files that are different vs the original skin. The plugin will use the missing files from the default skin, AFAIK.

thanks for the help

now we just need some skins, don´t like the Original

[geronimo]

_ With an Apple machine, you will follow : HD / Library / Application Support / Uhe / Themes _

[ceasless]

If you are on the fence, wondering whether you should get this..

The answer is yes. Yes, you should.

[Razzia]

Disclaimer - I haven't read the manual just yet...

Only kidding about the stick
It's always best to read the manual before making assumptions about a product.

Yeah I know, no worries

Tbh I bought this one almost blind. Had barely tried the beta for half an hour. It's a bad policy, but I've been nothing but impressed by my other uhe purchases and if I trust a dev and I like the idea behind a given plugin I don't like to futz around using a plugin with demo limitations too much unless it's something really expensive.

[jbuonacc]

We've been working on a version that has multiple inputs and outputs (4 in, 8 out), but getting this thing to work would have postponed the release way too long. We ran into a lot of problems with a lot of hosts with this. There doesn't seem to be an easy way to get this going smoothly, but we will give it another shot next year or so. (Actually, the code changes to make this work are also required to bring Uhbik up to date for surround stuff)

Nevertheless, this version was merely supposed to allow for interfacing with, say, Eurorack stuff and modular hosts. It wasn't supposed to have any stomp box effects built in.

We'll see...

well, that sure wouldn't please anyone that's asking to use the Repro-1 fx with something else.

how hard/possible would it be just to "rip" the stomp fx out into their own fx plug-in with some simple (stereo?) in/out? like a "Repro-1 pedal board", fx only? maybe with the filter also, which can be placed before, after, or in between the pedals? i think this would certainly please everyone who is asking for this. even if it weren't included free for Repro-1 users, seems like it would sell pretty well for a lower price.

maybe a bit naive in thinking so, but this seems like something that you could whip together in an afternoon.

If you are on the fence, wondering whether you should get this..

The answer is yes. Yes, you should.

definitely. this synth is outstanding.

[Stefken]

how hard/possible would it be just to "rip" the stomp fx out into their own fx plug-in with some simple (stereo?) in/out? like a "Repro-1 pedal board", fx only? maybe with the filter also, which can be placed before, after, or in between the pedals? i think this would certainly please everyone who is asking for this. even if it weren't included free for Repro-1 users, seems like it would sell pretty well for a lower price..

Just a classic insert fx was what I was thinking about. Nothing fancy like 8 out.
Especially like the wavefolder (and the filter). The other stuff is quite common stuff.

[cowudders]

We've been working on a version that has multiple inputs and outputs (4 in, 8 out), but getting this thing to work would have postponed the release way too long.

Nevertheless, this version was merely supposed to allow for interfacing with, say, Eurorack stuff and modular hosts. It wasn't suppsoed to have any stomp box effects built in.

cv/gate-stuff might be more niche than a simple fx-plug, but having played around with reaktor blocks (the version that has the new cv modules) today, i have to say, this makes so much sense and is bags of fun. my favourite NI product in ages.

That said, i would swap the 'Rounds' effects and 'Driver' for your Repro-suite without thinking twice.

[Granum]

Hey Urs recently bought this (and Satin with my Coupon!) and am really loving it, beautiful instrument. I'm finding the sequencer fun to use but I'm wondering if it would be possible for a setting to restart the sequencer from the beginning when a key is pressed [i.e. while set to 'clock' and 'always' mode]. Or if not maybe a midi-dump feature? It would be much more useful for actual recordings IMO then. The way it is now if I stop my host the sequencer stops where it is and because of this starts at a different point every time I press play. Cheers!

[jbuonacc]

... I'm wondering if it would be possible for a setting to restart the sequencer from the beginning when a key is pressed [i.e. while set to 'clock' and 'always' mode]. Or if not maybe a midi-dump feature? It would be much more useful for actual recordings IMO then. The way it is now if I stop my host the sequencer stops where it is and because of this starts at a different point every time I press play. Cheers!

why are you using 'always' mode if you want it to do this? 'on key' mode does just what you're asking, no?

[Howard]

* scrolling down with the mouse scroll wheel in the preset browser, makes you browse up and vice versa (it's not a plane guys )

This is unfortunately the case with mousewheel on dropdowns as well, across the whole u-he range. I await anxiously for the day this will be a Preferences panel setting... And it seems quite simple to reverse the mousewheel, right, Urs?

I'll look through our "to do" list, and if it's not there already I'll add it. Thanks

Ah... feature request already in there twice (!), "FRAME-587" and "'FRAME-629"

[Granum]

'on key' mode does just what you're asking, no?

Nope, not really, I see 'on key' having a slightly different purpose than the one I'm describing. Because I want to be able to just hit the key once and have it play for the whole track and not have to have tons of clips re-triggering the key or one long key press (which will need to be adjusted etc). This is a workflow issue. But it's a small thing, and perhaps I should just deal with it.

But I must ask, what are the advantages of having "always" stop the sequencer where it is at (when stopping the DAW) and restart from there rather than go back to the beginning when a new note is pressed?

[Urs]

But I must ask, what are the advantages of having "always" stop the sequencer where it is at (when stopping the DAW) and restart from there rather than go back to the beginning when a new note is pressed?

I don't know the details, but I can show this thread to Jan (dev who implemented it). Not sure if he's on KVR though...

What I do know is that we ran into a lot of trouble with the sequencer due to hosts with obvious bugs (one host has particularly sloppy timing). Based on similar experience with our other sequencers we grabbed for a most common denominator to implement the sequencer functionality for now. Once we see how people do we'll improve functionality and hopefully our bug reports reach those host developers.