Yahoo Groups archive

Doepfer

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

Thread

A160-5 latency

A160-5 latency

2016-10-17 by jaccoville@yahoo.com

Hello Doepfer users,

When setting up a patch with my A160-5 clockdivider I noticed that when I send a CV to the multiplier input for creating ratcheting there is a latency of one sequencer step.
To be clear: I made the patch classic.

See example in the manual.
So one A155.

The point is that I have to set the CV step on sequencer step, let's say, 7 to get the ratcheting effect on step 8 in the sequence.

Is this normal?

Best regards

Jacco Ville

Re: [Doepfer_a100] A160-5 latency

2016-10-17 by achtung_999

This is stated in the manual. And if you think about it, it makes sense doesn't it?
There are no electronics yet, that have psychic powers ;-)

Ernst

Show quoted textHide quoted text
On Mon, Oct 17, 2016 at 9:02 PM, jaccoville@yahoo.com [Doepfer_a100] <Doepfer_a100@yahoogroups.com> wrote:

Hello Doepfer users,


When setting up a patch with my A160-5 clockdivider I noticed that when I send a CV to the multiplier input for creating ratcheting there is a latency of one sequencer step.
To be clear: I made the patch classic.

See example in the manual.
So one A155.

The point is that I have to set the CV step on sequencer step, let's say, 7 to get the ratcheting effect on step 8 in the sequence.

Is this normal?

Best regards

Jacco Ville


Re: [Doepfer_a100] A160-5 latency

2016-10-17 by Jacco Ville

Well for me this note in the manual is about the clock input which has to be stable and infact it is in this setup.

Only the CV input is getting a voltage which fluctuates to get the ratcheting    effect. 

Jacco 
Show quoted textHide quoted text
> Op 17 okt. 2016 om 23:06 heeft achtung_999 heinrich.himmelwasser@gmail.com [Doepfer_a100] <Doepfer_a100@yahoogroups.com> het volgende geschreven:
> 
> This is stated in the manual. And if you think about it, it makes sense doesn't it?
> There are no electronics yet, that have psychic powers ;-)
> 
> Ernst
> 
> 
>> On Mon, Oct 17, 2016 at 9:02 PM, jaccoville@yahoo.com [Doepfer_a100] <Doepfer_a100@yahoogroups.com> wrote:
>>  
>> Hello Doepfer users,
>> 
>> 
>> When setting up a patch with my A160-5 clockdivider I noticed that when I send a CV to the multiplier input for creating ratcheting there is a latency of one sequencer step. 
>> To be clear: I made the patch classic. 
>> 
>> See example in the manual. 
>> So one A155. 
>> 
>> The point is that I have to set the CV step on sequencer step, let's say, 7 to get the ratcheting effect on step 8 in the sequence. 
>> 
>> Is this normal?
>> 
>> Best regards 
>> 
>> Jacco Ville
> 
>

AW: [Doepfer_a100] A160-5 latency

2016-10-18 by yahoo@doepfer.de

> Hello Doepfer users,
>
> When setting up a patch with my A160-5 clockdivider I noticed
> that when I send a CV to the multiplier input for creating
> ratcheting there is a latency of one sequencer step.
> To be clear: I made the patch classic.
>
> See example in the manual.
> So one A155.
>
> The point is that I have to set the CV step on sequencer step,
> let's say, 7 to get the ratcheting effect on step 8 in the sequence.
>
> Is this normal?
>
> Best regards
>
> Jacco Ville

I just used the A-160-5 for a performance in Munic (DigitalAnalog Festival)
and cannot confirm this behaviour. You should use the pre output of the
A-155 to avoid any delay. If this does not help please contact Christian
Assall (software@doepfer.de). He programmed the A-160-5 firmware together
with the A-155.

Best wishes
Dieter Doepfer

Re: AW: [Doepfer_a100] A160-5 latency

2016-10-18 by Jacco Ville

Hello Dieter,

I made the patch exactly by the book. 
To be sure I made it once again. 

