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.4.0 update is here!

1…45679

Comments

  • cuscolimacuscolima

    @j_liljedahl when moving a fx AU from one track to another, all the settings are also moved and this is great as you can have the exact same behaviour from the AU.
    If I copy a fx from one track to another track, the settings are unfortunately not copied...Is it a normal behaviour? I think it would be better to have the settings copied too. Thanks for your attention

  • j_liljedahlj_liljedahl

    @cuscolima said:
    @j_liljedahl when moving a fx AU from one track to another, all the settings are also moved and this is great as you can have the exact same behaviour from the AU.
    If I copy a fx from one track to another track, the settings are unfortunately not copied...Is it a normal behaviour? I think it would be better to have the settings copied too. Thanks for your attention

    I can't reproduce this here, the state of the AU is copied as expected. Which specific AU and settings are you seeing this with?

  • cuscolimacuscolima

    @j_liljedahl said:

    @cuscolima said:
    @j_liljedahl when moving a fx AU from one track to another, all the settings are also moved and this is great as you can have the exact same behaviour from the AU.
    If I copy a fx from one track to another track, the settings are unfortunately not copied...Is it a normal behaviour? I think it would be better to have the settings copied too. Thanks for your attention

    I can't reproduce this here, the state of the AU is copied as expected. Which specific AU and settings are you seeing this with?

    I did it with Delayrium. On the pic you can see first the original fx and below the copied one. I have however checked with another app (BLEASS reverb) and it worked ok. So I guess the issue occurs only with some apps. Thanks

  • j_liljedahlj_liljedahl

    @cuscolima said:

    @j_liljedahl said:

    @cuscolima said:
    @j_liljedahl when moving a fx AU from one track to another, all the settings are also moved and this is great as you can have the exact same behaviour from the AU.
    If I copy a fx from one track to another track, the settings are unfortunately not copied...Is it a normal behaviour? I think it would be better to have the settings copied too. Thanks for your attention

    I can't reproduce this here, the state of the AU is copied as expected. Which specific AU and settings are you seeing this with?

    I did it with Delayrium. On the pic you can see first the original fx and below the copied one. I have however checked with another app (BLEASS reverb) and it worked ok. So I guess the issue occurs only with some apps. Thanks

    That means there's a bug in Delayrium regarding its state save/restore, that you should report to its developers. I bet you'll see similar problem just by saving and reloading the AUM session?

  • auxmuxauxmux

    Thinking about favorites. This would be great for AUM presets as well. I have so many across apps, it'd great to filter and/or mark faves.

  • j_liljedahlj_liljedahl

    @auxmux said:
    Thinking about favorites. This would be great for AUM presets as well. I have so many across apps, it'd great to filter and/or mark faves.

    You mean AUv3 plugin user presets? The modern way to save those, via the user preset API introduced in iOS 13, do not support tags or folders, or even renaming. But you could open a preset and resave it with something in the name as mark (for example a heart emoji, etc)

  • SamuSamu

    I think a 'Favorite AUv3' list per 'category' (Instrument, Effect, Processor) would be nice for starters as I seldom use presets unless the Plug-In manages them. This way we could easily hide the plug-ins we rarely need or use...

    In practice the lists would be like the current listings but with the option to show/hide individual entries.

    Can't estimate the implementation time but a few hours here and there during a couple of weeks should be enough for a list-filter implementation?

    Cheers!

  • richardyotrichardyot

    I'm having timing issues that weren't present before:

    • With Link active, load a Lumbeat drum app into an Aum slot, press play in AUM so the drums start playing
    • While the playhead is active tap record to activate recording on the next bar (synced with Link)
    • Record 16 bars of audio and then tap the record button again to stop at the end of the current bar (this creates a loopable file)
    • Locate the recorded audio in Audioshare, and import it into a DAW set to the same BPM - you will note that the tempo does not match, the imported file is misaligned.
  • richardyotrichardyot

    @j_liljedahl I've made a short video showing the timing issue:

    https://www.dropbox.com/s/9kqgfe6inhrrh41/Aum Bug.mp4?dl=0

  • j_liljedahlj_liljedahl
    edited June 2022

    @richardyot said:
    I'm having timing issues that weren't present before:

    • With Link active, load a Lumbeat drum app into an Aum slot, press play in AUM so the drums start playing
    • While the playhead is active tap record to activate recording on the next bar (synced with Link)
    • Record 16 bars of audio and then tap the record button again to stop at the end of the current bar (this creates a loopable file)
    • Locate the recorded audio in Audioshare, and import it into a DAW set to the same BPM - you will note that the tempo does not match, the imported file is misaligned.

    Here's what I think might be happening for you. While synchronized via Ableton Link, the displayed tempo (115 in your case) is just the "target" tempo, the real internal tempo can/will fluctuate in small amounts. This is the nature of Link.

    Just setting the same BPM in two different apps will never guarantee that stuff lines up, you would need to actually sync them for that. Or stretch the file according to how many beats it contains. When recording with Link enabled in AUM, a synced loop will seldom be the exact calculated length, it will often diff with a few samples. I'm not sure how large the drift is in your example?

    For best precision, turn off Link, which will allow AUM to use its sample precise clock. Then use apps and plugins that supports standard host sync. (I would consider an IAA/AUv3 that does not listen to host sync to be unfinished). Recordings should then be of exact calculated length. Then it's up to the app you import this recording to do the right thing with it.

    Another thing to check is that Lumbeat is actually on time? Try comparing with the AUM built-in metronome and see if you hear any drift.

  • richardyotrichardyot

    @j_liljedahl said:

    @richardyot said:
    I'm having timing issues that weren't present before:

    • With Link active, load a Lumbeat drum app into an Aum slot, press play in AUM so the drums start playing
    • While the playhead is active tap record to activate recording on the next bar (synced with Link)
    • Record 16 bars of audio and then tap the record button again to stop at the end of the current bar (this creates a loopable file)
    • Locate the recorded audio in Audioshare, and import it into a DAW set to the same BPM - you will note that the tempo does not match, the imported file is misaligned.

    Here's what I think might be happening for you. While synchronized via Ableton Link, the displayed tempo (115 in your case) is just the "target" tempo, the real internal tempo can/will fluctuate in small amounts. This is the nature of Link.

    Just setting the same BPM in two different apps will never guarantee that stuff lines up, you would need to actually sync them for that. Or stretch the file according to how many beats it contains. When recording with Link enabled in AUM, a synced loop will seldom be the exact calculated length, it will often diff with a few samples. I'm not sure how large the drift is in your example?

    For best precision, turn off Link, which will allow AUM to use its sample precise clock. Then use apps and plugins that supports standard host sync. (I would consider an IAA/AUv3 that does not listen to host sync to be unfinished). Recordings should then be of exact calculated length. Then it's up to the app you import this recording to do the right thing with it.

    Another thing to check is that Lumbeat is actually on time? Try comparing with the AUM built-in metronome and see if you hear any drift.

    Thanks for getting back to me. I do think this is an issue that has cropped up with the latest update, simply because this is a workflow I have been using for years and years without ever having come across this issue previously. It's only with the latest update that I'm getting this tempo drift, and as you can see in the video it's quite severe.

    I've always used this method for creating beat-perfect loops with Lumbeat apps, and it's always been reliable in the past.

  • auxmuxauxmux

    @j_liljedahl said:

    @auxmux said:
    Thinking about favorites. This would be great for AUM presets as well. I have so many across apps, it'd great to filter and/or mark faves.

    You mean AUv3 plugin user presets? The modern way to save those, via the user preset API introduced in iOS 13, do not support tags or folders, or even renaming. But you could open a preset and resave it with something in the name as mark (for example a heart emoji, etc)

    Not user presets per AU, but AUM presets. I tend to use those more than presets managed by AUs.

  • j_liljedahlj_liljedahl

    @auxmux said:

    @j_liljedahl said:

    @auxmux said:
    Thinking about favorites. This would be great for AUM presets as well. I have so many across apps, it'd great to filter and/or mark faves.

    You mean AUv3 plugin user presets? The modern way to save those, via the user preset API introduced in iOS 13, do not support tags or folders, or even renaming. But you could open a preset and resave it with something in the name as mark (for example a heart emoji, etc)

    Not user presets per AU, but AUM presets. I tend to use those more than presets managed by AUs.

    I’m not sure what AUM presets are? Do you mean AUM sessions? AUv3 user presets can be saved both locally in AUM, and shared between hosts using the ”new” user preset functionality since iOS 13.

  • j_liljedahlj_liljedahl

    @richardyot said:

    @j_liljedahl said:

    @richardyot said:
    I'm having timing issues that weren't present before:

    • With Link active, load a Lumbeat drum app into an Aum slot, press play in AUM so the drums start playing
    • While the playhead is active tap record to activate recording on the next bar (synced with Link)
    • Record 16 bars of audio and then tap the record button again to stop at the end of the current bar (this creates a loopable file)
    • Locate the recorded audio in Audioshare, and import it into a DAW set to the same BPM - you will note that the tempo does not match, the imported file is misaligned.

    Here's what I think might be happening for you. While synchronized via Ableton Link, the displayed tempo (115 in your case) is just the "target" tempo, the real internal tempo can/will fluctuate in small amounts. This is the nature of Link.

    Just setting the same BPM in two different apps will never guarantee that stuff lines up, you would need to actually sync them for that. Or stretch the file according to how many beats it contains. When recording with Link enabled in AUM, a synced loop will seldom be the exact calculated length, it will often diff with a few samples. I'm not sure how large the drift is in your example?

    For best precision, turn off Link, which will allow AUM to use its sample precise clock. Then use apps and plugins that supports standard host sync. (I would consider an IAA/AUv3 that does not listen to host sync to be unfinished). Recordings should then be of exact calculated length. Then it's up to the app you import this recording to do the right thing with it.

    Another thing to check is that Lumbeat is actually on time? Try comparing with the AUM built-in metronome and see if you hear any drift.

    Thanks for getting back to me. I do think this is an issue that has cropped up with the latest update, simply because this is a workflow I have been using for years and years without ever having come across this issue previously. It's only with the latest update that I'm getting this tempo drift, and as you can see in the video it's quite severe.

    I've always used this method for creating beat-perfect loops with Lumbeat apps, and it's always been reliable in the past.

    I didn’t change anything regarding this, except allowing a sample perfect clock when Link is disabled.

    Did you check if Lumbeat drifts compared to AUMs metronome?

  • auxmuxauxmux

    @j_liljedahl said:

    @auxmux said:

    @j_liljedahl said:

    @auxmux said:
    Thinking about favorites. This would be great for AUM presets as well. I have so many across apps, it'd great to filter and/or mark faves.

    You mean AUv3 plugin user presets? The modern way to save those, via the user preset API introduced in iOS 13, do not support tags or folders, or even renaming. But you could open a preset and resave it with something in the name as mark (for example a heart emoji, etc)

    Not user presets per AU, but AUM presets. I tend to use those more than presets managed by AUs.

    I’m not sure what AUM presets are? Do you mean AUM sessions? AUv3 user presets can be saved both locally in AUM, and shared between hosts using the ”new” user preset functionality since iOS 13.

    Thinking about the "Save in AUM" local presets for AUs vs the user ones that can be used across hosts, and having some means of sorting/filtering those.

  • richardyotrichardyot

    @j_liljedahl said:
    Did you check if Lumbeat drifts compared to AUMs metronome?

    I just tested it, and the AUM metronome stays in sync with the drum app no matter how long it runs for. It looks to me that the problem occurs once the file is rendered.

    I'm using a sample rate of 44.1 on a 2017 10.5 iPad Pro, if that helps.

    If I open the recording in Audioshare I can see that it doesn't conform to a set number of beats:

    And if I crop the file using the "snap to beat" option I can see that it's out of sync:

  • richardyotrichardyot

    @j_liljedahl I've narrowed the problem down, it's nothing to do with Link or with using IAA, it appears to be a sample rate issue.

    Instead of using Link I used an AUv3 app (Sugar Bytes DrumComputer) that follows the AUM clock. If my sample rate is set to 44.1 then I get the same error with the timing drifting in the rendered file. If I set the sample rate to 48 then the rendered file conforms to the correct tempo.

  • espiegel123espiegel123

    @richardyot said:
    @j_liljedahl I've narrowed the problem down, it's nothing to do with Link or with using IAA, it appears to be a sample rate issue.

    Instead of using Link I used an AUv3 app (Sugar Bytes DrumComputer) that follows the AUM clock. If my sample rate is set to 44.1 then I get the same error with the timing drifting in the rendered file. If I set the sample rate to 48 then the rendered file conforms to the correct tempo.

    My understanding from conversations with Michael is that this is an OS bug. Some devices have a fixed hardware sample rate and implement sample rates strictly via software (surprisingly even an iPad 6 whose default sample rate is 44.1k) AND provide strange timestamps and numbers of sample per window. This is all fine when one uses the sample-based clock rather than the other clock (sorry, I don't know the right names)

    If you look in the archives here, you will find a couple of threads about the old AUM and how loop lengths on some devices at some sample rates were not the correct number of samples. For example, on my iPad 6 running at 48k was required. At 44.1k, loops were off.

  • j_liljedahlj_liljedahl

    @richardyot said:
    @j_liljedahl I've narrowed the problem down, it's nothing to do with Link or with using IAA, it appears to be a sample rate issue.

    Instead of using Link I used an AUv3 app (Sugar Bytes DrumComputer) that follows the AUM clock. If my sample rate is set to 44.1 then I get the same error with the timing drifting in the rendered file. If I set the sample rate to 48 then the rendered file conforms to the correct tempo.

    Yes, this was what I was talking about. If you disable Link (turn it fully off in the clock options), AUM will use a precise clock based on sample time instead of the host-tick-based Link clock.

    There's simply no way to combine Ableton Link with the idea that X bars at tempo T equals exactly Y samples. Also with the "correct" sample rate, as soon as you connect with Link peers running on other devices, the clock time will do small adjustments and corrections to keep the devices in sync. The sample clock of two devices will never be fully in sync unless you hook up WordClock between the audio interfaces.

  • Wrlds2ndBstGeoshredrWrlds2ndBstGeoshredr

    1) When I touch a channel send, it opens a set node color window. It used to take me to the bus menu to select a different bus. That was far more useful than the node color window.

    2) Last night a couple of my file players would not play after I pressed start. After a few more tries they would start.

  • nuno_agogonuno_agogo

    @Wrlds2ndBstGeoshredr said:
    1) When I touch a channel send, it opens a set node color window. It used to take me to the bus menu to select a different bus. That was far more useful than the node color window.

    +1

  • wimwim

    @Wrlds2ndBstGeoshredr said:
    1) When I touch a channel send, it opens a set node color window. It used to take me to the bus menu to select a different bus. That was far more useful than the node color window.

    Long-press brings up the replace option.

  • j_liljedahlj_liljedahl

    @nuno_agogo said:

    @Wrlds2ndBstGeoshredr said:
    1) When I touch a channel send, it opens a set node color window. It used to take me to the bus menu to select a different bus. That was far more useful than the node color window.

    +1

    It's hard to please everyone. Custom name and color for busses was a common user request. The logical place to put the UI for that is when tapping the node, just as it works for every other node - they bring up the UI for that node (if it has one). But yes, long press and tap Replace will give you the same thing. (Yes, it's one extra tap).

  • nuno_agogonuno_agogo

    @j_liljedahl said:

    @nuno_agogo said:

    @Wrlds2ndBstGeoshredr said:
    1) When I touch a channel send, it opens a set node color window. It used to take me to the bus menu to select a different bus. That was far more useful than the node color window.

    +1

    It's hard to please everyone. Custom name and color for busses was a common user request. The logical place to put the UI for that is when tapping the node, just as it works for every other node - they bring up the UI for that node (if it has one). But yes, long press and tap Replace will give you the same thing. (Yes, it's one extra tap).

    will work for me then. thought it was gone at all. AUM is my number one, so very pleased :)

  • NeuMNeuM

    @Wrlds2ndBstGeoshredr said:

    @espiegel123 said:

    @Wrlds2ndBstGeoshredr said:
    @j_liljedahl

    Since I updated AUM, none of my fabfilters AUs will load. The error is “no such plugin; uuid not found”.

    Have you rebooted?

    That fixed it. Tnx!

    I can't count the number of times some bizarre error has been fixed with a simple reboot of the ole iPad.

  • GeoTonyGeoTony

    I agree with 2 @Wrlds2ndBstGeoshredr re file player not playing. To be honest I think I have this for the last couple of years. Will try and video and let @j_liljedahl have the details.

  • Wrlds2ndBstGeoshredrWrlds2ndBstGeoshredr

    @j_liljedahl

    @nuno_agogo said:

    @Wrlds2ndBstGeoshredr said:
    1) When I touch a channel send, it opens a set node color window. It used to take me to the bus menu to select a different bus. That was far more useful than the node color window.

    +1

    It's hard to please everyone. Custom name and color for busses was a common user request. The logical place to put the UI for that is when tapping the node, just as it works for every other node - they bring up the UI for that node (if it has one). But yes, long press and tap Replace will give you the same thing. (Yes, it's one extra tap).

    will work for me then. thought it was gone at all. AUM is my number one, so very pleased :)

    This seems like one of those cases where pleasing the power users makes things more confusing for the majority. On the other hand, it is a nice feature. I can’t complain.

  • j_liljedahlj_liljedahl

    @Wrlds2ndBstGeoshredr said:
    @j_liljedahl

    @nuno_agogo said:

    @Wrlds2ndBstGeoshredr said:
    1) When I touch a channel send, it opens a set node color window. It used to take me to the bus menu to select a different bus. That was far more useful than the node color window.

    +1

    It's hard to please everyone. Custom name and color for busses was a common user request. The logical place to put the UI for that is when tapping the node, just as it works for every other node - they bring up the UI for that node (if it has one). But yes, long press and tap Replace will give you the same thing. (Yes, it's one extra tap).

    will work for me then. thought it was gone at all. AUM is my number one, so very pleased :)

    This seems like one of those cases where pleasing the power users makes things more confusing for the majority. On the other hand, it is a nice feature. I can’t complain.

    Note that getting directly to the node picker (for replacing the node) was just a shortcut for a few kind of nodes (Bus nodes and HW in/out nodes), because they had no other UI to show before. Now that Bus nodes have an UI, that shortcut had to go. Same thing will happen if HW in/out nodes gets an UI.

  • iLLaFenTiLLaFenT

    Awesome Update Man

  • cuezaireekaacuezaireekaa
    edited June 2022

    Does anyone ever have an issue when sliding an effect node left or right, and it just scrolls the page most the time? I have a hard time getting the page to not scroll, and I just want to enable or disable the node. Am I doing something wrong?
    Edit: perhaps I was just not patient enough to let the screen stop scrolling before I swipe the node..

Sign In or Register to comment.

© Vanilla Keystone Theme 2024