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.

The apps by Unfiltered Audio has been released

1…6781012

Comments

  • GrandbearGrandbear

    @trickyflemming said:
    @Grandbear @Agatha_aga @drewhino @Kewe_Esse
    New Silo and Needlepoint public betas are up on the App Dev subforum: https://forum.audiob.us/discussion/52675/unfiltered-audio-silo-public-beta/p1
    Let me know if interface performance is improved on your devices.

    Thanks! I can confirm it's working fine now for Silo

  • craftycuratecraftycurate

    @trickyflemming said:
    Just sent in fresh betas for Needlepoint and Silo that should fix the interface choppiness. They should be available tomorrow most likely. Working on Tails fixes now.

    Excellent thanks!

  • [Deleted User][Deleted User]
    edited June 2023

    Deleted

  • LSVLSV

    @wim said:

    That's really interesting. It looks like AUM is getting some out of bounds reporting of plugin latency or something. Not sure if that's something @j_liljedahl might have insight into?

    I've tried with Latency Compensation turned on & off and also pre & post fader just to see. Same results under all those settings. There are rare attempts where two or even three nodes will load but within a few seconds of setting parameters on one, they all go out. If I max out the buffer, I sometimes can load 4 instances before it pops. For now, I'm using a single instance without any hiccups at all.

  • j_liljedahlj_liljedahl

    @wim said:

    @LSV said:
    FYI- This is the error I get while initiating the second node with Tails. @trickyflemming

    @wim said:

    That's really interesting. It looks like AUM is getting some out of bounds reporting of plugin latency or something. Not sure if that's something @j_liljedahl might have insight into?

    Yes when the total latency compensation needs exceeds the internal delay buffer size, this error is shown. Check the Node Statistics to see where the excessive latency is coming from.

  • j_liljedahlj_liljedahl

    @LSV said:

    @wim said:

    That's really interesting. It looks like AUM is getting some out of bounds reporting of plugin latency or something. Not sure if that's something @j_liljedahl might have insight into?

    I've tried with Latency Compensation turned on & off and also pre & post fader just to see. Same results under all those settings. There are rare attempts where two or even three nodes will load but within a few seconds of setting parameters on one, they all go out. If I max out the buffer, I sometimes can load 4 instances before it pops. For now, I'm using a single instance without any hiccups at all.

    Plugin Latency Compensation in AUM can’t be turned off, but maybe you mean you turned it off inside the plugin?

  • Agatha_agaAgatha_aga
    edited December 2022

    @trickyflemming said:
    @Grandbear @Agatha_aga @drewhino @Kewe_Esse
    New Silo and Needlepoint public betas are up on the App Dev subforum: https://forum.audiob.us/discussion/52675/unfiltered-audio-silo-public-beta/p1
    Let me know if interface performance is improved on your devices.

    Yes, Silo and Needlepoint are smooth now, thanks! Even the slight visual glitch when resizing the window disappeared in these 2 apps (it still appears in the other 3 apps).

  • ghost_forestsghost_forests

    Outstanding service @trickyflemming!

  • wimwim

    @j_liljedahl said:

    @LSV said:

    @wim said:

    That's really interesting. It looks like AUM is getting some out of bounds reporting of plugin latency or something. Not sure if that's something @j_liljedahl might have insight into?

    I've tried with Latency Compensation turned on & off and also pre & post fader just to see. Same results under all those settings. There are rare attempts where two or even three nodes will load but within a few seconds of setting parameters on one, they all go out. If I max out the buffer, I sometimes can load 4 instances before it pops. For now, I'm using a single instance without any hiccups at all.

    Plugin Latency Compensation in AUM can’t be turned off, but maybe you mean you turned it off inside the plugin?

    I wonder if the plugin is reporting latency incorrectly.

  • espiegel123espiegel123

    @LSV said:

    @wim said:

    That's really interesting. It looks like AUM is getting some out of bounds reporting of plugin latency or something. Not sure if that's something @j_liljedahl might have insight into?

    I've tried with Latency Compensation turned on & off and also pre & post fader just to see. Same results under all those settings. There are rare attempts where two or even three nodes will load but within a few seconds of setting parameters on one, they all go out. If I max out the buffer, I sometimes can load 4 instances before it pops. For now, I'm using a single instance without any hiccups at all.

    When it happens check the latency compensation stats for the plugins. AUM has a nice display of the relevant info

  • LSVLSV

    @j_liljedahl said:

    Plugin Latency Compensation in AUM can’t be turned off, but maybe you mean you turned it off inside the plugin?

    Yes. In Settings, I switched it off. Not even sure how it works but it had the word Latency so I messed with it.

    @espiegel123 Thanks for the tip. Here's a shot of what I'm seeing once the error happens.

  • espiegel123espiegel123

    @LSV : The latency compensation you are turning off is strictly hardware latency compensation and doesn't apply to plugins.

  • LSVLSV

    I saw that it said hardware but jiggled it anyway. I'm uploading a quick video of how things shakeout as the process of loading unfolds.

    @espiegel123 said:
    @LSV : The latency compensation you are turning off is strictly hardware latency compensation and doesn't apply to plugins.

  • espiegel123espiegel123

    @LSV : have you tried increasing your buffers?

  • LSVLSV

    Quick video demo of what happens when loading more than a single instance of Tails.

  • GrandbearGrandbear
    edited December 2022

    FWIW Tails (App Store version) is also crashing for me when loading more than one instance in Drambo.

    Edit: here's the crash log

  • LSVLSV
    edited December 2022

    @espiegel123 said:
    @LSV : have you tried increasing your buffers?

    Yes. Mentioned upthread.

    @LSV : iPad 11" 2020 padOS 15.7.1

    I had the same experience until I boosted the AUM buffer from 256 to 512. 512 allows 3 instances but no more. All other buffer settings allow only 2 instances before crashing. Under 512, 2 instances run well with no noticeable latency or sluggishness. I prefer to keep AUM buffer at lower setting so maybe this can be looked at.

    There have been a few times where up to four would load successfully before cutting off when trying to set parameters. I believe that was under a buffer of 2048 though.

  • PxlhgPxlhg

    @trickyflemming Got the bundle, great apps! BUT! The latency issue in AUM is not good. Silo seem to work fine but when I added Tails and Bass Mint to some of the synth channels, playing the guitar took me back 20 years - very bad latency. The apps sound okay though, when not playing the guitar. When I deleted the last two mentioned the latency issue went away. (iOS 16.1.1 iPad 11" M1). Really hope we can get a genuine fix for this.

  • espiegel123espiegel123

    @LSV said:

    @espiegel123 said:
    @LSV : have you tried increasing your buffers?

    Yes. Mentioned upthread.

    @LSV : iPad 11" 2020 padOS 15.7.1

    I had the same experience until I boosted the AUM buffer from 256 to 512. 512 allows 3 instances but no more. All other buffer settings allow only 2 instances before crashing. Under 512, 2 instances run well with no noticeable latency or sluggishness. I prefer to keep AUM buffer at lower setting so maybe this can be looked at.

    There have been a few times where up to four would load successfully before cutting off when trying to set parameters. I believe that was under a buffer of 2048 though.

    Some sorts of plugins need non/minimal buffers either do to computational load or the sort of processing they do needs a bigger chunk of samples to work with.

  • LSVLSV

    @espiegel123 said:

    Some sorts of plugins need non/minimal buffers either do to computational load or the sort of processing they do needs a bigger chunk of samples to work with.

    Good to know. Thanks.

  • drewinnitdrewinnit
    edited December 2022

    I updated the apps today and all projects which use them are now glitching heavily for me in Drambo :(

    The wall of glitchy noise was so bad that I thought my iPad was broken! I troubleshot by removing units and then all became good once I removed the Unfiltered stuff

    In the project I troubleshot, it was Bass Mint to blame. I had 2 instances (though one was disabled). With both removed, the project plays. With even a single instance loaded, the entire audio becomes corrupted

  • JumpercollinsJumpercollins
    edited December 2022

    Same here. @trickyflemming think we have a problem. Latest iPad OS iPad Pro M1 store version of Tails.

  • drewinnitdrewinnit

    I'm kinda glad I could quickly identify it was an issue with the apps, the noise was so bad it really made me think I'd dropped my iPad and something inside had broken irreparably!

  • trickyflemmingtrickyflemming

    @drewinnit said:
    I updated the apps today and all projects which use them are now glitching heavily for me in Drambo :(

    The wall of glitchy noise was so bad that I thought my iPad was broken! I troubleshot by removing units and then all became good once I removed the Unfiltered stuff

    In the project I troubleshot, it was Bass Mint to blame. I had 2 instances (though one was disabled). With both removed, the project plays. With even a single instance loaded, the entire audio becomes corrupted

    That's bizarre! Is the interface visible or hidden during the glitching? Bass Mint only had minor changes to the visualizer and had hardware rendering added in. Sounds like I might need to revert the hardware rendering (like we did for the Silo and Needlepoint betas).

    Regarding Tails: yes, latency reporting is broken. I'm waiting for a fix from the JUCE team to add variable latency reporting. I can either update the public beta today to remove the new variable latency switch and add the fix for fixed latency reporting, or I can wait a day or two for the JUCE fix. In the meantime, I've spotted some other things that are contributing to the multi-instance crashing, and that is almost fixed. Just have to do testing and I'll roll out a new public beta.

  • JumpercollinsJumpercollins

    @trickyflemming said:

    @drewinnit said:
    I updated the apps today and all projects which use them are now glitching heavily for me in Drambo :(

    The wall of glitchy noise was so bad that I thought my iPad was broken! I troubleshot by removing units and then all became good once I removed the Unfiltered stuff

    In the project I troubleshot, it was Bass Mint to blame. I had 2 instances (though one was disabled). With both removed, the project plays. With even a single instance loaded, the entire audio becomes corrupted

    That's bizarre! Is the interface visible or hidden during the glitching? Bass Mint only had minor changes to the visualizer and had hardware rendering added in. Sounds like I might need to revert the hardware rendering (like we did for the Silo and Needlepoint betas).

    Regarding Tails: yes, latency reporting is broken. I'm waiting for a fix from the JUCE team to add variable latency reporting. I can either update the public beta today to remove the new variable latency switch and add the fix for fixed latency reporting, or I can wait a day or two for the JUCE fix. In the meantime, I've spotted some other things that are contributing to the multi-instance crashing, and that is almost fixed. Just have to do testing and I'll roll out a new public beta.

    Sweet thanks for the work.

  • drewinnitdrewinnit
    edited December 2022

    @trickyflemming said:

    @drewinnit said:
    I updated the apps today and all projects which use them are now glitching heavily for me in Drambo :(

    The wall of glitchy noise was so bad that I thought my iPad was broken! I troubleshot by removing units and then all became good once I removed the Unfiltered stuff

    In the project I troubleshot, it was Bass Mint to blame. I had 2 instances (though one was disabled). With both removed, the project plays. With even a single instance loaded, the entire audio becomes corrupted

    That's bizarre! Is the interface visible or hidden during the glitching? Bass Mint only had minor changes to the visualizer and had hardware rendering added in. Sounds like I might need to revert the hardware rendering (like we did for the Silo and Needlepoint betas).

    Regarding Tails: yes, latency reporting is broken. I'm waiting for a fix from the JUCE team to add variable latency reporting. I can either update the public beta today to remove the new variable latency switch and add the fix for fixed latency reporting, or I can wait a day or two for the JUCE fix. In the meantime, I've spotted some other things that are contributing to the multi-instance crashing, and that is almost fixed. Just have to do testing and I'll roll out a new public beta.

    If I open Bass Mint I can see the interface, though it is briefly a bit squashed when the unit first opens

    https://u.pcloud.link/publink/show?code=XZz2jsVZ9iXpk9zRqPfLXcYJopErBF2WdeqV

    filmed a quick screen grab. the noise was a bit milder in this one but still made the project unusable until i deleted the Bass Mints

    iOS 13.7, iPad Air 3 (2019)

  • drewhinodrewhino

    @trickyflemming said:
    @Grandbear @Agatha_aga @drewhino @Kewe_Esse
    New Silo and Needlepoint public betas are up on the App Dev subforum: https://forum.audiob.us/discussion/52675/unfiltered-audio-silo-public-beta/p1
    Let me know if interface performance is improved on your devices.

    fantastic! silo looking and feeling lots better in this beta! makes a world of difference with the work flow. thank you for such a next level effects app and all your work! it’s greatly appreciated

  • trickyflemmingtrickyflemming

    Okay new Tails public beta is up. It fixes the multi-instance crash that I was able to reproduce on my end.

    If JUCE doesn't have a patch for variable latency by tomorrow morning, I'll go ahead and send out a beta with variable latency removed so that there's at least a stable version of what was already released (Variable latency will of course be added in once the patch is up).

  • JumpercollinsJumpercollins

    @trickyflemming said:
    Okay new Tails public beta is up. It fixes the multi-instance crash that I was able to reproduce on my end.

    If JUCE doesn't have a patch for variable latency by tomorrow morning, I'll go ahead and send out a beta with variable latency removed so that there's at least a stable version of what was already released (Variable latency will of course be added in once the patch is up).

    @trickyflemming Just tried the new Tails beta that’s fixed the double trouble for me Tails you win😍

  • laopanlaopan

    Silo & Needlepoint is so much better now,but bass mint and lo fi af still a little bit of stuttering,open and close module in lo fi af is very slow in my ipad air 3 15.6.1

Sign In or Register to comment.

© Vanilla Keystone Theme 2024