What I notice is that once the CV from the A155 sends a voltage the A160-5 does shows this by increasing the leds BUT the actual ratcheting of the notes to my A140 adsr follows AFTER the CV has passed, so the next note makes the ratcheting sequence. 
For me it seems not logical. 
There is always a steady masterclock to the "clock in" of the A160-5. 

Best regards

Jacco Ville




Op 18 okt. 2016 om 09:09 heeft yahoo@doepfer.de [Doepfer_a100] <Doepfer_a100@yahoogroups.com> het volgende geschreven:
Show quoted textHide quoted text
>> Hello Doepfer users,
>> 
>> When setting up a patch with my A160-5 clockdivider I noticed
>> that when I send a CV to the multiplier input for creating
>> ratcheting there is a latency of one sequencer step.
>> To be clear: I made the patch classic.
>> 
>> See example in the manual.
>> So one A155.
>> 
>> The point is that I have to set the CV step on sequencer step,
>> let's say, 7 to get the ratcheting effect on step 8 in the sequence.
>> 
>> Is this normal?
>> 
>> Best regards
>> 
>> Jacco Ville
> 
> I just used the A-160-5 for a performance in Munic (DigitalAnalog Festival)
> and cannot confirm this behaviour. You should use the pre output of the
> A-155 to avoid any delay. If this does not help please contact Christian
> Assall (software@doepfer.de). He programmed the A-160-5 firmware together
> with the A-155.
> 
> Best wishes
> Dieter Doepfer
> 
> 
> 
> 
> ------------------------------------
> 
> ------------------------------------
> 
> 
> ------------------------------------
> 
> Yahoo Groups Links
> 
> 
>

Re: AW: [Doepfer_a100] A160-5 latency

2016-10-18 by Florian Anwander

Hello Jacco,

just think twice:

The voltage which sets the division/multiplication factor, comes 
slightly after the clock-tick, that should be multiplied. So the 
multiplying/dividing will happen for the next clock tick. Why comes the 
Voltage after the clocktick? Because there is a minimal delay within the 
A-155. There are rise times in the 4051 and in the address dividers, 
which do the sequencing in the A-155. These are in the range of 
nanoseconds. But this is enugh to be "to late".

So yes: I think it is normal that the CV will set the multiplication 
factor for the NEXT step.

Florian
Show quoted textHide quoted text
On 18.10.16 09:47 , Jacco Ville jaccoville@yahoo.com [Doepfer_a100] wrote:
> Hello Dieter,
>
> I made the patch exactly by the book.
> To be sure I made it once again.
>
> What I notice is that once the CV from the A155 sends a voltage the A160-5 does shows this by increasing the leds BUT the actual ratcheting of the notes to my A140 adsr follows AFTER the CV has passed, so the next note makes the ratcheting sequence.
> For me it seems not logical.
> There is always a steady masterclock to the "clock in" of the A160-5.
>
> Best regards
>
> Jacco Ville
>
>
>
>
> Op 18 okt. 2016 om 09:09 heeft yahoo@doepfer.de [Doepfer_a100]<Doepfer_a100@yahoogroups.com>  het volgende geschreven:
>
>>> Hello Doepfer users,
>>>
>>> When setting up a patch with my A160-5 clockdivider I noticed
>>> that when I send a CV to the multiplier input for creating
>>> ratcheting there is a latency of one sequencer step.
>>> To be clear: I made the patch classic.
>>>
>>> See example in the manual.
>>> So one A155.
>>>
>>> The point is that I have to set the CV step on sequencer step,
>>> let's say, 7 to get the ratcheting effect on step 8 in the sequence.
>>>
>>> Is this normal?
>>>
>>> Best regards
>>>
>>> Jacco Ville
>> I just used the A-160-5 for a performance in Munic (DigitalAnalog Festival)
>> and cannot confirm this behaviour. You should use the pre output of the
>> A-155 to avoid any delay. If this does not help please contact Christian
>> Assall (software@doepfer.de). He programmed the A-160-5 firmware together
>> with the A-155.
>>
>> Best wishes
>> Dieter Doepfer
>>
>>
>>
>>
>> ------------------------------------
>>
>> ------------------------------------
>>
>>
>> ------------------------------------
>>
>> Yahoo Groups Links
>>
>>
>>
>
>
> ------------------------------------
> Posted by: Jacco Ville<jaccoville@yahoo.com>
> ------------------------------------
>
>
> ------------------------------------
>
> Yahoo Groups Links
>
>
>

