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 w/Samplr or Midi Link Sync?

I'm having a hard time getting anything to follow Cubasis' midi clock output--ideally I'd like to have Midi Link Sync pick it up so I can sync to Link apps, but I'd be happy just getting Samplr to follow along.

I have "send midi clock" checked in Cubasis' settings, have Cubasis checked as Midi Source in Midi Link Sync, transport rolling, hit "enable sync" and I can't get past "waiting for midi clock start" in Midi Link Sync. And when I go back to Cubasis, transport has stopped.

In Samplr I check Cubasis as midi clock input and it won't pick it up.

Any ideas? Has anyone had any luck with Midi Clock in Cubasis?

Comments

  • Try setting your Midi in source to "MIDI link Sync IN" instead of "Cubasis" inside of the MIDI link sync app. It's weird about Cubasis Midi clock out, it sends to generic Virtual Midi so you have to select that type of option to get apps to respond to it. In the case of Midi link sync, its own named port must be receiving from Virtual Midi automatically.

  • Not sure about Cubasis midi in but you could try using Loopy Hd or Patterning to send midi clock to sampr and cubasis. Not sure would work but midi clock from those to apps is solid so it might

  • edited November 2017

    Yep, Loopy is the key:

    Samplr is set to receive clock from Loopy.

  • Thanks y’all, hugely helpful. @CracklePot, that worked-got Midi Link Sync following Cubasis. @audiorangutan so Loopy is synced to link via cubasis/midi link sync then sending midi clock to samplr?! That’s awesome. I have cubasis and loopy synced nice n tight, samplr is following loopy’s clock but is a little off— got all three metronomes going. So close!

  • @hightunnels said:
    Thanks y’all, hugely helpful. @CracklePot, that worked-got Midi Link Sync following Cubasis. @audiorangutan so Loopy is synced to link via cubasis/midi link sync then sending midi clock to samplr?! That’s awesome. I have cubasis and loopy synced nice n tight, samplr is following loopy’s clock but is a little off— got all three metronomes going. So close!

    That’s awesome to hear. :)

  • Great to see users helping users here! Many thanks for the support!

    Best
    Lars

  • @hightunnels said:
    Thanks y’all, hugely helpful. @CracklePot, that worked-got Midi Link Sync following Cubasis. @audiorangutan so Loopy is synced to link via cubasis/midi link sync then sending midi clock to samplr?! That’s awesome. I have cubasis and loopy synced nice n tight, samplr is following loopy’s clock but is a little off— got all three metronomes going. So close!

    I got them syncing pretty tight. I posted a video demonstrating this setup if you are interested.
    https://forum.audiob.us/discussion/22868/video-demo-cubasis-recording-loopy-samplr-patterning-via-iaa-from-aum-all-syncing-via-midi-link#latest

  • @audiorangutan said:

    @hightunnels said:
    Thanks y’all, hugely helpful. @CracklePot, that worked-got Midi Link Sync following Cubasis. @audiorangutan so Loopy is synced to link via cubasis/midi link sync then sending midi clock to samplr?! That’s awesome. I have cubasis and loopy synced nice n tight, samplr is following loopy’s clock but is a little off— got all three metronomes going. So close!

    I got them syncing pretty tight. I posted a video demonstrating this setup if you are interested.
    https://forum.audiob.us/discussion/22868/video-demo-cubasis-recording-loopy-samplr-patterning-via-iaa-from-aum-all-syncing-via-midi-link#latest

    Once more, thanks for the great clip!

    Best
    Lars

  • @audiorangutan thanks for that! Will check it later-still not able to get Samplr quite there...

  • edited November 2017

    It seems that the Cubasis MIDI port does not send out MIDI clock, but rather MIDI clock is sent to all coreMIDI destinations when this option is enabled. (so called promiscuous MIDI output )
    Using MIDIflow you can observe this behaviour by monitoring the output from the Cubasis port. (nothing if just used for MIDI clock)
    If you then create a virtual port in MIDIflow you can then see the MIDI clock signals arriving there rather than from the Cubasis port output.
    By creating a virtual input and output it is then possible to route this clock to other Apps like Samplr.


    This is what it looks like with Cubasis playing...
    Left side of this image shows virtual ports created in MIDIflow. Right side shows Cubasis MIDI port.

    @LFS Could you consider the idea of making the 'enable MIDI clock' option just send the MIDI sync to the Cubasis Virtual output rather than sending it to all CoreMIDI destinations? This would make more sense in my opinion to synchronise things discretely without Apps receiving MIDI clock globally as with the current implementation.

  • @iamspoon Very interesting! Have you tested out sync between Cubasis and Samplr? Any chance you could do a walkthrough of the setup? The link to midi--loopy--samplr route works, but somewhat inconsistently for me. Thanks!

  • @iamspoon
    Nice! That’s next level, buddy. I was wondering what was going on with Cubasis clock. I will get MIDIflow and try it out.

  • @hightunnels Cubasis and Samplr Sync is pretty usable/tight using this method and Start/Stop work as expected too.
    I think this 'Omni' style distribution of MIDI clock is a bit outdated now that the majority of Apps have virtual MIDI ports implemented properly and also causes some confusion since it makes it seem the Cubasis MIDI port doesn't work to synchronize other Apps or MIDI hardware.
    Anyhow, here's the setup...

    1. Add virtual input ("Cubasis Clock in" is one I already created)
    2. Add virtual output ("Cubasis Clock out" is again one I already created earlier)
    3. Open Cubasis and route Samplr to an audio track as Inter-App audio. (or Audiobus if you prefer to launch it there as it is handy to have the Audiobus panel for app switching and play/stop etc..)
    4. In Samplr select the MIDI clock input to be the virtual port output you created in step 2. ("Cubasis Clock out" in this example)

    I hope that helps : )
    If it wasn't clear, you need to keep MIDIflow running in the background to do the MIDI clock routing.

  • @iamspoon Thanks—grabbing midiflow now!

  • Can we do all this with the Midiflow AB3 apps? Didn’t have enough cash to get the Midiflow stand-alone app.

  • I don't have them so I'm afraid I cant answer that one... you could probably do it with MIDIbridge if you already own that or any other App that lets you create a custom virtual port.
    Ideally, this behaviour could be changed by Steinberg though then we wouldn't need these workarounds... :p

  • Samplr is very fickle about jitter in the MIDI clock it receives. It screws up the audio unless the clock is perfect.

    This user had an interesting solution:

    @Proto
    I use Cubasis to record Samplr.I just set the bpm the same and use the free app "FreEWI" to let Samplr listen to start and stop midi commands and its stays in sync for a long time.Also tried midibridge but it goes out of sync very quick.FreEWI saved me a lot of midi frustrations with Samplr.You only need to launch Freewi and let it run in the background.

    So there is no clock being passed, just synchronized starts/stops.

  • edited November 2017

    That is an interesting idea.
    I found Samplr synced really well from Cubase running on a PC connected via a CCK/MIDI interface though despite the slight clock jitter. I didn't notice the audio getting screwed.
    Also, seems pretty stable and sounding fine with Cubasis.
    Maybe it's relative to that you're using it for though in terms of losing fidelity. Most of my Samplr usage is glitchy sounding in standalone to begin with : )

    Just testing on detailed headphones : As far as I can tell the project I'm working on in Samplr sounds identical when slaved to Cubasis Clock or running standalone. Running at 90BPM the tempo display is Samplr is showing jitter of maximum +/- 0.1 BPM but I don't hear any audio artefacts.
    However, using "FreEWI" and matching tempos seems like a good free solution too.

  • edited November 2017

    That's exactly my experience too.
    Samplr will slave-sync to external gear quite well, but to sync from an internal Midi Clock source, you will need some kind of helper app that will re-route the IAA Midi Clock to a Core Midi port.

  • @Processaurus said:
    Samplr is very fickle about jitter in the MIDI clock it receives. It screws up the audio unless the clock is perfect.

    This user had an interesting solution:

    @Proto
    I use Cubasis to record Samplr.I just set the bpm the same and use the free app "FreEWI" to let Samplr listen to start and stop midi commands and its stays in sync for a long time.Also tried midibridge but it goes out of sync very quick.FreEWI saved me a lot of midi frustrations with Samplr.You only need to launch Freewi and let it run in the background.

    So there is no clock being passed, just synchronized starts/stops.

    HOT DAMN! FreEWI does exactly that. I just tested it and now can start Samplr from Cubasis, GarageBand, AUM. But beware that AUMs clock runs slow. Like, If I want to match an app running at 102bpm, I have to set AUMs clock at 102.04bpm.

  • edited May 2018

    @LFS said:
    Great to see users helping users here! Many thanks for the support!

    Best
    Lars

    Any news on Cubasis improving it’s sync?

    Forum posts here deal with why Ableton Link is unlikely.

    ...but could we at least have some external control of the transport? Midi/mmc?

    Best
    Spooky

  • @iamspoon said:
    It seems that the Cubasis MIDI port does not send out MIDI clock, but rather MIDI clock is sent to all coreMIDI destinations when this option is enabled. (so called promiscuous MIDI output )
    Using MIDIflow you can observe this behaviour by monitoring the output from the Cubasis port. (nothing if just used for MIDI clock)
    If you then create a virtual port in MIDIflow you can then see the MIDI clock signals arriving there rather than from the Cubasis port output.
    By creating a virtual input and output it is then possible to route this clock to other Apps like Samplr.


    This is what it looks like with Cubasis playing...
    Left side of this image shows virtual ports created in MIDIflow. Right side shows Cubasis MIDI port.

    @LFS Could you consider the idea of making the 'enable MIDI clock' option just send the MIDI sync to the Cubasis Virtual output rather than sending it to all CoreMIDI destinations? This would make more sense in my opinion to synchronise things discretely without Apps receiving MIDI clock globally as with the current implementation.

    @LFS

    Yes, pleeeeease improve the clock options.

    Really want to use Cubasis to record multitrack midi but the clock is consistently freezing my Digitakt when hitting start. Tried with using a clock from other apps successfully, only Cubasis clock causes the freeze.

  • MidiFire works great syncing Samplr with Cubasis using CoreMidi networking (WiFi). Inside Cubasis you need to adjust the output latency slider (midi settings) around 30/40 ms.

  • @SpookyZoo said:
    @LFS

    Yes, pleeeeease improve the clock options.

    Really want to use Cubasis to record multitrack midi but the clock is consistently freezing my Digitakt when hitting start. Tried with using a clock from other apps successfully, only Cubasis clock causes the freeze.

    Interesting, on iOS 8.4 syncing my Digitakt to Cubasis (version 2.2 that supports iOS 8) works perfectly.
    And yes, I also miss remote-controlling Cubasis transport, such a basic thing ... :/

  • @audiorangutan said:
    Yep, Loopy is the key:

    Samplr is set to receive clock from Loopy.

    Great post .. very informative.. question .. how does this work with Audiobus ?

    I couldn’t get Cubasis to start /stop my AB3 project ? Although I enabled send midi clock in cubasis

    And selected virtual midi in midi link sync

  • @hisdudeness said:

    I couldn’t get Cubasis to start /stop my AB3 project ? Although I enabled send midi clock in cubasis

    And selected virtual midi in midi link sync

    I can’t get Cubasis to start anything either, only run the Link clock in Midi Link Sync. I then have to press play in Audiobus to get everything else going in sync with the Link output. There are a lot of details to get this Samplr - Loopy - Cubasis workflow happening, but it is tons of fun. Samplr still rocks!

Sign In or Register to comment.