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.

MIDI Clock synchronization: Start/Stop commands not passed thru from clock source to destination.

I have the following configuration:

  • Hardware Synth 1 is configured in Loopy Pro's Synchronization settings as MIDI clock source with start/stop enabled.
  • Pressing "Start" on this synth immediately start Loopy Pro - that's expected!
  • A second Synth 2 is connected to Loopy Pro but configured as a MIDI clock destination.
  • Starting Loopy Pro starts this synth together with Loopy Pro - that's expected as well!
  • Now the problem: When I press "Start" on Synth 1 this does start Loopy Pro but the start command does not reach the second synth. I would expect to be able to start the whole chain Synth1 -> Loopy Pro -> Synth2 from Synth1.

Comments

  • @catherder said:
    I have the following configuration:

    • Hardware Synth 1 is configured in Loopy Pro's Synchronization settings as MIDI clock source with start/stop enabled.
    • Pressing "Start" on this synth immediately start Loopy Pro - that's expected!
    • A second Synth 2 is connected to Loopy Pro but configured as a MIDI clock destination.
    • Starting Loopy Pro starts this synth together with Loopy Pro - that's expected as well!
    • Now the problem: When I press "Start" on Synth 1 this does start Loopy Pro but the start command does not reach the second synth. I would expect to be able to start the whole chain Synth1 -> Loopy Pro -> Synth2 from Synth1.

    Is synth 2 an external app or hardware synth?

  • Can you set Synth2 to have its clock source be Synth1 instead?

  • @catherder : I just tried a setup like you describe and midi sent clock start and stop.

    Setup was

    MIDIfire as clock source for Loopy Pro

    Loopy Pro as clock source for Streambyter.

    When I started and stopped midifire’s clock, Streambyter received start/stop messages.

  • @espiegel123 said:
    @catherder : I just tried a setup like you describe and midi sent clock start and stop.

    Setup was

    MIDIfire as clock source for Loopy Pro

    Loopy Pro as clock source for Streambyter.

    When I started and stopped midifire’s clock, Streambyter received start/stop messages.

    That's interesting. I can confirm this when I connect MidiSpy via virtual MIDI to Loopy Pro. I will have to do some more tests. Maybe it's something freaky with that synth - an Arturia MicroFreak.
    Thanks for testing.

  • @catherder said:

    @espiegel123 said:
    @catherder : I just tried a setup like you describe and midi sent clock start and stop.

    Setup was

    MIDIfire as clock source for Loopy Pro

    Loopy Pro as clock source for Streambyter.

    When I started and stopped midifire’s clock, Streambyter received start/stop messages.

    That's interesting. I can confirm this when I connect MidiSpy via virtual MIDI to Loopy Pro. I will have to do some more tests. Maybe it's something freaky with that synth - an Arturia MicroFreak.
    Thanks for testing.

    A simple way to see if it is the synth is to send from loopy pro to MIDIFire and pass the receiving click on from MIDIFire your hardware synth. MIDIFire has a midi monitor.

Sign In or Register to comment.