Re: AW: [Doepfer_a100] A160-5 latency

2016-10-18 by Jacco Ville

Hello Florian, 

Thank you for your clear explaination. 
I like the A160-5 to use but I have to have to attention to place the CV one step ahead which isn't a big deal. 
Now I know why 

Thanks again 

Jacco
Show quoted textHide quoted text
> Op 18 okt. 2016 om 10:57 heeft Florian Anwander fanwander@mnet-online.de [Doepfer_a100] <Doepfer_a100@yahoogroups.com> het volgende geschreven:
> 
> Hello Jacco,
> 
> just think twice:
> 
> The voltage which sets the division/multiplication factor, comes 
> slightly after the clock-tick, that should be multiplied. So the 
> multiplying/dividing will happen for the next clock tick. Why comes the 
> Voltage after the clocktick? Because there is a minimal delay within the 
> A-155. There are rise times in the 4051 and in the address dividers, 
> which do the sequencing in the A-155. These are in the range of 
> nanoseconds. But this is enugh to be "to late".
> 
> So yes: I think it is normal that the CV will set the multiplication 
> factor for the NEXT step.
> 
> Florian
> 
> On 18.10.16 09:47 , Jacco Ville jaccoville@yahoo.com [Doepfer_a100] wrote:
> > Hello Dieter,
> >
> > I made the patch exactly by the book.
> > To be sure I made it once again.
> >
> > What I notice is that once the CV from the A155 sends a voltage the A160-5 does shows this by increasing the leds BUT the actual ratcheting of the notes to my A140 adsr follows AFTER the CV has passed, so the next note makes the ratcheting sequence.
> > For me it seems not logical.
> > There is always a steady masterclock to the "clock in" of the A160-5.
> >
> > Best regards
> >
> > Jacco Ville
> >
> >
> >
> >
> > Op 18 okt. 2016 om 09:09 heeft yahoo@doepfer.de [Doepfer_a100]<Doepfer_a100@yahoogroups.com> het volgende geschreven:
> >
> >>> Hello Doepfer users,
> >>>
> >>> When setting up a patch with my A160-5 clockdivider I noticed
> >>> that when I send a CV to the multiplier input for creating
> >>> ratcheting there is a latency of one sequencer step.
> >>> To be clear: I made the patch classic.
> >>>
> >>> See example in the manual.
> >>> So one A155.
> >>>
> >>> The point is that I have to set the CV step on sequencer step,
> >>> let's say, 7 to get the ratcheting effect on step 8 in the sequence.
> >>>
> >>> Is this normal?
> >>>
> >>> Best regards
> >>>
> >>> Jacco Ville
> >> I just used the A-160-5 for a performance in Munic (DigitalAnalog Festival)
> >> and cannot confirm this behaviour. You should use the pre output of the
> >> A-155 to avoid any delay. If this does not help please contact Christian
> >> Assall (software@doepfer.de). He programmed the A-160-5 firmware together
> >> with the A-155.
> >>
> >> Best wishes
> >> Dieter Doepfer
> >>
> >>
> >>
> >>
> >> ------------------------------------
> >>
> >> ------------------------------------
> >>
> >>
> >> ------------------------------------
> >>
> >> Yahoo Groups Links
> >>
> >>
> >>
> >
> >
> > ------------------------------------
> > Posted by: Jacco Ville<jaccoville@yahoo.com>
> > ------------------------------------
> >
> >
> > ------------------------------------
> >
> > Yahoo Groups Links
> >
> >
> >
> 
>

