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 by mifki Limited - Live!!!

1535456585982

Comments

  • Ohh man, the wait for this one felt forever! This is gonna be incredible paired with Drambo.

  • edited May 2020

  • @mifki pouring a lot more time into learning miRack but I find that the one thing that slows me down is navigating the modules.

    My memory isn't what it used to be, so I was wondering whether it would be possible to have text search for module name and description?

    The tags view helps a bit but I find that there are many modules that haven't been tagged correctly.

    That's my only issue currently. Everything else is working brilliantly for me.

  • @Jocphone said:
    @mifki pouring a lot more time into learning miRack but I find that the one thing that slows me down is navigating the modules.

    My memory isn't what it used to be, so I was wondering whether it would be possible to have text search for module name and description?

    The tags view helps a bit but I find that there are many modules that haven't been tagged correctly.

    That's my only issue currently. Everything else is working brilliantly for me.

    +1

  • This is the best news ever.

  • So, what can this do (or will do as an Auv3) that Drambo can't?

  • @RajahP said:
    So, what can this do (or will do as an Auv3) that Drambo can't?

    In terms of eurorack/modular, everything.

  • edited May 2020

    Feedback! End of cycle triggers. Recursive patching. Sequencers. (Drambo has a powerful timeline sequencer, but doesn’t have a very robust note sequencing module.)

    Edit: it also has more module variety. So there are a number of different filters / amps etc, whereas Drambo more or less just has 1 of everything. I think it’ll be updated in the future to offer different filter models etc.

    @RajahP said:
    So, what can this do (or will do as an Auv3) that Drambo can't?

  • edited May 2020

    @RajahP said:
    So, what can this do (or will do as an Auv3) that Drambo can't?

    I would said they are a bit different kind of beasts .. Main difference is probably that Drambo has predefined "from left to right" signal flow, every new module added to chain is automaticaly wired with previous module and you can't make feedbacks (yet) .. this is not bad thing, it has a some advantages - it simplifies whole thing and you can concentrate more on making music than on wiring things in right way ..

    And of course in terms of UI you don't see cables, Drambo uses color coding (interconnected output from one module has same color as input on following next connected module)

    In miRack(generally in standard eurorack-like modular) on other side you aren't limited this way, you can cross-connect every module with every other module in rack ..

    generally speaking - Drambo is like modular synth for people for who classic modular is too complicated - because in Drambo just play adding modules in right order leads to fully working patch, without need of manually wire anything with anything... Also Drambo adds sequencer/groovebox flavour to the game.

    On other side miRack/VCVrack/eurorack is just plain vanilla modular, without limitations. IF you put some modules to rack, you need to connect them in meaningfull way to get meaningfull result. But, you're not limited in some pre-defined direction of signal flow - i mean from left to right, from top to bottom, any module with any other loaded module ..

    It's on you which approach is better for you. I like Drambo for intuitive building of groove, loops, song fragments, on other side i like miRack for simply loading it to AUv3 slot in NS and building synth or FX patch i want ..

  • @dendy said:
    Be prepared, it's coming !

    Lol, for a moment there my brain tricked me into seeing patch cables BETWEEN AUv3 plugin windows.
    Keep the dream alive :joy:

  • @dendy
    Sorry, but I can hardly wait... :)
    Sooo...
    Are multi instances working fine?
    Preset/project loading is working fine?
    All syncs well (host tempo to internal seqs)?
    I guess there are no parameters exposed to the host, is there anything exposed like start/stop maybe?
    Thanks in advance!

  • @0tolerance4silence Yes to all above. 😁 It's all possible.

  • @OnfraySin said:

    @RajahP said:
    So, what can this do (or will do as an Auv3) that Drambo can't?

    In terms of eurorack/modular, everything.

    @aleyas said:
    Feedback! End of cycle triggers. Recursive patching. Sequencers. (Drambo has a powerful timeline sequencer, but doesn’t have a very robust note sequencing module.)

    Edit: it also has more module variety. So there are a number of different filters / amps etc, whereas Drambo more or less just has 1 of everything. I think it’ll be updated in the future to offer different filter models etc.

    @RajahP said:
    So, what can this do (or will do as an Auv3) that Drambo can't?

    @dendy said:

    @RajahP said:
    So, what can this do (or will do as an Auv3) that Drambo can't?

    I would said they are a bit different kind of beasts .. Main difference is probably that Drambo has predefined "from left to right" signal flow, every new module added to chain is automaticaly wired with previous module and you can't make feedbacks (yet) .. this is not bad thing, it has a some advantages - it simplifies whole thing and you can concentrate more on making music than on wiring things in right way ..

    And of course in terms of UI you don't see cables, Drambo uses color coding (interconnected output from one module has same color as input on following next connected module)

    In miRack(generally in standard eurorack-like modular) on other side you aren't limited this way, you can cross-connect every module with every other module in rack ..

    generally speaking - Drambo is like modular synth for people for who classic modular is too complicated - because in Drambo just play adding modules in right order leads to fully working patch, without need of manually wire anything with anything... Also Drambo adds sequencer/groovebox flavour to the game.

    On other side miRack/VCVrack/eurorack is just plain vanilla modular, without limitations. IF you put some modules to rack, you need to connect them in meaningfull way to get meaningfull result. But, you're not limited in some pre-defined direction of signal flow - i mean from left to right, from top to bottom, any module with any other loaded module ..

    It's on you which approach is better for you. I like Drambo for intuitive building of groove, loops, song fragments, on other side i like miRack for simply loading it to AUv3 slot in NS and building synth or FX patch i want ..

    Thanks.. looking forward to the videos..

  • edited May 2020

    All my answers are based on my testing inside NS, didn't tested it in any other DAW ...

    Are multi instances working fine?

    Perfectly. Tried project with 10 instances - totally smooth .. of course it depends on complexity of your patches, mine was like 3-4 oscillators, 2-4 envelopes, 2-4 lfos, some filter, ovedrive, reverb, delay, chorus.. stuff like that

    Preset/project loading is working fine?

    Yeah, saving with project file, save patch individual withing miRack patch browser - everything works just fine. Mifky reworked patch handling (i think this is already available in public version) and it's very good now.

    All syncs well (host tempo to internal seqs)?

    Totally rock solid. Didn't experiences single one issue.

    I guess there are no parameters exposed to the host, is there anything exposed like start/stop maybe?

    Thanks in advance!

    You can automate selected parameters. Mifky made pretty handy "macro knobs" like implementation to work around dynamically changing list of internal parameters (which is not supported by AUv3 standard). You have list of probably 20 fixed paraemters which are exposed to host app (with generic names parmeter 01, 02, 03 ... etc). Those parameters are possible to automate i host app.

    Then, inside miRack, you can assign any of those parameters to any module parameter (one external automatable parameter can control multiple mirack module parameters at once). This assignment is then stored together with patch.

    For start stop you have "HOST" module inside miRack, which you can use for synchronising your patch with host tempo ..

  • @auxmux said:
    @0tolerance4silence Yes to all above. 😁 It's all possible.

    @dendy said:
    All my answers are based on my testing inside NS, didn't tested it in any other DAW ...

    Are multi instances working fine?

    Perfectly. Tried project with 10 instances - totally smooth .. of course it depends on complexity of your patches, mine was like 3-4 oscillators, 2-4 envelopes, 2-4 lfos, some filter, ovedrive, reverb, delay, chorus.. stuff like that

    Preset/project loading is working fine?

    Yeah, saving with project file, save patch individual withing miRack patch browser - everything works just fine. Mifky reworked patch handling (i think this is already available in public version) and it's very good now.

    All syncs well (host tempo to internal seqs)?

    Totally rock solid. Didn't experiences single one issue.

    I guess there are no parameters exposed to the host, is there anything exposed like start/stop maybe?

    Thanks in advance!

    You can automate selected parameters. Mifky made pretty handy "macro knobs" like implementation to work around dynamically changing list of internal parameters (which is not supported by AUv3 standard). You have list of probably 20 fixed paraemters which are exposed to host app (with generic names parmeter 01, 02, 03 ... etc). Those parameters are possible to automate i host app.

    Then, inside miRack, you can assign any of those parameters to any module parameter (one external automatable parameter can control multiple mirack module parameters at once). This assignment is then stored together with patch.

    For start stop you have "HOST" module inside miRack, which you can use for synchronising your patch with host tempo ..

    Woaah... That's even better than I imagined.
    Now it's even harder to wait... :smiley:

    Thanks guys for the info!

  • @Peblin said:
    Lol, for a moment there my brain tricked me into seeing patch cables BETWEEN AUv3 plugin windows.

    Are u fvcking nuts? Do you want to open an intergalactic wormhole? That’s too much power for humans. Lol.

  • Looking forward to this as I'm a big fan of VCV. Already bought it, but AUv3 will bring it much more into my workflow.And hopefully Midi Out comes soon as the crazy sequencing it can do is wonderful for generative type of music that isn't confined to grids.

  • Can confirm, rock solid in AUM. Also VERY CPU efficient. I’m using miRack so much more now as a AUv3.

  • @0tolerance4silence said:
    Yay...

    What he said...👍🏼

  • Very excited. Great description @dendy I think this way of exposing parameters in auv3 is excellent. Yea!

  • I was actually thinking about adding a module that would allow to communicate with other AUv3 instances :smiley:

  • @mifki said:
    I was actually thinking about adding a module that would allow to communicate with other AUv3 instances :smiley:

    I beg you. Make this so :D

  • Dear god yes that would be amazing!

    @gonekrazy3000 said:

    @mifki said:
    I was actually thinking about adding a module that would allow to communicate with other AUv3 instances :smiley:

    I beg you. Make this so :D

  • @gonekrazy3000 said:

    @mifki said:
    I was actually thinking about adding a module that would allow to communicate with other AUv3 instances :smiley:

    I beg you. Make this so :D

    Like MIDI or audio?

  • @mifki said:
    miRack is now available as a free macOS app http://mifki.com/blog/mirack-is-now-available-on-macos-10-15/

    Cool, out of curiosity, will this also support Audio Units on macOS when the AUv3 supports comes for iPadOS?
    (Just downloaded the app for macOS to give it a spin and it's so far working great).

  • @mifki said:
    miRack is now available as a free macOS app http://mifki.com/blog/mirack-is-now-available-on-macos-10-15/

    I think there is bug - scrollbars are not working correctly on macOS - when i drag and move crollbars, it moves me down all the time, doesn't matter im which direction i'm dragging scrollbar handle :)

    Btw. just out of curiosity - how much work was to convert iOS version using Catalyst to MacOS version ?

  • edited May 2020

    @Samu said:
    Cool, out of curiosity, will this also support Audio Units on macOS when the AUv3 supports comes for iPadOS?
    (Just downloaded the app for macOS to give it a spin and it's so far working great).

    Depends. I can get it to work in GarageBand/Logic but not in other DAWs that supposedly support AU.

    @dendy said:
    I think there is bug - scrollbars are not working correctly on macOS - when i drag and move crollbars, it moves me down all the time, doesn't matter im which direction i'm dragging scrollbar handle :)

    Strange, I don't have this issue. I'll check, somehow...

    Btw. just out of curiosity - how much work was to convert iOS version using Catalyst to MacOS version ?

    Not too much. I was surprised there's no proper support for some basic stuff in Catalyst like right-clicks and two-finger scrolling, so had to find workarounds for those. Also Mac version was one of the reasons to get rid of the document browser, it didn't work well on Mac, too.

  • edited May 2020

    IMPORTANT (for beta testers): I had to change miRack AUv3 identifier. This means that DAW projects using beta AUv3 version won't find the plugin when AUv3 is publicly released. Save your patches (actually, you can always go back to beta version if needed). Sorry about this, but it was required in order to be able to make AU for Mac in the future.

  • @mifki said:

    @Samu said:
    Cool, out of curiosity, will this also support Audio Units on macOS when the AUv3 supports comes for iPadOS?
    (Just downloaded the app for macOS to give it a spin and it's so far working great).

    Depends. I can get it to work in GarageBand/Logic but not in other DAWs that supposedly support AU.

    Goodie! I guess the 'other' DAWs have to be updated to support sandboxed plug-ins so in due time they will get updated...
    If the mention of sandboxed plug-ins is there the users who use other DAWs could start bugging their DAW developers :D

Sign In or Register to comment.