The A155 as mentioned always resets to step 1 and starts at step 2.

Not sure what's causing the lag, but if you're using a software
sequencer its possible that a lot of active sensing messages or other
spurious midi messages are clogging the A190 processor a bit.

Joe

--- In Doepfer_a100@yahoogroups.com , "code_pig" <code_pig@y...> wrote:
> Actually, I have no problem with the A190-A155 combination. I mean,
> there is a slight lag (which I assume is down to the MIDI digital to
> analog CV conversion), but the sequencer parks at step one, and
> starts at step two.
>
> The lag doesn't bother me much, and seeing as how I multitrack
> things, I can offset the lag.
>
> What is supplying the MIDI clock, and how is the clock being routed

> I'm certain you know this, but try never to supply timing critical
> MIDI data via a THRU port.
>
>
> --- In Doepfer_a100@yahoogroups.com , "Tim Stinchcombe"
<timothy@t...>
> wrote:
> > Hi shm,
> >
> > > I have been unable to get any kind of meaningful midi sync: yes
> the
> > > tempo is right, but the sequencer won't start on 1. The notes
are
> >
> > I notice from the 'Database' section that this same problem is
> > mentioned there, so I'm wondering whether it's one of those things
> > one has to live with. I've just got hold of a 155 myself, and will
> be
> > looking at it over the next few days. I don't know whether I shall
> be
> > able to help out on the MIDI front (unless I can work out how to
> get
> > my PC to output some sort of MIDI clock, but I'm no musician), but
> if
> > I come up with anything I'll let you know.
> >
> > > more likely to occur on, say, 1 and 73/960, etc. So, I have
been
> > > recording midi notes at the desired rate to trigger the A-155
off
> > of
> > > the gate output of the A-190.
> > >
> > > I would very much appreciate some tips on midi sync. Thanks.
> >
> > Again, I'm wondering if lack of response from other group members
> who
> > would have more idea than me, reinforces the above ( )
> >
> > Tim