Re: [Doepfer_a100] A160-5 latency

2016-10-18 by achtung_999

Ah yes! Of course, sorry Jacco I did not read your message correctly.
Ernst
Show quoted textHide quoted text
On Mon, Oct 17, 2016 at 11:26 PM, Jacco Ville jaccoville@yahoo.com [Doepfer_a100] <Doepfer_a100@yahoogroups.com> wrote:

Well for me this note in the manual is about the clock input which has to be stable and infact it is in this setup.

Only the CV input is getting a voltage which fluctuates to get the ratcheting effect.

Jacco

Op 17 okt. 2016 om 23:06 heeft achtung_999 heinrich.himmelwasser@gmail.com [Doepfer_a100] <Doepfer_a100@yahoogroups.com> het volgende geschreven:

This is stated in the manual. And if you think about it, it makes sense doesn't it?
There are no electronics yet, that have psychic powers ;-)

Ernst


On Mon, Oct 17, 2016 at 9:02 PM, jaccoville@yahoo.com [Doepfer_a100] <Doepfer_a100@yahoogroups.com> wrote:

Hello Doepfer users,


When setting up a patch with my A160-5 clockdivider I noticed that when I send a CV to the multiplier input for creating ratcheting there is a latency of one sequencer step.
To be clear: I made the patch classic.

See example in the manual.
So one A155.

The point is that I have to set the CV step on sequencer step, let's say, 7 to get the ratcheting effect on step 8 in the sequence.

Is this normal?

Best regards

Jacco Ville



Re: AW: [Doepfer_a100] A160-5 latency

2016-10-18 by jaccoville@yahoo.com

And in the end it is a faulty microprocessor. 
I contacted Doepfer about this and they confirmed. 
Change of processor and go!

Cheers

Jacco

Re: AW: [Doepfer_a100] A160-5 latency

2016-10-22 by jaccoville@yahoo.com

Hi there all,

After having mail contact with Chris from Doepfer who offerd excellent service to take care of a new processor I couldn't resist also order a new A160-5 at Thomann.
Once installed in my system it worked like a charm, no latency issues or whatsoever.
Thank you again Chris for your help with this and with sending me the long
awaited update software for my A157's.

Cheers

Jacco Ville
The Netherlands

Re: AW: [Doepfer_a100] A160-5 latency

2016-10-22 by Jonathan

Doesvthat mean there are lots of faulty microprocessors? I just assumed the one step latency was expected as stabilisation time for the mutiplication routine. Is mine faulty too?

Jonathan Shapero
From my iPad Air
Show quoted textHide quoted text
> On 22 Oct 2016, at 08:51, jaccoville@yahoo.com [Doepfer_a100] <Doepfer_a100@yahoogroups.com> wrote:
> 
> 
> 
> Hi there all,
> 
> After having mail contact with Chris from Doepfer who offerd excellent service to take care of a new processor I couldn't resist also order a new A160-5 at Thomann.
> Once installed in my system it worked like a charm, no latency issues or whatsoever. 
> Thank you again Chris for your help with this and with sending me the long  
> awaited update software for my A157's. 
> 
> Cheers
> 
> Jacco Ville
> The Netherlands
> 
> 
>

Re: AW: [Doepfer_a100] A160-5 latency

2016-10-22 by Jacco Ville

Hello Jonathan,

There should be no latency....
So I recommand to contact Chris about this. 
No worries, very correct and friendly service. 
Just swapping the processor and your good to go. 

Best regards

