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 forward momentum of AU

13

Comments

  • @mrcanister said:
    @Fruitbat1919
    yeah, tis a hassle. hehe. but it has always been like that for me. never used DAW's that much, but in bm3 i just name that the pad with the patch i've created. setting up the midi channels is a mare. never encounter much bugs per se tho. also, things don't get too complex because i don;t use a lot of different apps. i've been playing electronica for round 8yrs and i've never completed a single tune. might be a connection there :smile:

    O I’m the same. I’ve never ever finished a tune to a point that it would be classed as releasable (what ever that means lol). I’ve made more quarter tunes than I’ve had hot dinners though ;)

  • @Fruitbat1919 said:

    @oat_phipps said:

    @AndyPlankton said:

    @Fruitbat1919 said:

    @AndyPlankton said:

    @Fruitbat1919 said:

    @Sebastian said:

    @oat_phipps said:

    @Fruitbat1919 said:

    1. Function is related to form if said form is broken, which I truly believe IAA is.

    I sort of agree with you in the sense that IAA, and even Audiobus, felt like iOS hacks to make connectivity even possible.

    In a way, they totally were. Audiobus first, because there was no audio infrastructure to build it on, so it had to be a network protocol and IAA because ... yeah I'm not gonna finish this sentence because I don't want to get disappeared by the CoreAudio team. ;D

    Do they still use hoods and water torture? ;)

    No, they make you sit in front of the system diagram for the IAA implementation, and make you read the bug list repeatedly while ignoring your "If you do it this way it would work better" comments, which in turn sends you into mental confusion.....allowing them to brainwash you..

    You willingly walk out wearing a t-shirt with

    I :heart: IAA

    printed on it..... :D

    I see they got to you @AndyPlankton is there a way to be deprogrammed? ( joking of course. I know you always try to be balanced in your writings :) )

    hehehe The devil needs an advocate ;)

    Job’s taken. Shove off

    Fight, fight, fight...... >:)

    :D :D :D
    I'd lose....I'm a scaredy cat really

  • @AndyPlankton said:

    @Fruitbat1919 said:

    @oat_phipps said:

    @AndyPlankton said:

    @Fruitbat1919 said:

    @AndyPlankton said:

    @Fruitbat1919 said:

    @Sebastian said:

    @oat_phipps said:

    @Fruitbat1919 said:

    1. Function is related to form if said form is broken, which I truly believe IAA is.

    I sort of agree with you in the sense that IAA, and even Audiobus, felt like iOS hacks to make connectivity even possible.

    In a way, they totally were. Audiobus first, because there was no audio infrastructure to build it on, so it had to be a network protocol and IAA because ... yeah I'm not gonna finish this sentence because I don't want to get disappeared by the CoreAudio team. ;D

    Do they still use hoods and water torture? ;)

    No, they make you sit in front of the system diagram for the IAA implementation, and make you read the bug list repeatedly while ignoring your "If you do it this way it would work better" comments, which in turn sends you into mental confusion.....allowing them to brainwash you..

    You willingly walk out wearing a t-shirt with

    I :heart: IAA

    printed on it..... :D

    I see they got to you @AndyPlankton is there a way to be deprogrammed? ( joking of course. I know you always try to be balanced in your writings :) )

    hehehe The devil needs an advocate ;)

    Job’s taken. Shove off

    Fight, fight, fight...... >:)

    :D :D :D
    I'd lose....I'm a scaredy cat really

    I do too. While I’m telling them about why fighting is pointless, I usually get punched lol

  • @RUST( i )K said:

    @Samu said:
    Imagine if IAA was a 'conspiracy'? Where would all the Audio piped thru IAA go to?

    I know, Into Apple's A********

    I wish there was a tool like 'Audio Hijack' in iOS, we would not need to use any 'dirty hacks' at all, just select an apps audio-stream from Core Audio as the source but that would be a big NO-NO for all the big media corps....

    Bingo.

    Bango.

    So that being said, people may want to pay attention to you and I friends at Retronyms.

    They are ....um...branching out of the matrix in a way with changes happening.

    I think Retronyms about to blow up bigger than ever in the next 6 months if you ask me.

    I love their products and support there work 100%.
    Proud to say.

    Yes I miss being able to just open an audio app and record whats coming out of the audio card regardless of it's source (Soundforge - Audacity)

  • @Fruitbat1919 said:

    @AndyPlankton said:

    @Fruitbat1919 said:

    @oat_phipps said:

    @AndyPlankton said:

    @Fruitbat1919 said:

    @AndyPlankton said:

    @Fruitbat1919 said:

    @Sebastian said:

    @oat_phipps said:

    @Fruitbat1919 said:

    1. Function is related to form if said form is broken, which I truly believe IAA is.

    I sort of agree with you in the sense that IAA, and even Audiobus, felt like iOS hacks to make connectivity even possible.

    In a way, they totally were. Audiobus first, because there was no audio infrastructure to build it on, so it had to be a network protocol and IAA because ... yeah I'm not gonna finish this sentence because I don't want to get disappeared by the CoreAudio team. ;D

    Do they still use hoods and water torture? ;)

    No, they make you sit in front of the system diagram for the IAA implementation, and make you read the bug list repeatedly while ignoring your "If you do it this way it would work better" comments, which in turn sends you into mental confusion.....allowing them to brainwash you..

    You willingly walk out wearing a t-shirt with

    I :heart: IAA

    printed on it..... :D

    I see they got to you @AndyPlankton is there a way to be deprogrammed? ( joking of course. I know you always try to be balanced in your writings :) )

    hehehe The devil needs an advocate ;)

    Job’s taken. Shove off

    Fight, fight, fight...... >:)

    :D :D :D
    I'd lose....I'm a scaredy cat really

    I do too. While I’m telling them about why fighting is pointless, I usually get punched lol

    Yeah...sounds familiar :D

  • feels weird talking about AU in the audiobus forum. I barely use it right now... when everything is AU then... audiobus it’s kinda worthless?...

    I know people will argue it will always be useful. I don’t see it. Time will tell...

  • @Lacm1993 said:
    feels weird talking about AU in the audiobus forum. I barely use it right now... when everything is AU then... audiobus it’s kinda worthless?...

    I know people will argue it will always be useful. I don’t see it. Time will tell...

    Audiobus does AU and has a solid connection to other host apps, such as AUM, so yeah, it’s useful :)

  • @Fruitbat1919 said:

    @Lacm1993 said:
    feels weird talking about AU in the audiobus forum. I barely use it right now... when everything is AU then... audiobus it’s kinda worthless?...

    I know people will argue it will always be useful. I don’t see it. Time will tell...

    Audiobus does AU and has a solid connection to other host apps, such as AUM, so yeah, it’s useful :)

    But if In the future I can do everything inside a DAW (because everything it’s AU)? Then... why keep audiobus?... I don’t get it. Any use for it then?

  • personally, I'll always favor tools that have a solid sound engine, sequenced, fx, automation, etc in one convenient package over > @RUST( i )K said:

    @Samu said:
    Imagine if IAA was a 'conspiracy'? Where would all the Audio piped thru IAA go to?

    I know, Into Apple's A********

    I wish there was a tool like 'Audio Hijack' in iOS, we would not need to use any 'dirty hacks' at all, just select an apps audio-stream from Core Audio as the source but that would be a big NO-NO for all the big media corps....

    Bingo.

    Bango.

    So that being said, people may want to pay attention to you and I friends at Retronyms.

    They are ....um...branching out of the matrix in a way with changes happening.

    I think Retronyms about to blow up bigger than ever in the next 6 months if you ask me.

    I love their products and support there work 100%.
    Proud to say.

    Is this to do with whatever they're dropping tomorrow? I never used retronyms apps as none were really for me, but it's seems like they're very capable

  • @Lacm1993 said:

    @Fruitbat1919 said:

    @Lacm1993 said:
    feels weird talking about AU in the audiobus forum. I barely use it right now... when everything is AU then... audiobus it’s kinda worthless?...

    I know people will argue it will always be useful. I don’t see it. Time will tell...

    Audiobus does AU and has a solid connection to other host apps, such as AUM, so yeah, it’s useful :)

    But if In the future I can do everything inside a DAW (because everything it’s AU)? Then... why keep audiobus?... I don’t get it. Any use for it then?

    Yes. For live use DAWs are often too expensive on the overheads. Mixing hosts like AUM and AB are far better for use for multi keyboard setups.

  • @Lacm1993 said:

    @Fruitbat1919 said:

    @Lacm1993 said:
    feels weird talking about AU in the audiobus forum. I barely use it right now... when everything is AU then... audiobus it’s kinda worthless?...

    I know people will argue it will always be useful. I don’t see it. Time will tell...

    Audiobus does AU and has a solid connection to other host apps, such as AUM, so yeah, it’s useful :)

    But if In the future I can do everything inside a DAW (because everything it’s AU)? Then... why keep audiobus?... I don’t get it. Any use for it then?

    I feel that getting MIDI AUs in the MIDI lanes of AB3 could inject new life in it: all the fun of MIDI plugins, without the 'complex' MIDI routing. Sounds like low-hanging-fruit to me :)

  • @brambos said:

    @Lacm1993 said:

    @Fruitbat1919 said:

    @Lacm1993 said:
    feels weird talking about AU in the audiobus forum. I barely use it right now... when everything is AU then... audiobus it’s kinda worthless?...

    I know people will argue it will always be useful. I don’t see it. Time will tell...

    Audiobus does AU and has a solid connection to other host apps, such as AUM, so yeah, it’s useful :)

    But if In the future I can do everything inside a DAW (because everything it’s AU)? Then... why keep audiobus?... I don’t get it. Any use for it then?

    I feel that getting MIDI AUs in the MIDI lanes of AB3 could inject new life in it: all the fun of MIDI plugins, without the 'complex' MIDI routing. Sounds like low-hanging-fruit to me :)

    I think with the ongoing march of AU with AU Midi, there will always be a need for variations in hosts to suit differing needs. DAWs by their very name mean a do it all ‘workstation’, while hosts can be either the same or more specific.

    It would be a shame if Audiobus did not become one of those hosts that fills a specific use case as it already has so much of the work done!

  • I'm just thinking loudly about using @brambos Rozeta plug-ins as 'Midi Inserts' in Cubasis, now that would be yummy :)

  • @Samu said:
    I'm just thinking loudly about using @brambos Rozeta plug-ins as 'Midi Inserts' in Cubasis, now that would be yummy :)

    I was surprised that Cubasis supported AU at all on iOS given Steinberg’s strong history with VST on the desktop. Now that they’ve done a direct deal with Waves and pushed back on AU Full Screen I’m concerned they may not take AU any further (including AU MIDI plugins)

  • @realdavidai said:

    @Samu said:
    I'm just thinking loudly about using @brambos Rozeta plug-ins as 'Midi Inserts' in Cubasis, now that would be yummy :)

    I was surprised that Cubasis supported AU at all on iOS given Steinberg’s strong history with VST on the desktop. Now that they’ve done a direct deal with Waves and pushed back on AU Full Screen I’m concerned they may not take AU any further (including AU MIDI plugins)

    It may take time, but IMO any dev that doesn’t go the AU route is going to fall by the wayside over time. AU in all its iterations is the future on iOS - those that use it the best will no doubt be at the forefront of iOS music making. This is just the start like the early coming of age days of VST on PC

  • @realdavidai said:

    @Samu said:
    I'm just thinking loudly about using @brambos Rozeta plug-ins as 'Midi Inserts' in Cubasis, now that would be yummy :)

    I was surprised that Cubasis supported AU at all on iOS given Steinberg’s strong history with VST on the desktop. Now that they’ve done a direct deal with Waves and pushed back on AU Full Screen I’m concerned they may not take AU any further (including AU MIDI plugins)

    No surprise here....Steinberg, just like all the other major players are not daft, they make a host, and to be successfull going forwards, hosts need to support AU.

  • @tja said:
    As long as there is this strange memory restriction for AUs of about 360 MB, there are by far less usable the possible

    Agree, that is going to hold things back to some extent until they lift that, it seems a bit arbitrary.
    I wonder if there is a way around this for apps that use samples by streaming straight from disk somehow (i think bm2 definitely did this)

  • @RedSkyLullaby said:

    @tja said:
    As long as there is this strange memory restriction for AUs of about 360 MB, there are by far less usable the possible

    Agree, that is going to hold things back to some extent until they lift that, it seems a bit arbitrary.
    I wonder if there is a way around this for apps that use samples by streaming straight from disk somehow (i think bm2 definitely did this)

    For most plugins this limit should not be that.. eh.. limiting. Unless it’s based on sample playback you’ll never fill up 360Mb with 20 instances of synth code and a few bitmaps.

  • edited December 2017

    @brambos you're very optimistic in an age where an app like Dropbox -- which definitely is pure code and not that complex -- is 136 MB in size ;) the software development world needs a huge global reset.

    Edit: OK, maybe a few icons too. Another example is Instagram, at 84 MB. And no, it does NOT already come with all the cat videos IN the app bundle :D

  • @SevenSystems said:
    @brambos you're very optimistic in an age where an app like Dropbox -- which definitely is pure code and not that complex -- is 136 MB in size ;) the software development world needs a huge global reset.

    Edit: OK, maybe a few icons too. Another example is Instagram, at 84 MB. And no, it does NOT already come with all the cat videos IN the app bundle :D

    Wasteful programming :) But seriously, I feel it’s the responsibility of the developer to keep that down. I don’t think any of my apps exceeds 10Mb, and those include a standalone host and a separate plugin. And most of that is taken up by 12 versions of the same startup bitmap for all those iPhone screen versions.

    In fact, my Rozeta plugins don’t exceed 512Kb per instance (including dynamically allocated memory). But those aren’t synth plugins.

  • @brambos said:
    I don’t think any of my apps exceeds 10Mb, and those include a standalone host and a separate plugin. And most of that is taken up by 12 versions of the same startup bitmap for all those iPhone screen versions.

    Haha yes, I checked Ruismaker's size before ranting, and was positively surprised ;) Xequence has now grown from 2.5 to 3.5 MB or so, but that's because of the 24 WAV files for the metronome :D

  • @brambos said:

    @SevenSystems said:
    @brambos you're very optimistic in an age where an app like Dropbox -- which definitely is pure code and not that complex -- is 136 MB in size ;) the software development world needs a huge global reset.

    Edit: OK, maybe a few icons too. Another example is Instagram, at 84 MB. And no, it does NOT already come with all the cat videos IN the app bundle :D

    Wasteful programming :) But seriously, I feel it’s the responsibility of the developer to keep that down. I don’t think any of my apps exceeds 10Mb, and those include a standalone host and a separate plugin. And most of that is taken up by 12 versions of the same startup bitmap for all those iPhone screen versions.

    In fact, my Rozeta plugins don’t exceed 512Kb per instance (including dynamically allocated memory). But those aren’t synth plugins.

    Look at Syntronik. That manages well as an AU. Not sure why most apps can’t to be fair

  • edited December 2017

    I think IAA is fatally flawed and AU is definitely the future but AU has it's own issues so I don't think the future is quite here yet.

    Devices need more RAM to really use AU, 8GB? (I have an AIr 2 with 2 GB this may be better on Pros with 4 GB)

    AU Preset saving is weird and not consistent. Everything should use FIles app now

    360 MB per plugin RAM limit (mentioned above)

    Serious iOS bug with AU host not releasing RAM when AUs are ejected. Host has to be closed and restarted to release this RAM.

    Have I missed anything?

  • @yowza said:
    I think IAA is fatally flawed and AU is definitely the future but AU has it's own issues so I don't think the future is quite here yet.

    Devices need more RAM to really use AU, 8GB? (I have an AIr 2 with 2 GB this may be better on Pros with 4 GB)

    AU Preset saving is weird and not consistent. Everything should use FIles app now

    360 MB per plugin RAM limit (mentioned above)

    Serious iOS bug with AU host not releasing RAM when AUs are ejected. Host has to be closed and restarted to release this RAM.

    Have I missed anything?

    Yes problems still exist. Must admit to having very few issues compared to IAA.

    Yes, preset saves need more uniformity.

    The 360 mb limit seems to not have bothered many large sample use apps, so I’ve yet to see this as a problem.

    Not encountered any issues with going from one host to another without restarts with only AUs involved, so the release issue has yet to cause me any grief at all.

    Yeah iPads need more spec as time goes on for apps to grow naturally and more use of multiple apps. Software is usually forging ahead needing more resources than the lower spec computers have....it’s just the way things are.

    So in real use, AU has shown so little problems to me, that I really can’t be that concerned. IAAs on the other hand are often show stoppers ;)

    AU will improve as it already has been so far. I have seen little IAA improvement at all.

  • edited December 2017

    @yowza said:
    Devices need more RAM to really use AU, 8GB? (I have an AIr 2 with 2 GB this may be better on Pros with 4 GB)

    Have you ever hit the RAM limit with AU before hitting the CPU limit (not referring to the 360Mb per plugin limit, but the overall system memory)? Just curious if that happens in real world projects.

    AU Preset saving is weird and not consistent. Everything should use FIles app now

    Yes, Apple should sort this out for good. To me this is the most pressing and only real issue with AU today.

    360 MB per plugin RAM limit (mentioned above)

    I'll just repeat that this limit is mostly theoretical for pure synthesis and effects plugins. Sample-based plugins will run into this but that's just a tiny subsection of today's AU offer.

    Either way, now that iOS11 has finally left the iPad 4 behind Apple can safely drop (or raise) this limitation in my opinion. Although that may quickly lead to lazily-built sample-players completely hogging every little bit of your system resources.

    Serious iOS bug with AU host not releasing RAM when AUs are ejected. Host has to be closed and restarted to release this RAM.

    Yes, that needs to be solved. But is it a really a real-world problem holding AU back? It's not an inherent AU issue in my opinion, just a bug in iOS that needs to be fixed at some point.

    I think iOS11 really made a big step towards bringing AU to a mature state.

  • @SevenSystems said:

    @brambos said:
    I don’t think any of my apps exceeds 10Mb, and those include a standalone host and a separate plugin. And most of that is taken up by 12 versions of the same startup bitmap for all those iPhone screen versions.

    Haha yes, I checked Ruismaker's size before ranting, and was positively surprised ;) Xequence has now grown from 2.5 to 3.5 MB or so, but that's because of the 24 WAV files for the metronome :D

    And with midi import it will go to 3.6 MB. ;-0. Just kidding.

  • I don’t recall a universal preset mechanism on Desktop? Is there one? I’ve always considered preset handling and navigation part of the identity of a plugin.

  • @realdavidai said:
    I don’t recall a universal preset mechanism on Desktop? Is there one? I’ve always considered preset handling and navigation part of the identity of a plugin.

    That's because it's 'transparent' at least on the Mac all presets (AU or VST) are stored in one common location.

  • You AU people are like a cult. You kinda scare me.

    au.jpg 48.6K
  • @ipadthai said:
    You AU people are like a cult. You kinda scare me.

    Most likely depending on your definition and use of the word ‘Cult’ :)

Sign In or Register to comment.