Yahoo Groups archive

Doepfer

Index last updated: 2026-04-29 00:15 UTC

Thread

legato slew control

legato slew control

2009-04-04 by Stu Grimshaw

hallo group,

does anyone have an elegant way of reproducing the legato-enables-slide behaviour of most synths that i know?

i tried the archives, but didn't hit the right keywords :)

thanks, stu

Re: [Doepfer_a100] legato slew control

2009-04-06 by Florian Anwander

Hello Stu

> does anyone have an elegant way of reproducing the legato-enables-slide behaviour of most synths that i know?
Why not simply Gate as CV for the A-171?

or
CV -> multiple ---------> A150 I/O1 O/I-------> VCO
       multiple -> A170 -> A150 I/O2
Gate--------------------> A150 CV

With gate=0V the switch will connect I/O1 to O/I, means CV direct to VCO
With gate=1V (=legato) the switch will connect I/O2 to O/I, means CV via 
slwelimiter to VCO.

Florian

Re: legato slew control

2009-04-06 by Stu Grimshaw

> Why not simply Gate as CV for the A-171?

that's what i thought, but there are two problems: cv input increases the speed of the slew not the time (weird), and even inverting the gate doesn't work, because when the gate switches on, the slew gets increased before the voltage starts to change, i.e. you only have minimum slew time when the gate is at 0v, when a key is not pressed. as soon as a key is pressed, you have a the longer slew.

> 
> or
> CV -> multiple ---------> A150 I/O1 O/I-------> VCO
>        multiple -> A170 -> A150 I/O2
> Gate--------------------> A150 CV
> 
> With gate=0V the switch will connect I/O1 to O/I, means CV direct to VCO
> With gate=1V (=legato) the switch will connect I/O2 to O/I, means CV via 
> slwelimiter to VCO.

> as far as i can see - i'm not at home - this will have the same problem. the higher slew kicks in as soon as you play the next note, causing a slide.

i'm off to england tomorrow, so i'll not be able to test your patch till monday. i'll report back :)

Re: legato slew control

2009-04-07 by falafelbiels

Hi there,

I find this works:

take an AD envelope with zero A and a little D (I use A-143-2 with everyting to zero, except Decay), feed that to the CV in of an a-171 VC Slew Limiter and it works. While the key is held, the output of the AD is low, so the rate of the slewlimiter is low as well. On retriggering CV is added to the slew rate, et presto.

--- In Doepfer_a100@yahoogroups.com, "Stu Grimshaw" <grimshaw@...> wrote:
Show quoted textHide quoted text
>
> 
> > Why not simply Gate as CV for the A-171?
> 
> that's what i thought, but there are two problems: cv input increases the speed of the slew not the time (weird), and even inverting the gate doesn't work, because when the gate switches on, the slew gets increased before the voltage starts to change, i.e. you only have minimum slew time when the gate is at 0v, when a key is not pressed. as soon as a key is pressed, you have a the longer slew.
> 
> > 
> > or
> > CV -> multiple ---------> A150 I/O1 O/I-------> VCO
> >        multiple -> A170 -> A150 I/O2
> > Gate--------------------> A150 CV
> > 
> > With gate=0V the switch will connect I/O1 to O/I, means CV direct to VCO
> > With gate=1V (=legato) the switch will connect I/O2 to O/I, means CV via 
> > slwelimiter to VCO.
> 
> > as far as i can see - i'm not at home - this will have the same problem. the higher slew kicks in as soon as you play the next note, causing a slide.
> 
> i'm off to england tomorrow, so i'll not be able to test your patch till monday. i'll report back :)
>

Re: [Doepfer_a100] Re: legato slew control

2009-04-07 by Florian Anwander

Hello falafelbiels

> I find this works:
> take an AD envelope with zero A and a little D (I use A-143-2 with everyting to zero, except Decay), feed that to the CV in of an a-171 VC Slew Limiter and it works. While the key is held, the output of the AD is low, so the rate of the slewlimiter is low as well. On retriggering CV is added to the slew rate, et presto.
Yes, you are right! That is the way it should work.