Jacco Ville
Show quoted textHide quoted text
> Op 22 okt. 2016 om 16:54 heeft Jonathan jss9h@aol.com [Doepfer_a100] <Doepfer_a100@yahoogroups.com> het volgende geschreven:
> 
> Doesvthat mean there are lots of faulty microprocessors? I just assumed the one step latency was expected as stabilisation time for the mutiplication routine. Is mine faulty too?
> 
> Jonathan Shapero
> From my iPad Air
> 
>> On 22 Oct 2016, at 08:51, jaccoville@yahoo.com [Doepfer_a100] <Doepfer_a100@yahoogroups.com> wrote:
>> 
>> Hi there all,
>> 
>> After having mail contact with Chris from Doepfer who offerd excellent service to take care of a new processor I couldn't resist also order a new A160-5 at Thomann.
>> Once installed in my system it worked like a charm, no latency issues or whatsoever. 
>> Thank you again Chris for your help with this and with sending me the long  
>> awaited update software for my A157's. 
>> 
>> Cheers
>> 
>> Jacco Ville
>> The Netherlands
> 
>

Re: AW: [Doepfer_a100] A160-5 latency

2016-10-22 by achtung_999

Jonathan, you are like me before in this thread, mistaking the bit about the steady clock with the problem that Jacco was experiencing.

Ernst
Show quoted textHide quoted text
On Sat, Oct 22, 2016 at 4:54 PM, Jonathan jss9h@aol.com [Doepfer_a100] <Doepfer_a100@yahoogroups.com> wrote:

Doesvthat mean there are lots of faulty microprocessors? I just assumed the one step latency was expected as stabilisation time for the mutiplication routine. Is mine faulty too?

Jonathan Shapero
From my iPad Air

On 22 Oct 2016, at 08:51, jaccoville@yahoo.com [Doepfer_a100] <Doepfer_a100@yahoogroups.com> wrote:

Hi there all,

After having mail contact with Chris from Doepfer who offerd excellent service to take care of a new processor I couldn't resist also order a new A160-5 at Thomann.
Once installed in my system it worked like a charm, no latency issues or whatsoever.
Thank you again Chris for your help with this and with sending me the long
awaited update software for my A157's.

Cheers

Jacco Ville
The Netherlands


Re: AW: [Doepfer_a100] A160-5 latency

2016-10-23 by Jacco Ville

Hi Jonathan,

If that is the matter what Ernst said.
Your (masterclock) has to be steady, at a sudden tempo change the A160-5 will need a few pulses to adapt.
However, this shouldn't be the point with the multiplier/ratcheting function. When sending different CV to the CV input it has to spit out the multiplied pulses direct and with no delay, so spot on. 
The last thing didn't happen with my A160-5 so that was where the faulty processor showed up. 
Make the basic patch like described in the manual and you'll notice right away. 

Best regards

Jacco Ville
Show quoted textHide quoted text
> Op 23 okt. 2016 om 01:40 heeft achtung_999 heinrich.himmelwasser@gmail.com [Doepfer_a100] <Doepfer_a100@yahoogroups.com> het volgende geschreven:
> 
> Jonathan, you are like me before in this thread, mistaking the bit about the steady clock with the problem that Jacco was experiencing. 
> 
> Ernst
> 
>> On Sat, Oct 22, 2016 at 4:54 PM, Jonathan jss9h@aol.com [Doepfer_a100] <Doepfer_a100@yahoogroups.com> wrote:
>>  
>> Doesvthat mean there are lots of faulty microprocessors? I just assumed the one step latency was expected as stabilisation time for the mutiplication routine. Is mine faulty too?
>> 
>> Jonathan Shapero
>> From my iPad Air
>> 
>>> On 22 Oct 2016, at 08:51, jaccoville@yahoo.com [Doepfer_a100] <Doepfer_a100@yahoogroups.com> wrote:
>>> 
>>> Hi there all,
>>> 
>>> After having mail contact with Chris from Doepfer who offerd excellent service to take care of a new processor I couldn't resist also order a new A160-5 at Thomann.
>>> Once installed in my system it worked like a charm, no latency issues or whatsoever. 
>>> Thank you again Chris for your help with this and with sending me the long  
>>> awaited update software for my A157's. 
>>> 
>>> Cheers
>>> 
>>> Jacco Ville
>>> The Netherlands
>> 
> 
>

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.