Doepfer

Hi!

At the moment I have this tedious step while making music: I make every note slightly shorter so that they don't overlap, in order to get the gate to retrigger for each and every note.

It's occurred to me that the A-140's retrigger input exists for just such a purpose, so I don't have to do that.  Is there any way to get the MCV-24 to output a trigger with each new note, or each subsequent overlapping new note?  This would save me (and maybe other people too?) a lot of time!

Thanks,
Zoë.

> Hi!
>
> At the moment I have this tedious step while making music: I make
> every note slightly shorter so that they don't overlap, in order
> to get the gate to retrigger for each and every note.
>
> It's occurred to me that the A-140's retrigger input exists for
> just such a purpose, so I don't have to do that.  Is there any
> way to get the MCV-24 to output a trigger with each new note, or
> each subsequent overlapping new note?  This would save me (and
> maybe other people too?) a lot of time!
>
> Thanks,
> Zoë.

As far as I remember (the MCV24 is out of production since about 7 years)
this was possible. There was a parameter called "retrigger time" (or
similar) which was used to define the retrigger behaviour. Details should be
mentioned in the user's manual. Or you contact Christian Assall
(software@doepfer.de). He programmed the MCV24 firmware and may be he
remembers this detail.

Best wishes
Dieter Doepfer

> As far as I remember (the MCV24 is out of production since about 7 years)
> this was possible. There was a parameter called "retrigger time" (or
> similar) which was used to define the retrigger behaviour. Details should be
> mentioned in the user's manual. Or you contact Christian Assall
> (software@doepfer.de). He programmed the MCV24 firmware and may be he
> remembers this detail.

Ah, Retriggerzeit!  Yes, I remember briefly experimenting with this without much luck...  I think I only managed to cause a delay in the gate, or something similar...  I'll keep at it then, now I know that is what that thing's for!

Thank you very much.

set retrigger time to 001 or 002. then you should have a new trigger with every new note.


thanks,
Bakis.




________________________________

 From: Zoë Blade <zoe@bytenoise.co.uk>
To: Doepfer_a100@yahoogroups.com 
Sent: Wednesday, April 30, 2014 2:18 PM
Subject: Re: [Doepfer_a100] MCV-24 retrigger out?
 


  
> As far as I remember (the MCV24 is out of production since about 7 years)
> this was possible. There was a parameter called "retrigger time" (or
> similar) which was used to define the retrigger behaviour. Details should be
> mentioned in the user's manual. Or you contact Christian Assall
> (software@doepfer.de). He programmed the MCV24 firmware and may be he
> remembers this detail.

Ah, Retriggerzeit!  Yes, I remember briefly experimenting with this without much luck...  I think I only managed to cause a delay in the gate, or something similar...  I'll keep at it then, now I know that is what that thing's for!

Thank you very much.

> set retrigger time to 001 or 002. then you should have a new trigger with every new note.

OK, having another play with this, I remember what's going on now...  Setting ReTrigTime to 001, it does trigger each note, and I believe it does this by very briefly turning the gate off every time it gets a new note while still playing the last one.  So the gate off coincides with the new note start, then the gate goes back on a short while later.

For really tight timing, I was wondering if there was a way to get the gate to stay open, but with each new note to send a trigger on a separate output, the way I hear old monosynths used to do it way back, and like the A-140's Retrig input seems designed for.

It's not the end of the world if it's not possible, I'm more than happy with the MCV-24 and A-100 as they are. :D  It'd just save a lot of tedious editing while maintaining that tight timing.

Thanks,
Zoë.