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.

Loopy Pro AUV3 won’t change time signature (hosted in Drambo)

edited June 2024 in App Tips and Tricks

I’m trying to set Loopy pro hosted in Drambo to the same signature as the host.

If I set the synchronisation to host I cannot change the signature in Loopy at all.
If I set it host sync to off and set it to listen to any other time signal (and set Drambo to send clock to all available destinations Loopy won’t start.

Drambo doesn’t have signatures in its transport settings which I expect is what Loopy is listening for. Drambo also doesn’t show loopy pro AUV3 as the destination so I’m relying on sending clock to my midi interface and set loopy to the same interface but still no luck.

I guess not many people host Loopy in other apps but I’ve had too many loading issues with Drambo and this not works very well other than the above.

Any ideas?

Comments

  • Hi. Have you tried enabling Link in both Drambo and Loopy Pro AUv3? Loopy then runs/stops with Drambo, follows tempo, and allows changing the time signature (which doesn't seem to appear in Drambo). So, you cannot make the time signature follow Drambo, since Drambo has none, but you can freely set it in Loopy Pro.

  • edited June 2024

    @supadom said:
    I’m trying to set Loopy pro hosted in Drambo to the same signature as the host.

    If I set the synchronisation to host I cannot change the signature in Loopy at all.
    If I set it host sync to off and set it to listen to any other time signal (and set Drambo to send clock to all available destinations Loopy won’t start.

    Drambo doesn’t have signatures in its transport settings which I expect is what Loopy is listening for. Drambo also doesn’t show loopy pro AUV3 as the destination so I’m relying on sending clock to my midi interface and set loopy to the same interface but still no luck.

    I guess not many people host Loopy in other apps but I’ve had too many loading issues with Drambo and this not works very well other than the above.

    Any ideas?

    I checked in AUM and Loopy AUv3 follows changes in AUM’s time signature. Host sync includes tempo and time signature info. MIDI Clock doesn’t have either tempo or time signature info.You might want to lobby the Drambo dev to support time signatures other than 4/4 as a host.

    Since MIDI clock doesn’t have time signature information, you need to set up midi bindings (or widgets that you bind to) to change time signature. The action is Beats Per Bar.

    You could use ableton link rather than midi clock. You’ll still need bindings to change the time signature but the sync won’t require sending the midi out to your interface and will be more reliable/accurate.

    —-
    If you wonder why Loopy doesn’t list the AU Midi in as a clock source, the reason is likely
    that host sync is more accurate than midi clock and also has tempo and time information. So, it would be rare to use midi clock from the host rather than host sync

    You might want to add a request to the loopy pro roadmap for AU Midi In to be added as a clock source.

    Where you see Drambo as a source that refers to the Drambo app’s virtual midi in port (I.e. the port other apps use to send midi to Drambo ) which is why you need to loop it back. You could loop the clock back to Drambo with software rather than loop it out to your interface.

  • @uncledave said:
    Hi. Have you tried enabling Link in both Drambo and Loopy Pro AUv3? Loopy then runs/stops with Drambo, follows tempo, and allows changing the time signature (which doesn't seem to appear in Drambo). So, you cannot make the time signature follow Drambo, since Drambo has none, but you can freely set it in Loopy Pro.

    My issue with Link is that I it always runs in the background so I cannot start it instantly when jamming with non electronic instruments. So if things are going out of sync with another musician I can always stop and restart the session on the 1. I remember at some point when I was still using Audiobus I was able to do that but the details are long gone from my brain.

  • @espiegel123 said:

    @supadom said:
    I’m trying to set Loopy pro hosted in Drambo to the same signature as the host.

    If I set the synchronisation to host I cannot change the signature in Loopy at all.
    If I set it host sync to off and set it to listen to any other time signal (and set Drambo to send clock to all available destinations Loopy won’t start.

    Drambo doesn’t have signatures in its transport settings which I expect is what Loopy is listening for. Drambo also doesn’t show loopy pro AUV3 as the destination so I’m relying on sending clock to my midi interface and set loopy to the same interface but still no luck.

    I guess not many people host Loopy in other apps but I’ve had too many loading issues with Drambo and this not works very well other than the above.

    Any ideas?

    I checked in AUM and Loopy AUv3 follows changes in AUM’s time signature. Host sync includes tempo and time signature info. MIDI Clock doesn’t have either tempo or time signature info.You might want to lobby the Drambo dev to support time signatures other than 4/4 as a host.

    Since MIDI clock doesn’t have time signature information, you need to set up midi bindings (or widgets that you bind to) to change time signature. The action is Beats Per Bar.

    You could use ableton link rather than midi clock. You’ll still need bindings to change the time signature but the sync won’t require sending the midi out to your interface and will be more reliable/accurate.

    —-
    If you wonder why Loopy doesn’t list the AU Midi in as a clock source, the reason is likely
    that host sync is more accurate than midi clock and also has tempo and time information. So, it would be rare to use midi clock from the host rather than host sync

    You might want to add a request to the loopy pro roadmap for AU Midi In to be added as a clock source.

    Where you see Drambo as a source that refers to the Drambo app’s virtual midi in port (I.e. the port other apps use to send midi to Drambo ) which is why you need to loop it back. You could loop the clock back to Drambo with software rather than loop it out to your interface.

    I spoke to Drambo dev and he’s looking into it.

    In the meantime I will check the ‘beats per bar’ action out . Thanks

  • I was able to get loopy to follow Drambo’s midi clock natively.

    In loopy pro, clock source Drambo

    In Drambo’s settings, I turned on clock for Drambo out

  • Thanks @espiegel123 you’re right. Looks like I haven’t tried hard enough.

    I’m getting a weird behaviour with some silent gap at the end of one of the loops but other than that all is working ok.

    Cheers.

  • I’m getting a weird behaviour with some silent gap at the end of one of the loops but other than that all is working ok.

    I think I’ve sorted it now.

Sign In or Register to comment.