MPC One Midiclock Problems

Hello: my first jam session with a friend resulted in some "discoveries".

I was receiving Midiclock. I set the One to external sync. It generally does work. However, I lost sync 5 - 10 times in 2 hours.

I did some things that reduced the frequency. I stopped sending out Midiclock from the MPC.

I noticed that if I accessed the SD card with the browser, I would lose sync. I did not try to access the internal drive.

Conclusions so far: don't send out midi clock while receiving sync; don't try to load new samples, at least from the SD card.

Anybody notice similar issues? Any workarounds?

Hi, with which firmware ?

rrooyyccee wrote:Hello: my first jam session with a friend resulted in some "discoveries".

Conclusions so far: don't send out midi clock while receiving sync; don't try to load new samples, at least from the SD card.

Anybody notice similar issues? Any workarounds?

Re the clock, that's how it's supposed to be, hardware can't be slave and master at the same time.

Not master but i've already use an mpc one with receive clock from roland looper and send at the same time midi clock in a pedal delay without problem

Latest firmware was installed Friday night. Receiving Master clock from a Deluge. Initially sending midi clock to an Arturia Midibrut. Stopped doing this due to frequent dropped clock. Still having dropped clock when accessing the SD card to browse for samples. As long as I didn't browse, clock was maintained. So, not a huge problem, but kind of inconvenient as I don't think you can rejoin midi clock without the Master resetting. Doing so on the beat is not so hard but requires some coordination.

You have the 2.11.2 (latest firmware) and before with 2.10.1 you have the same problem ? with my mpc one the synchro is perfect with firmware 2.10 but i never tested with 2.11.2 because i sold all my hardware for the mpc key, but i know that the 2.11.2 use more ressource, some users with mpc live 1 have slow down, but not with 2.10

Confirmed yesterday that I have 2.11.2. I see in another thread that people are having some problems similar to mine with sequences stopping when accessing the browser. So...that thread combined with my experience point towards system resources not being quite ready or there being an issue with 2.11.2.