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.

miRack — now AUv3! — for Beginners

1567810

Comments

  • @mifki said:
    Yeah it got broken some time ago, and I finally found how to fix it, thanks for reminding.

    Thanks!

  • @mifki said:

    @wim said:
    Wireless Audio AUv3 might work once we can load AUv3's. Maybe Sonobus too. Latency is always a big-ass problem with these though. If these guys can't make it more usable/reliable after all their efforts then it seems like an uphill battle for someone with other things on their hands.

    I tried both of them quickly now, they both seem to work. Sonobus seems to have a better latency and obviously more options in general. However I'm getting a lot of dropped packets, not sure whether it's something wrong with my router or what. Make sure to change streaming format to PCM if you want to send CVs. As pointed out above though both are probably not quite suitable for production use over WiFi unfortunately.

    @hghon said:
    I didn’t explain what I meant correctly. I meant send/receive within patches instead of cables that stretch 3 rows and 10 modules across large patches 😄 if the patches are large enough say I want to connect my clock to another module some distance away, send/receive ports would sort that out without having to lock and hide all cables

    Yeah that's how I understood it myself initially, yes, that's a good idea, I'll add it to my list.

    Yea @mifki you can scratch send/receive modules off your list, turns out this functionality is already present. Southpole Snake does exactly that and in a very elegant way 👍👍

  • Version 4 is out, with polyphony!

  • @bygjohn said:
    Version 4 is out, with polyphony!

    Awesome! Going to fire up the iPad then.

  • If you could click a polyphony button on a real modular setup I might be more interested. I’m sticking to digital modular and semi-modular for now and saving my patches too. Great update

  • Great update @mifki working very well so far!

  • That's just epic @mifki , thank you so much! I hope you'll be able to unlock polyphony for the oscillators of Audible instruments and Valley which are my favorites (by far).

  • Agreed this is a great update, definitely craving polyphony for Audible modules.

  • Thank you @mifki!
    Now get busy on that tip jar. 😉

  • edited December 2023

    Thanks for the polyphony @mifki :)
    There’s a persistent bug with saving/exporting a sample from Simpliciter, if I try and save a wav in the mirack folder it crashes all instances of mirack, if I try and choose the iCloud mirack folder it says not allowed. Is this fixable?
    (Via the AUv3 version)

  • @Carnbot said:
    Thanks for the polyphony @mifki :)
    There’s a persistent bug with saving/exporting a sample from Simpliciter, if I try and save a wav in the mirack folder it crashes all instances of mirack, if I try and choose the iCloud mirack folder it says not allowed. Is this fixable?
    (Via the AUv3 version)

    I'll have a look now.

  • edited December 2023

    @mifki Another bug I noticed that last night. Midi out module in AU is not saving the last used devicez which is typically just the host. It reverted to no device when I reopened an AUM session last night. Not sure if happening with midi in too.

    This was fine in previous versions.

  • @Carnbot said:
    Thanks for the polyphony @mifki :)
    There’s a persistent bug with saving/exporting a sample from Simpliciter, if I try and save a wav in the mirack folder it crashes all instances of mirack, if I try and choose the iCloud mirack folder it says not allowed. Is this fixable?
    (Via the AUv3 version)

    What's your use case for recording inside AUv3, is there another way to do what you want? The problem is that AUv3 plugins have very limited access to the file system, even more restricted than the parent app. I'm planning to overhaul asset management at some point and likely will end up with having an internal location for assets and a built-in manager to import/export them because there doesn't seem to be another solution that'd work both standalone and in AUv3 and for all the ways different modules use files. But that'll take some time to implement, hence my question if there's a workaround in the meanwhile for you. I probably can do something to fix Simpliciter sooner but some other modules like NYSTHI recorders still won't work in AUv3 unfortunately.

  • wimwim
    edited December 2023

    That has always puzzled me. Some apps can access the full file system just as well from the AUv3 version as from the standalone, yet developers say this often about AUv3's, so there must be something to it. What I don't understand is how apps like Koala get away with it seemingly smoothly. Oh well. It's a pity files on iOS are such a pain to deal with for developers. 😕

  • edited December 2023

    Apart from their own document folders (which are sadly completely separate for apps and extensions), apps and extensions can access files explicitly selected by users.

    In case of saving a document, the process is to write to a temporary location, and then present a system dialog for user to choose a new location, and the OS will move (or copy) the file. While this works in most cases and will work for Simpliciter, it won't work for some other modules, namely NYSTHI recorders which allow to select a location to save before recording - there's no way to give access to a non-existent file.

    It's not a big issue in standalone app because it can access its documents folder without restrictions and I advise just to use that folder for everything, but extension's documents folder is separate and more importantly not accessible to user in Files app so it's basically useless for this purpose.

  • wimwim
    edited December 2023

    That makes sense. Thanks for taking the time to educate me @mifki. I've always wondered about that.

  • @mifki said:

    @Carnbot said:
    Thanks for the polyphony @mifki :)
    There’s a persistent bug with saving/exporting a sample from Simpliciter, if I try and save a wav in the mirack folder it crashes all instances of mirack, if I try and choose the iCloud mirack folder it says not allowed. Is this fixable?
    (Via the AUv3 version)

    What's your use case for recording inside AUv3, is there another way to do what you want? The problem is that AUv3 plugins have very limited access to the file system, even more restricted than the parent app. I'm planning to overhaul asset management at some point and likely will end up with having an internal location for assets and a built-in manager to import/export them because there doesn't seem to be another solution that'd work both standalone and in AUv3 and for all the ways different modules use files. But that'll take some time to implement, hence my question if there's a workaround in the meanwhile for you. I probably can do something to fix Simpliciter sooner but some other modules like NYSTHI recorders still won't work in AUv3 unfortunately.

    Thanks for looking into it...In this case, using the sampler to record in AUM from both mirack and other apps, gear etc and then exporting the file to use on computer. In this case there are workarounds to get the recordng from simpliciter to my PC by way of other apps but it's just trying a get a workflow with as least steps as possible :)
    Apple have made this far more complicated than it should be, they should share the same folders...

    If I use the standalone mirack I can export from the module to the local folder, but not icloud even if I check the icloud option in the mirack settings, so there does seem to be a general issue with icloud and mirack for me anyway.

  • I'll check iCloud, it does work for me in standalone app but not in AUv3 while in my understanding, the extension should have access to it. I'm not sure why it doesn't work for you in standalone - are you trying to use miRack folder or some other one?

  • Been so good to watch miRack develop over the years, it’s one of the coolest iOS music tools around. Thanks @mifki

  • Scratch that, looks like I've found a solution for the file access problem.

  • That sounds promising :)

    Yeah to clarify, I'm always trying to save in the icloud/miRack folder when working with icloud.
    I tried exporting to the iCloud mirack folder from standalone miRack/simpliciter and it also crashed on my iphone so there is also the bug there happening sometimes, but it can save the regular mirack files to the icloud mirack folder.

  • @mifki
    in latest release (current)- the "xypad" module crashes the miRack:(
    it used to work but now it doesnt for some reason...
    if one has "shift" on and tries to draw something in xypad - boom -
    instant crash of miRack...:(

    can you fix it?! it used to work really well before.
    and its a solid block of my live acts...

    big thnx!

  • @waka_x said:
    @mifki
    in latest release (current)- the "xypad" module crashes the miRack:(
    it used to work but now it doesnt for some reason...
    if one has "shift" on and tries to draw something in xypad - boom -
    instant crash of miRack...:(

    can you fix it?! it used to work really well before.
    and its a solid block of my live acts...

    big thnx!

    Yep instant crash for me as well. Please help @mifki 🙏

  • edited December 2023

    .

  • Now that I experienced the huge benefit in processor power increase using multithreaded, I’m slowly shifting from AUM to miRack for some of my live projects. Roughly I can have 2x + the amount of effects and synths when hosted in miRack.
    One very important feature missing is having multiple AUv3 floating and resize able windows, @mifki have you considered adding this feature to miRack? Thanks!

  • edited January 23

    @Synthi said:
    Now that I experienced the huge benefit in processor power increase using multithreaded, I’m slowly shifting from AUM to miRack for some of my live projects. Roughly I can have 2x + the amount of effects and synths when hosted in miRack.
    One very important feature missing is having multiple AUv3 floating and resize able windows, @mifki have you considered adding this feature to miRack? Thanks!

    Yes, of course, this is planned. I have also mentioned before more DAW-like global transport/tempo controls - these two items together with preset management are the priority now to make miRack better as a host.

  • Wow, great! Thanks!

  • Is it possible to create a Midi Thru in MiRack?
    I need to send midi notes and CC messages directly to my Volca Beats.
    Currently I can send the midi notes but not the CC messages.
    I’m using an external sequencer.

  • @Gravitas said:
    Is it possible to create a Midi Thru in MiRack?
    I need to send midi notes and CC messages directly to my Volca Beats.
    Currently I can send the midi notes but not the CC messages.
    I’m using an external sequencer.

    This may turn out not to work - I’m not an expert, and I may well have got the wrong end of the stick. Wouldn’t be the first time…

    Could you patch the CCs through from a CC input module to a CC output module, alongside the Basic MIDI input and output modules?

  • @bygjohn said:

    @Gravitas said:
    Is it possible to create a Midi Thru in MiRack?
    I need to send midi notes and CC messages directly to my Volca Beats.
    Currently I can send the midi notes but not the CC messages.
    I’m using an external sequencer.

    This may turn out not to work - I’m not an expert, and I may well have got the wrong end of the stick. Wouldn’t be the first time…

    Could you patch the CCs through from a CC input module to a CC output module, alongside the Basic MIDI input and output modules?

    I looked at that and you have to assign
    the CC’s both on the inputs and outputs
    and not simply patch a midi input
    to a midi output and have the midi info
    being passed thru.

Sign In or Register to comment.