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.

AUM record arm without transport start/stop

Without it, you can't record audio on a lane and use Xequence to record the MIDI and have them sync. You also can't stop playing MIDI without stopping recording the audio. A good example of the second is to record trailing effects when the MIDI stops.

Am I spitting into the wind? Other "DAWs" allow record arm/disarm without affecting the transport. It sure would be nice.

I suppose it's been discussed before and I just missed it. I did an ABF search for "AUM record arm" and didn't see anything obvious. Forgive me if this is rehashing old stuff...

Comments

  • I’ve bumped into this constraint many times. I suppose you could do some MIDI trickery with Mozaic or something but I’ve never bothered. I hope it’s on @j_liljedahl list!

  • wimwim
    edited May 2021

    I haven't tried it, but it seems like if you have Link and Link Start/Stop enabled in both apps, Xequence 2 should start when you hit record in AUM. It should also stop when you hit stop in AUM. Just turn off the Xequence 2 count-in to get them to sync properly. Or, if you need the count-in then you'll need to crop off the first bar of the AUM recordings.

    Another way, if you really want to start things from X2 rather than AUM might be to map a midi message to AUM's Toggle Record parameter. Then send that from an X2 pattern at the start of the first bar.

  • @wim said:
    I haven't tried it, but it seems like if you have Link and Link Start/Stop enabled in both apps, Xequence 2 should start when you hit record in AUM. It should also stop when you hit stop in AUM. Just turn off the Xequence 2 count-in to get them to sync properly. Or, if you need the count-in then you'll need to crop off the first bar of the AUM recordings.

    Another way, if you really want to start things from X2 rather than AUM might be to map a midi message to AUM's Toggle Record parameter. Then send that from an X2 pattern at the start of the first bar.

    That’s true, but you can’t record-arm either one without starting the transport in both. Yes, there are workarounds, but it would be so much easier and more convenient with the ability to arm either or both without triggering the transport. Note that in Atom2, you can record-arm separately, so the concept is viable.

  • @lukesleepwalker said:
    I’ve bumped into this constraint many times. I suppose you could do some MIDI trickery with Mozaic or something but I’ve never bothered. I hope it’s on @j_liljedahl list!

    Sending a record-arm message to the selected AUM channel can be done by a msg in an Xeq2 play-only. I’ve also done some control from a Mozaic script. Both are doable, but take setup time.

  • wimwim
    edited May 2021

    @motmeister said:

    @wim said:
    I haven't tried it, but it seems like if you have Link and Link Start/Stop enabled in both apps, Xequence 2 should start when you hit record in AUM. It should also stop when you hit stop in AUM. Just turn off the Xequence 2 count-in to get them to sync properly. Or, if you need the count-in then you'll need to crop off the first bar of the AUM recordings.

    Another way, if you really want to start things from X2 rather than AUM might be to map a midi message to AUM's Toggle Record parameter. Then send that from an X2 pattern at the start of the first bar.

    That’s true, but you can’t record-arm either one without starting the transport in both. Yes, there are workarounds, but it would be so much easier and more convenient with the ability to arm either or both without triggering the transport. Note that in Atom2, you can record-arm separately, so the concept is viable.

    I'll take your word for it that there's some workflow advantage I'm not seeing. All I care about is hitting a button and everything starts recording. 🤷🏼‍♂️

Sign In or Register to comment.