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 1.3.9 update

1235

Comments

  • @j_liljedahl said:
    I'm planning a rewrite from the ground up regarding MIDI sync, adding clock slaving as well as bringing the MIDI clock in/out into the main MIDI matrix so it can be connected anywhere and to multiple endpoints.

    Truly awesome!

  • @auxmux said:

    @arktek said:

    @j_liljedahl said:

    @0tolerance4silence said:
    @j_liljedahl
    small bug in AUM/Dub - if tempo sync is enabled in Dub, AUMs new parameter picker would automatically pick “Coarse Time” parameter.

    Ah, good catch. I can fix Dub to not emit a "parameter did change" for coarse time in sync mode unless the tempo actually changed, but it highlights a problem that might show up in other plugins as well: there's no way to differentiate between user wiggling a knob and the parameter being set by the plugin itself. I have some ideas to improve this though for the next update.

    Out of curiosity - is there a reason why the midi sync out port selection is not remembered on project reload, and ‘port allocation’ seems messier? It could be my interface (iCM4+), which have a mix of DIN ports and ?dynamically allocated USB midi?
    F.e - AUM would list all my ports in the same order (alphabetically) every time in the matrix, but not in sync out section.

    I'm planning a rewrite from the ground up regarding MIDI sync, adding clock slaving as well as bringing the MIDI clock in/out into the main MIDI matrix so it can be connected anywhere and to multiple endpoints.

    Oh my, still lots to look forward to.....thank you for all of your work...

    @j_liljedahl If you're looking into clock changes, one awesome update would be clock dividers built into AUM. This way different AU sequencers could be run at different speeds.

    That's a cool idea! Perhaps a bit confusing since AU host time is not really a clock pulse in the traditional sense, but a continuous timeline, so it would mean an AU running at half clock speed would think it's at 1:00 when the host is at 2:00, etc. I do think that any good sequencer (AUv3 or hardware) should have settings for clock division or note value, but I will consider the idea :)

  • Has the ability to layer presets (add rather than load a preset) ever come up as a possible future feature? Without knowing the internals of AUM, I'm not sure if it's a crazy idea. There's a 3 Mozaic group that I often use to turn MIDI off/on in a chain, and sometimes I don't decide to use it until after I've got the audio mix going. It would be SO great to be able to just add a lane that already contains these three with their proper routing, without clearing the existing mix.

    Don't throw stones... lol. Everybody has ideas...

  • @j_liljedahl said:

    @auxmux said:

    @arktek said:

    @j_liljedahl said:

    @0tolerance4silence said:
    @j_liljedahl
    small bug in AUM/Dub - if tempo sync is enabled in Dub, AUMs new parameter picker would automatically pick “Coarse Time” parameter.

    Ah, good catch. I can fix Dub to not emit a "parameter did change" for coarse time in sync mode unless the tempo actually changed, but it highlights a problem that might show up in other plugins as well: there's no way to differentiate between user wiggling a knob and the parameter being set by the plugin itself. I have some ideas to improve this though for the next update.

    Out of curiosity - is there a reason why the midi sync out port selection is not remembered on project reload, and ‘port allocation’ seems messier? It could be my interface (iCM4+), which have a mix of DIN ports and ?dynamically allocated USB midi?
    F.e - AUM would list all my ports in the same order (alphabetically) every time in the matrix, but not in sync out section.

    I'm planning a rewrite from the ground up regarding MIDI sync, adding clock slaving as well as bringing the MIDI clock in/out into the main MIDI matrix so it can be connected anywhere and to multiple endpoints.

    Oh my, still lots to look forward to.....thank you for all of your work...

    @j_liljedahl If you're looking into clock changes, one awesome update would be clock dividers built into AUM. This way different AU sequencers could be run at different speeds.

    That's a cool idea! Perhaps a bit confusing since AU host time is not really a clock pulse in the traditional sense, but a continuous timeline, so it would mean an AU running at half clock speed would think it's at 1:00 when the host is at 2:00, etc. I do think that any good sequencer (AUv3 or hardware) should have settings for clock division or note value, but I will consider the idea :)

    Thanks @j_liljedahl! 🙂 Ah, interesting, that makes sense, but thanks for considering!

    I was playing with Rozeta Rhythm which made me think of this for AUs, since it doesn't have a clock divider. Other sequencers have clock dividers like Autony, but wanted to see, if there could be more flexibility in timing, like in modular. This way there's a master tempo, but the clock dividers/multipliers would send different tempos to any AU sequencers.

    For example, I've built Gate Sequencers using miRack/VCV for drums, and used clock dividers to play the sequences at different speeds. In VCVRack, you can host VSTs like Maschine and use a clock module to run it at a different tempo than the master clock.

  • i wish the aum keyboard could be set to scales! using an external or other auv3 keyboard isn’t as seem less , unless you could pick a default keyboard app and the keyboard icon would automatically reroute to that app instead of the built in

  • @j_liljedahl said:

    @0tolerance4silence said:
    @j_liljedahl
    small bug in AUM/Dub - if tempo sync is enabled in Dub, AUMs new parameter picker would automatically pick “Coarse Time” parameter.

    Ah, good catch. I can fix Dub to not emit a "parameter did change" for coarse time in sync mode unless the tempo actually changed, but it highlights a problem that might show up in other plugins as well: there's no way to differentiate between user wiggling a knob and the parameter being set by the plugin itself. I have some ideas to improve this though for the next update.

    Out of curiosity - is there a reason why the midi sync out port selection is not remembered on project reload, and ‘port allocation’ seems messier? It could be my interface (iCM4+), which have a mix of DIN ports and ?dynamically allocated USB midi?
    F.e - AUM would list all my ports in the same order (alphabetically) every time in the matrix, but not in sync out section.

    I'm planning a rewrite from the ground up regarding MIDI sync, adding clock slaving as well as bringing the MIDI clock in/out into the main MIDI matrix so it can be connected anywhere and to multiple endpoints.

    Bring it on!
    It’s just getting better.
    🙏🏻
    Happy holidays

  • @reasOne said:
    i wish the aum keyboard could be set to scales! using an external or other auv3 keyboard isn’t as seem less , unless you could pick a default keyboard app and the keyboard icon would automatically reroute to that app instead of the built in

    Did u try kb-1?
    highly recommend !

  • @aleyas said:> >

    @j_liljedahl If you're looking into clock changes, one awesome update would be clock dividers built into AUM. This way different AU sequencers could be run at different speeds.

    Oh my, I LOVE this idea.

    Oh my goodness, clock dividers and multipliers would kick iOS music-making up two notches in one move. Would also be great if we could modulate clock speed and division rates with a sequencer or lfo.

  • @Wrlds2ndBstGeoshredr said:

    @aleyas said:> >

    @j_liljedahl If you're looking into clock changes, one awesome update would be clock dividers built into AUM. This way different AU sequencers could be run at different speeds.

    Oh my, I LOVE this idea.

    Oh my goodness, clock dividers and multipliers would kick iOS music-making up two notches in one move. Would also be great if we could modulate clock speed and division rates with a sequencer or lfo.

    oh, yeah. Especially if the clock divisions included things like 2/1 and 4/1... Imagine what that could do to Ambient stuff.

  • @motmeister said:

    @Wrlds2ndBstGeoshredr said:

    @aleyas said:> >

    @j_liljedahl If you're looking into clock changes, one awesome update would be clock dividers built into AUM. This way different AU sequencers could be run at different speeds.

    Oh my, I LOVE this idea.

    Oh my goodness, clock dividers and multipliers would kick iOS music-making up two notches in one move. Would also be great if we could modulate clock speed and division rates with a sequencer or lfo.

    oh, yeah. Especially if the clock divisions included things like 2/1 and 4/1... Imagine what that could do to Ambient stuff.

    A lot is possible in mirack already, but native with AUM would be 🤯

  • @j_liljedahl said:

    @auxmux said:

    @arktek said:

    @j_liljedahl said:

    @0tolerance4silence said:
    @j_liljedahl
    small bug in AUM/Dub - if tempo sync is enabled in Dub, AUMs new parameter picker would automatically pick “Coarse Time” parameter.

    Ah, good catch. I can fix Dub to not emit a "parameter did change" for coarse time in sync mode unless the tempo actually changed, but it highlights a problem that might show up in other plugins as well: there's no way to differentiate between user wiggling a knob and the parameter being set by the plugin itself. I have some ideas to improve this though for the next update.

    Out of curiosity - is there a reason why the midi sync out port selection is not remembered on project reload, and ‘port allocation’ seems messier? It could be my interface (iCM4+), which have a mix of DIN ports and ?dynamically allocated USB midi?
    F.e - AUM would list all my ports in the same order (alphabetically) every time in the matrix, but not in sync out section.

    I'm planning a rewrite from the ground up regarding MIDI sync, adding clock slaving as well as bringing the MIDI clock in/out into the main MIDI matrix so it can be connected anywhere and to multiple endpoints.

    Oh my, still lots to look forward to.....thank you for all of your work...

    @j_liljedahl If you're looking into clock changes, one awesome update would be clock dividers built into AUM. This way different AU sequencers could be run at different speeds.

    That's a cool idea! Perhaps a bit confusing since AU host time is not really a clock pulse in the traditional sense, but a continuous timeline, so it would mean an AU running at half clock speed would think it's at 1:00 when the host is at 2:00, etc. I do think that any good sequencer (AUv3 or hardware) should have settings for clock division or note value, but I will consider the idea :)

    FYI Photon has clock dividers with the playback of its midi files.

  • @j_liljedahl Thanks for an excellent update!

    I’ve noticed an issue with a couple of plugins, in this and previous releases. Is this the best place to post?

    When an exposed plugin parameter is assigned to the AUM Control knob, sometimes the knob doesn’t appear. Is this an issue with the plugin or with AUM? See below with FF Saturn ... No matter which Saturn parameter is selected, no control knob appears:

  • edited December 2020

    Yeah it doesn’t apply to those AUs because that’s also where the midi sources menu is, so it only works with non-midi enabled AUs where there isn’t a midi sources menu there, hopefully another way to access these macro controls will be added one day though. :)

  • @motmeister said:
    Has the ability to layer presets (add rather than load a preset) ever come up as a possible future feature? Without knowing the internals of AUM, I'm not sure if it's a crazy idea. There's a 3 Mozaic group that I often use to turn MIDI off/on in a chain, and sometimes I don't decide to use it until after I've got the audio mix going. It would be SO great to be able to just add a lane that already contains these three with their proper routing, without clearing the existing mix.

    Don't throw stones... lol. Everybody has ideas...

    For "layering presets", you can choose "Import" instead of "Audio" or "MIDI" and add a channel, or a group of channels with the routings, onto your current project. You can't import Audio and MIDI channels separately and have them automatically route, but you can import them at the same time from the same project, and add that project onto your existing project.

    I've recently started building a bank of AUM preset "instrument presets" for the genres I want to work with. I save each instrument as its own project; some instruments use multiple channels. I can import single channels and sets of channels. Is that what you meant by "layering presets"?

  • Yes! Exactly. It would be even more helpful if their MIDI connections were also imported.

  • I still hope for recorded audio to play automatically without the need to find it and load it in first- a bit like a looper. Is there any chance of this happening @j_liljedahl?

  • @robosardine
    Agreed
    Even if you record a loop, then AUM opens that recorded loop instantly on a new channel
    That would save time, if that’s how you want it to work
    Or an option when arming the record of a channel ‘ open recorded loop in new channel’ something like that
    Or when you have just recorded, when opening a new channel, new loop option as well as audio, midi etc

  • I know @j_liljedahl always stated that he wants it to be a super clean interface, which it is, and not over complicated,
    But I feel if people have purchased this amazing app, they have some knowledge and understanding of what this app can achieve....
    Either way great update
    Thanks again for my ‘go to app’

  • @Carnbot said:
    Yeah it doesn’t apply to those AUs because that’s also where the midi sources menu is, so it only works with non-midi enabled AUs where there isn’t a midi sources menu there, hopefully another way to access these macro controls will be added one day though. :)

    I know, this is quite annoying. Would it be better to skip the midi sources menu? after all, it's already accessible via the title bar if you open the plugin. Also it's much less common that you need to route MIDI to an fx node, even if some of them allow it.

  • @robosardine said:
    I still hope for recorded audio to play automatically without the need to find it and load it in first- a bit like a looper. Is there any chance of this happening @j_liljedahl?

    All that's needed is a good and simple AUv3 looper effect. No need to have this built into AUM.

  • @j_liljedahl said:

    @Carnbot said:
    Yeah it doesn’t apply to those AUs because that’s also where the midi sources menu is, so it only works with non-midi enabled AUs where there isn’t a midi sources menu there, hopefully another way to access these macro controls will be added one day though. :)

    I know, this is quite annoying. Would it be better to skip the midi sources menu? after all, it's already accessible via the title bar if you open the plugin. Also it's much less common that you need to route MIDI to an fx node, even if some of them allow it.

    Yeah it's hard to say, if it's gone it might be missed :) I personally find it useful to see which fx are midi enabled and you don't always want to open the plugin to change the sources. Perhaps the macro control just overrides that menu if enabled?

  • @Carnbot said:

    @j_liljedahl said:

    @Carnbot said:
    Yeah it doesn’t apply to those AUs because that’s also where the midi sources menu is, so it only works with non-midi enabled AUs where there isn’t a midi sources menu there, hopefully another way to access these macro controls will be added one day though. :)

    I know, this is quite annoying. Would it be better to skip the midi sources menu? after all, it's already accessible via the title bar if you open the plugin. Also it's much less common that you need to route MIDI to an fx node, even if some of them allow it.

    Yeah it's hard to say, if it's gone it might be missed :) I personally find it useful to see which fx are midi enabled and you don't always want to open the plugin to change the sources. Perhaps the macro control just overrides that menu if enabled?

    Yes, that's what I was thinking: if no "main param knob" (as I call it) is selected, it shows the MIDI menu (if it has one).

  • @j_liljedahl I love that you are continuing to develop AUM. It is the core of iOS music making for so many of us. Keep keeping on! 👍

  • @j_liljedahl It's like a new app, I had this crazy drum project I called \one source\ where just one 5 note loop in Atom drove several drum machines. Added other midi tools (mfx, the budapps, cycle etc. ) just to alter pitch and what have you on that same base loop and it just grow till it weren't playable anymore. Now I opened it again and not only do it run without problem, I added the freshly released GR-16 and ... it's just amazingly smooth. So happy. Thanks again.

  • edited December 2020

    @j_liljedahl said:

    @Carnbot said:
    Yeah it doesn’t apply to those AUs because that’s also where the midi sources menu is, so it only works with non-midi enabled AUs where there isn’t a midi sources menu there, hopefully another way to access these macro controls will be added one day though. :)

    I know, this is quite annoying. Would it be better to skip the midi sources menu? after all, it's already accessible via the title bar if you open the plugin. Also it's much less common that you need to route MIDI to an fx node, even if some of them allow it.

    Yes that's a great idea if the MIDI Sources menu is available elsewhere, since there is no alternative way to access the Macro knob. That way, we have access to the Macro control as well. I guess also the MIDI Sources menu will tend to be set once then left, whereas the Macro knob is designed to be tweaked in real time during a set.

    I often use the Macro knob for Wet\Dry or Mix, which allows effects to be mixed in without having to open the FX app gui. This is a little frustrating in FF Saturn 2, whose MIX control is very small and fiddly and makes real time adjustments a little tricky in the content of a live performance.

    So +1 for replacing the MIDI Sources menu with the Macro knob, or at least an option to show the Macro knob in that position (as some may prefer the MIDI Sources Menu)?

    Thanks again for all your hard work. This app is the bedrock of all my iOS music making :)

  • @Carnbot said:
    Yeah it doesn’t apply to those AUs because that’s also where the midi sources menu is, so it only works with non-midi enabled AUs where there isn’t a midi sources menu there, hopefully another way to access these macro controls will be added one day though. :)

    Ah I hadn't clocked the MIDI angle - I hadn't looked past the fact that the Macro knob wasn't available :)

  • Dear experts, please tell me AUM has PDC?

  • @j_liljedahl Quick question: did the midi mapping preset saving get implemented with this release? I’m having trouble finding it. Loving all the new features, especially the wiggle-your-knob thing!

  • edited December 2020

    @Turok said:
    Dear experts, please tell me AUM has PDC?

    I don't know if it has plug-in delay compensation specifically, but the very helpful manual is online:

    Latency compensation

    AUM does latency compensation if an effect introduces a delay of the signal. The compensation is propagated through mix busses and sends, so that everything lines up at the end.

    It also compensates for the total round-trip latency when recording hardware inputs. This can be disabled in the Settings.

    Tap the DSP meter / battery indicator to show the current latency values and some other statistics, including the current time and date.

  • @ExAsperis99 said:

    @Turok said:
    Dear experts, please tell me AUM has PDC?

    I don't know if it has plug-in delay compensation specifically, but the very helpful manual is online:

    Latency compensation

    AUM does latency compensation if an effect introduces a delay of the signal. The compensation is propagated through mix busses and sends, so that everything lines up at the end.

    It also compensates for the total round-trip latency when recording hardware inputs. This can be disabled in the Settings.

    Tap the DSP meter / battery indicator to show the current latency values and some other statistics, including the current time and date.

    Big thanks!

Sign In or Register to comment.