I forgot, that the new gate will disable the slew again immediately.

Florian

Re: legato slew control

2009-04-08 by Stu Grimshaw

that looks promising! thanks, i'll give it a go as soon as i'm home. looks like a good use for a passive decay envelope, which is really easy to build, and small enough to build it straight into the slew limiter module.

thanks for the post,

stu
Show quoted textHide quoted text
> 
> take an AD envelope with zero A and a little D (I use A-143-2 with everyting to zero, except Decay), feed that to the CV in of an a-171 VC Slew Limiter and it works. While the key is held, the output of the AD is low, so the rate of the slewlimiter is low as well. On retriggering CV is added to the slew rate, et presto.
> 
> --- In Doepfer_a100@yahoogroups.com, "Stu Grimshaw" <grimshaw@> wrote:
> >
> > 
> > > Why not simply Gate as CV for the A-171?
> > 
> > that's what i thought, but there are two problems: cv input increases the speed of the slew not the time (weird), and even inverting the gate doesn't work, because when the gate switches on, the slew gets increased before the voltage starts to change, i.e. you only have minimum slew time when the gate is at 0v, when a key is not pressed. as soon as a key is pressed, you have a the longer slew.
> > 
> > > 
> > > or
> > > CV -> multiple ---------> A150 I/O1 O/I-------> VCO
> > >        multiple -> A170 -> A150 I/O2
> > > Gate--------------------> A150 CV
> > > 
> > > With gate=0V the switch will connect I/O1 to O/I, means CV direct to VCO
> > > With gate=1V (=legato) the switch will connect I/O2 to O/I, means CV via 
> > > slwelimiter to VCO.
> > 
> > > as far as i can see - i'm not at home - this will have the same problem. the higher slew kicks in as soon as you play the next note, causing a slide.
> > 
> > i'm off to england tomorrow, so i'll not be able to test your patch till monday. i'll report back :)
> >
>

Re: legato slew control

2009-04-14 by falafelbiels

OOO Ooooh, if you happen to have a schematic for that passive decay envelope, I'd love to have a peek at it! (and of course save a copy)

Never tooe many envelopes...

--- In Doepfer_a100@yahoogroups.com, "Stu Grimshaw" <grimshaw@...> wrote:
Show quoted textHide quoted text
>
> that looks promising! thanks, i'll give it a go as soon as i'm home. looks like a good use for a passive decay envelope, which is really easy to build, and small enough to build it straight into the slew limiter module.
> 
> thanks for the post,
> 
> stu
> 
> 
> > 
> > take an AD envelope with zero A and a little D (I use A-143-2 with everyting to zero, except Decay), feed that to the CV in of an a-171 VC Slew Limiter and it works. While the key is held, the output of the AD is low, so the rate of the slewlimiter is low as well. On retriggering CV is added to the slew rate, et presto.
> > 
> > --- In Doepfer_a100@yahoogroups.com, "Stu Grimshaw" <grimshaw@> wrote:
> > >
> > > 
> > > > Why not simply Gate as CV for the A-171?
> > > 
> > > that's what i thought, but there are two problems: cv input increases the speed of the slew not the time (weird), and even inverting the gate doesn't work, because when the gate switches on, the slew gets increased before the voltage starts to change, i.e. you only have minimum slew time when the gate is at 0v, when a key is not pressed. as soon as a key is pressed, you have a the longer slew.
> > > 
> > > > 
> > > > or
> > > > CV -> multiple ---------> A150 I/O1 O/I-------> VCO
> > > >        multiple -> A170 -> A150 I/O2
> > > > Gate--------------------> A150 CV
> > > > 
> > > > With gate=0V the switch will connect I/O1 to O/I, means CV direct to VCO
> > > > With gate=1V (=legato) the switch will connect I/O2 to O/I, means CV via 
> > > > slwelimiter to VCO.
> > > 
> > > > as far as i can see - i'm not at home - this will have the same problem. the higher slew kicks in as soon as you play the next note, causing a slide.
> > > 
> > > i'm off to england tomorrow, so i'll not be able to test your patch till monday. i'll report back :)
> > >
> >
>

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.