Problem solved applying correctly the v2.8 update.

So the upgrade is ok with midi clock ;)

--- In kiwitechnics@yahoogroups.com , "poiskaill" <poiskaill@...> wrote:
>
> Hi,
>
> Made a new test: I've just disable 'send midi clock' in my sequencer and then it's ok, the 3p works fine.
> Except, 3p is not synchronised, and my other synths and seqs won't receive clock anymore :(
>
> But here is the problem: the midi clock is not supported by the upraded 3p.
>
> Hope you'll find a solution!
>
> Best regards
>
> --- In kiwitechnics@yahoogroups.com , Florian Anwander <fanwander@> wrote:
> >
> > Hello
> >
> > poiskaill wrote:
> > > The notes are not really straight
> > > in a cycle, but the first glitch happens when the seq starts and so,
> > > send the clock. That's the only thing I see as difference when the
> > > clock is sent or not.
> > Can you export your test sequence as MIDI song file (*mid) and put it
> > here in the files section. So one could track down the problem.
> >
> > > - Another one: When the 3p is sequenced I can change the preset but
> > > the sound doesn't change, I have to stop the seq to hear the new
> > > preset.
> > That is intended: The preset changes after the sequence has finished one
> > cycle. The next cycle will be with the new preset. This makes sense in
> > one situation (if you play live with the internal sequencer it is very
> > cool). But in some other situation it may be annoying for sure, e.g.:
> > searching a suitable preset while a production.
> >
> > > Am I alone with these midi troubles 1 2
> > I have to admit: I don't use MIDI at all at the moment. I went
> > completely back to internal sequencers, triggers and CV because MIDI is
> > so unflexible.
> >
> > Florian
> >
>