u-he Colour Copy - public beta!

[drzhnn]

Type 1 color should be called "thigh of frightened nymph". One may start thinking about naked ladies. Always a good thing for any creative process.

I have a feature request. Since CoCo can be used in many applications (delay, slap echo, flanger, chorus etc.) people will likely have multiple instances of the plugin in one project. So, I'd love to see a sticker element somewhere on the panel so we can name instances. Like it is in Presswerk.

[EvilDragon]

That's a pretty nifty suggestion!

[Robert Randolph]

Type 1 color should be called "thigh of frightened nymph". One may start thinking about naked ladies. Always a good thing for any creative process.

I have a feature request. Since CoCo can be used in many applications (delay, slap echo, flanger, chorus etc.) people will likely have multiple instances of the plugin in one project. So, I'd love to see a sticker element somewhere on the panel so we can name instances. Like it is in Presswerk.

I would really appreciate that as well. I've run in to some confusion with having multiple CoCo's open and having to buzz around figuring out which one goes where.

[2ZrgE]

Does the beta have any presets? I cannot find any in the usual places.

[Funkybot's Evil Twin]

Does the beta have any presets? I cannot find any in the usual places.

No presets yet. Mentioned in the first post.

[Funkybot's Evil Twin]

I also had something weird that I haven't been able to reproduce yet, but I somehow ended up in a situation where changing the delay base-time setting wasn't immediately updating the ms number in the top-right portion of the green display.

Did not experience this issue yet.
If you find a way to reproduce it, please lemme know.

Update: Ha, I think I found out why this can happen.
If the host stops processing audio, then it won't update the milliseconds display until the host continues to process.
E.g. in Cubase, if you are using the VST3 version and have the already mentioned "stop plugin processing with no audio input" activated.
Or in Reaper, as long as there are no tracks in the project, and the plugin resides on the master track, with the host not playing.

That would explain it. I was using the VST3 version in Cubase at the time. I plan on just sticking to VST2 for this one in Cubase.

[Guenon]

I have a feature request. Since CoCo can be used in many applications (delay, slap echo, flanger, chorus etc.) people will likely have multiple instances of the plugin in one project. So, I'd love to see a sticker element somewhere on the panel so we can name instances. Like it is in Presswerk.

+1

would be very welcome

[Bathrobe]

So why not name it CoCo? Since everybody is calling it that anyway and it´s got a delayish thing to it too.
Oh i forgot the gfx are ready and finished.
Okay carry on.

[M32]

Love this thing! Definitely some warm Mojo going on.

I think i found a bug, i'm in Ableton Live on Win64 bit, and multiple instances of the pugin seem to get mixed up, i had one inserted on a channel, copied this one to a return aux channel, and now the one on the return channel receives input from the audio channel/track where the original instance was/is still inserted. muting/turning of the original plugin does not change this. The send faders of the track are definitely down.

Took me a while to understand what was happening, really couldn't figure out why it sounded so mushy, the two delays with their modulation added together where making the rythm super sloppy.

dubdelay, chorused echo's, this thing's got it all, it certainly is going to be one of those magic fairydust tools you hardly notice until you turn it off. +10!

[zerocrossing]

Nice! I love me a delay plugin. That’s for sure. Hopefully my flight-clogged ears will be back up and running tomorrow and I can gave this some quality time.

[david.beholder]

Type 1 color should be called "thigh of frightened nymph". One may start thinking about naked ladies. Always a good thing for any creative process.

ляжка испуганной Машки, you know

[david.beholder]

Urs why there is no option to have ducking with suppressing all reflections including first?

[sleepcircle]

i thought it was sort of explained in this reply:

The ducking feature isn't really designed to do what you want. The intention was to allow duck the feedback in order to prevent what Howard fittingly labels "sonic mayhem" in the manual. So it's a feature designed to high-regen scenarios. Might take some convincing in the office in order to add the more common wet-ducking mode.

i guess you could have ducking duck ALL of the buffers, but then it seems like it'd be very difficult to get much sustained delay because most of it would never make it to any taps

[jackson881]

Hi all,
It *is* a beta... use at your own risk. Don't install just yet if you're in the middle of an important project. If you do install, consider making a backup first.

This will sound like a dumb question, but what is the "risk" exactly?

I understand that a beta plugin can crash your session or might not be compatible with the final release version, but are there dangers to the computer/drive as a whole?

What exactly should we make a "backup" of?
The song we are working on? Our entire drive?

Sorry to sound paranoid! Just wanted to understand clearly what the risks are.

[Viktor [TUC]]

"Backup" of any project you intend on testing it in, and the risk of using a beta (as with all kinds of software) could be crashes, or feature/sound changes in the final release version.
Things like that.