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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Comments
Yes, please. Multi-audio output would also be sweet.
AUv3 support is coming in Audulus 4: https://forum.audulus.com/t/auv3-delayed-until-audulus-4
That sounds really good, and could hopefully be universal too. MiRack patches running in NS2 or AUM on iPhone would be great
Of course .. that's the idea .. you build patch in standalone version.. you define those macro knob mappings in standalone version.. you save patch .. then you export patch to AU plugin .. you switch to host app, load AU plugin.. and interface of plugin would contain just those macro kbobs .. you choose patch (previously made in standalone version) .. best of both worlds
Haha I’m not a hater but the icon isn’t my fav 😂😂
Man I literally hate 4p icons lol I hide them deep in folders
I certainly wouldn't pay any price, that is silly. I also am not keen on macro knobs I prefer automation of all the knobs.
Multi audio input and output please!! With AB support we could make complex FX chains or mix inside MiRack!
I totally agree, I want to record and automate all knobs, sliders, switches and x/y pad movements from the original UI. This is why miRack should be a AU plugin, not an AU host. @mifki IAA/AB iOS plugin format are deprecated so iOS AU should be your focus for audio/MIDI interconnectivity.
I suspect if it becomes AUv3, it will lose a lot. As a host, Vitaly can use multiple cores in away that I don’t think will be possible as AUv3 ... and he doesn’t have the same memory limitations to deal with,
If it’s a AU host it will lose one of the most important capabilities the ability to record automations directly from the module UIs into a DAW. AU has much finer increments compared to MIDI and it is less CPU intensive.
@philowerx : but AUs can't multithread as a host can. As I understand it, the reason miRack seems so much lighter on CPU use than similar soft synths is due to the multithreading. You can currently automate things within miRack using the in-built sequencers to send cv to the parameters you want to automate.
Also, aren't there problems getting an AU host to know what automatable items exist in an AU plugin that is dynamic? IE, does the list of items in a host refresh as things are added to hosted AU? I think that's where macro knobs would alleviate that issue?
Preguntas?!
Host is better in my opinion because it can be it's own ecosystem. Also now with audio recorders like the 4pockets app, you could do a lot once multi-out is implemented.
In BeatMaker 3 you move an AU UI knob, slider, switch, etc and movement is automatically assigned an AU lane in the sequencer. It’s so much more intuitive and immediate compared to having to decide which parameters you want to record first and assigning each one of them to a macro.
While I agree with the main point about AU being the way forward, just a clarification ...
Audiobus isn't depreciated. It's not an Apple product that they can depreciate. @Michael has committed to maintaining Audiobus capability even if IAA eventually no longer functions.
I personally don’t need this to be AU and don’t have strong feelings about it being a host, but between the two I’d say being a host makes way more sense.
Fair. That's a lot like how Reason works (and one of the reasons I like it so much)
I dont think macro knobs is the best way, it always feels unsatisfying so i hope if automation becomes a feature it is for all knobs. Gesture record would be ideal.
There is already a module that is a gesture recorder.
Mifky said that he is considering AU plugin which would be just readonly player for patches with few knobs - not full miRack UI with all modules squashed into small AU plugin viewport. For this structure marco knos are perfect. Btw they did work perfectly in Nord Modular G2.
this concept (small readonly patch "player" with just few knobs) means that idea "i weak this knob in this module and automation lane appears in host" is prey much now-go.
In case AU version will be full rack with all modules - don't forget it is dynamic structure, so every new module added to rack would mean whole bunch of new parameters added to plugin - if miRack will be fully available as AU plugin
i'm pretty sure hosts will be not able to deal with situation of dynamically added new parameters...
Don't forget that every instance of such plugin would theoretically have different parameters based on patch you loaded
So direct access to all parameters of patch is obviously impossible even for readonly player - fixed macro knobs are probably only real solution...
At the end, i'm pretty sure having AU plugin with exposed hundreds (if not thousands) of parameters to Host app would be pretty good source of crashes and troubles ;
The Audulus 3 beta with AUv3 functionality, allowed you to route MIDI to the AUv3 instance and then MIDI learn the controls in the patch. At any time you could change your patch and reassign the controls. When you saved the patch, it would also save the MIDI assignments too.
This is different than having the controls exposed to the host DAW which would be a static list. Perhaps there’s a way to update that list when you load in a new preset?
Then there’s the ability to automate the controls of an AUv3 instance which involves moving the GUI controls and then having the host app (e.g. Cubasis 2 or BM3) record those automations. The advantage of GUI automation is that the resolution is much finer than is possible with MIDI so you can have smoother movements with more detail. The downside is not all AUv3 hosts support this functionality. It would be very nice to have a modular AUv3 app that could support this. I don’t know how dynamic this can be with an AUv3 app and perhaps you’d have to take the approach of building your patch first, save it, and then load an instance with that AUv3 and patch in an AUv3 host. Currently there’s not a way to automate the controls for MIDI effect AUv3 apps from its GUI the way you can for AUv3 instruments in Cubasis 2.
The Mozaic app allows you to create different patches but the exposed parameters are all oriented towards the generic controls for all of the layouts so this suggests at the very least that making patch specific exposed parameters is more difficult or perhaps not currently possible on iOS and/or AUv3 hosts don’t support that functionality.
Presumably with an AUv3 player type app you could load in a patch and then it would pass the appropriate information onto the host app if the developer created a way to translate a patch’s controls into a list to output to the host AUv3. Would the AUv3 host only get this information when it’s first loaded or could the host update this info each time you loaded a different patch preset into the AUv3 instance?
It seems to me these sorts of functionalities might not be possible with AUv3 and at the very least would require both AUv3 apps and AUv3 host apps to support them which might be more effort than developers would want to take on?
For example, AUv3 apps could have multiple audio output ports like IAA apps can have them yet I’m not aware of AUv3 apps or hosts that currently support this. The Audulus 4 developer has said he plans to have multiple audio output functionality for AUv3. The AUM developer has mentioned providing AUv3 multiple audio output port support in the app.
Clearly as the level of complexity of what’s possible for AUv3 and AUv3 hosts increases, the level of adoption, and the difficulty of incorporating those features will increase. Perhaps some host app will be developed to address these modular/patch base challenges with the ability to then output stems of any audio and MIDI tracks for further processing in more traditional DAWs? The advantage of such a modular AUv3 approach is that users can create custom synths and MIDI processors to use in their setups that would be too niche for it to be worthwhile for a developer to create an app for because there simply wouldn’t be enough people interested in it whereas people could create these modular patches themselves or share them with members of their modular community.
Modular AUv3 and AUv3 host developers could then focus on supporting their unique needs while other app developers would continue to focus on the larger mainstream music community.
Any developer insights about these questions would be welcome.
It records all gestures made to the parameters on the modules used in the patch?
Macros are very unsatisfactory, if the module doesnt have many parameters no need for marcos just allow all knobs to be automated.
No please, no more “macro-knobs”!!!!!
And I don’t want any kind of automation. I love the modular approach of miRack, not a some kind of auv3 synth
Fair point indeed 🙂 Of course you wouldn’t have to use it if you didn't want to. Mirack wouldn’t look any different.
There is a recording x/y pad. Use as many as you want and send the cv to control what you want.
Tbh, this automation talk sounds a little bit like people not realizing that modular synths are designed to have the parameters controlled by cv. So you tend to use modulation sources and sequencers to control params.
Exactly!! We have a LOT of modulation inside miRack already !!
Ah ok that not what i meant. I understand what modular synths are designed for, i have eurorack. My point was i don’t want macros knobs and if it went that route automation per parameter is preferred.
Personally I like mirack to host AUv3 as i mentioned before a few weeks ago.
Perhaps an AU Rack Player that wouldn’t support creating of patches, but could play them back - multiple instances worth if possible.
Off-topic, but related to the quoted comment:
I'm still waiting for Native Instruments to acknowledge how HUGE a "Reaktor Player for iOS" would be and develop it already. Imagine being able to have immediate hands-on control over a Reaktor Ensemble imported via iTunes/iCloud/Dropbox/etc.