Loopy Pro: Create music, your way.

What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.

Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.

Download on the App Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Cubasis MIDI clock locking DigiTakt

papertigerpapertiger
in General App Discussion

I just just ran into the following issue: using a USB connection, enabling MIDI Clock out in Cubasis 2.8.2 and setting the DigiTakt to receive clock (OS 1.11) locks up the DigiTakt every single time.

Anyone have any ideas why that would happen?

I have no clue if it worked before today’s update or not. First time I’ve tried it.

Thanks!

Comments

  • rs2000rs2000
    edited December 2019

    Works here except for the infamous MIDI clock bug in looped mode that Steinberg are apparently now asking $50 to (hopefully?) fix (it has been reported by numerous users in May 2018!).

    I'm still on DT version 1.06 though.
    I rarely had the DT lock up, when it happened, a power-off, then waiting at least 10 seconds and power on again usually helped.

    You might want to check your i/o and Thru settings on the DT in
    Settings > Midi Config > Port Config.

    You don't use the hardware MIDI ports at the same time, do you?

  • mistercharliemistercharlie
    edited December 2019

    @rs2000 said:
    the infamous MIDI clock bug in looped mode that Steinberg are apparently now asking $50 to (hopefully?) fix

    If we club together, I'm sure we can raise $50.

  • rs2000rs2000

    @mistercharlie said:

    @rs2000 said:
    the infamous MIDI clock bug in looped mode that Steinberg are apparently now asking $50 to (hopefully?) fix

    If we club together, I'm sure we can raise $50.

    ...and buy them a huuuge pizza and good beer :D

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • rs2000rs2000
    edited December 2019

    @d4d0ug said:
    Not sure if it’s just me but the clock coming from c3 to my BeatStep pro is all over the place, any one else seen this?

    The last Cubasis version that worked properly with MIDI clock was version 2.1 or 2.2 as far as I remember.
    I gave the dev team lots of information (also via the dedicated cubasisle forum) and offered to help them debug the issues that came with later versions and after 18 months I see no sign of interest in fixing it.

    However your problem is not necessarily related to that one.
    Can you monitor the MIDI messages (preferably using a desktop machine and a solid (USB) MIDI interface and check the timing between MIDI clock messages sent from C3?

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • LFSLFS

    Hi,

    Please note that there is a known issue related to MIDI clock in Cubasis 3:

    CBT-1273
    Cubasis 3 is not sending MIDI Clock start/stop from the transport buttons.
    No solution yet. Issue planned to be addressed in a future maintenance update.

    Best,
    Lars

  • [Deleted User][Deleted User]

    @LFS said:
    Hi,

    Please note that there is a known issue related to MIDI clock in Cubasis 3:

    CBT-1273
    Cubasis 3 is not sending MIDI Clock start/stop from the transport buttons.
    No solution yet. Issue planned to be addressed in a future maintenance update.

    Best,
    Lars

    Hopefully this fix is quick like in the next days or week. How can you even release with these type of bugs 🐛 ?

  • papertigerpapertiger

    I asked a very simple question about Cubasis 2.8.2.

    I’d like to request that people either respond to my original question or not at all. I’d rather this thread not deteriorate into another complaint thread about Cubasis 2 or 3.

  • rs2000rs2000

    @d4d0ug said:
    Yeah, I’m trying to find a good way to monitor. What I can definitely see is that the BSP syncs nicely with AUM, but with C3 the bpm is nearly always ‘out’ and jumps around.

    @LFS said:
    Hi,

    Please note that there is a known issue related to MIDI clock in Cubasis 3:

    CBT-1273
    Cubasis 3 is not sending MIDI Clock start/stop from the transport buttons.
    No solution yet. Issue planned to be addressed in a future maintenance update.

    Best,
    Lars

    If it was only about MIDI Status messages 0xFA and 0xFC, the bpm value on the BeatStep would not jump around.

    There must be more to it. Sounds like MIDI clock is even worse in Cubasis 3?

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • AndyPlanktonAndyPlankton

    @rs2000 said:

    @d4d0ug said:
    Yeah, I’m trying to find a good way to monitor. What I can definitely see is that the BSP syncs nicely with AUM, but with C3 the bpm is nearly always ‘out’ and jumps around.

    @LFS said:
    Hi,

    Please note that there is a known issue related to MIDI clock in Cubasis 3:

    CBT-1273
    Cubasis 3 is not sending MIDI Clock start/stop from the transport buttons.
    No solution yet. Issue planned to be addressed in a future maintenance update.

    Best,
    Lars

    If it was only about MIDI Status messages 0xFA and 0xFC, the bpm value on the BeatStep would not jump around.

    There must be more to it. Sounds like MIDI clock is even worse in Cubasis 3?

    I am using midi clock from Cubasis 3 with Novation Circuit and MonoStation with no timing issues.

  • rs2000rs2000

    @papertiger said:
    I asked a very simple question about Cubasis 2.8.2.

    I’d like to request that people either respond to my original question or not at all. I’d rather this thread not deteriorate into another complaint thread about Cubasis 2 or 3.

    Well then please report back about your Digitakt Sync and Port settings.
    Have you tried different settings?

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • AndyPlanktonAndyPlankton

    @d4d0ug said:

    @AndyPlankton said:

    @rs2000 said:

    @d4d0ug said:
    Yeah, I’m trying to find a good way to monitor. What I can definitely see is that the BSP syncs nicely with AUM, but with C3 the bpm is nearly always ‘out’ and jumps around.

    @LFS said:
    Hi,

    Please note that there is a known issue related to MIDI clock in Cubasis 3:

    CBT-1273
    Cubasis 3 is not sending MIDI Clock start/stop from the transport buttons.
    No solution yet. Issue planned to be addressed in a future maintenance update.

    Best,
    Lars

    If it was only about MIDI Status messages 0xFA and 0xFC, the bpm value on the BeatStep would not jump around.

    There must be more to it. Sounds like MIDI clock is even worse in Cubasis 3?

    I am using midi clock from Cubasis 3 with Novation Circuit and MonoStation with no timing issues.

    Hmm that’s interesting, thanks for the nod - I was looking for anyone to confirm if it was working for them (external midi sync on h/w)! Still an issue with the BSP but am going to do a. It more digging. The big difference seems to be when comparing with AUM which I think does do the start / stop behaviour.

    The start/stop in Cubasis 3 is going to be fixed with an update so all will be good there at some point :)

  • mlaumlau

    @LFS said:
    Hi,

    Please note that there is a known issue related to MIDI clock in Cubasis 3:

    CBT-1273
    Cubasis 3 is not sending MIDI Clock start/stop from the transport buttons.
    No solution yet. Issue planned to be addressed in a future maintenance update.

    Best,
    Lars

    @LFS hi Lars ! Did you solve this issue ?

Sign In or Register to comment.

© Vanilla Keystone Theme 2025