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
@mifki
Would it be possible to port Valley Plateau reverb module anytime soon?
Is it under open license?
Looks like it is covered by the GPL 3 licence so unlikely that it can appear in a commercial product.
I'm late to the show! Is it possible to sync MIracks to external midi, either via AB or a module in the app? If so, I'm in.
I read back through the thread and found the answer is yes!
I'm in!
Dexter and Plateau are BSD. Topograph & µGraph are GPL but there may be a possibility to add them, I can't comment on this at the moment.
Version 1.03 is live:
MODULES
APP NEWS
BUGFIXES
@mifki Fantastic app! I hope you do well from it. I've only tested in headphones so far, but sounds quality. 4 hours just flew by, but built some very usable patches!
One humble request: ability to re-colour cables without having to unplug and drag out new cable until the colour of choice appears. Perhaps a long press on a cable then a drop-down menu?
Like others, I really hope to see some new modules. An LPG would be fab.
I just did a few tests.
Well, it somehow works and clock (converted to 16th ticks) and Start/Stop/Continue triggers are available as well but latency is not adjustable (no latency correction) so audio will always be a bit late and even when feeding it perfectly stable MIDI clock, there's noticeable jitter. MIDI clock does not seem to be handled with highest priority in miRack either.
With LINK, Ableton provides a library where the high-priority clock handling is already covered inside the lib while with MIDI clock, the developer has to do it for himself - although there are a few 3rd party libs available too.
Edit: Adding Audiobus 3 (Hardware > AB3 MIDI > miRack) works much better so apparently there's an issue with handling MIDI from hardware ports.
good to know. cheers
For me the use case would be this + small eurorack + another hardware synth and if this would work, i would get es-8 or es-9 for this. However for this to be good enough for standalone use, this should also have a module for loading audio units inside of it and also have all the necessary audio and midi routing capabilities that AUM or audiobus currently provides. And im talking about midi/audio routing between different hardware synths, not just in/out of this app.
Another good approach would be to make this app an audio unit instead of audio unit host, so that you could build multiple smaller racks inside audiobus/aum/etc.
For me personally this app would be likely the only app i would prefer using via IAA, but since they are killing it somewhere in the future, focusing on it might not be the best idea.
Maybe having a standalone for inserting new modules and building the rack and also ofc for normal standalone use and have an AU plugin that could load(and patch cables) saved rack setups built on standalone. I see it could get a bit fiddly building racks inside AU and with ability for people to share these rack presets, people who might not be that interested in learning modular, but just want tons of different AU synths would get to enjoy this without the whole app feeling too intimidating and UI inside AU would be more compact and clearer, easier and more fun to use especially with smaller devices than the largest ipad.
This is a nice project, i hope it turns out great!
Thanks, I'll look into this.
Agree 100%!
+1 on AUv3 plugin prefferable than AU host.
Im not fussed about it being AUv3, i think mirack uses multi threading? Not sure if an auv3 can use multi threading?
Or maybe its that currently no iOS host supports multi threading 🧵?
iDensity v4 is an AU (FX and Instr) client and an AU host.
Does it use multi threading?
I'll leave the implementation details to the dev 😀
@mifki
I believe mirack uses multi threading (sorry im not a programmer so i cant get technical) so that makes it incompatible with ios hosts in terms of it being a AUv3? Also it would compromise mirack’s CPU usage?
Checking in with the question, Is there a way to record mirack yet? Or to play it into a DAW?
Not yet.
Alright, I've just finished reading through this thread as well as the thread on the VCV forums which was closed on 9/22 in hopes of understanding how to integrate mirack and Ableton into a workflow.
At first, I'd thought "I'll use mirack to create patches on my iPad, share them via cloud services to my laptop, open them in VCV, route its audio into my DAW, control it via MIDI from the DAW." In addition to being a lot of steps, I'm inferring that it is going to be difficult to get halfway through this process due to conflicts mentioned in the forums. My first efforts at opening a mirack patch in VCV were met with difficulties due to backward incompatibility. Instruments from v0.6 that work in mirack aren't recognized in VCV. For a brief moment I thought "That's fine, I'll just downgrade VCV Rack on my laptop and work with that."
Given that both VCV Rack and mirack are likely to forge ahead, it seems unnecessarily limited to adopt the above-mentioned strategy of "Sticking to v0.6." So... I came to the forums to get an idea of what to expect, and will be returning to the drawing board shortly.
Currently, I have an iConnectAUDIO4+ bridging my iPad Pro and laptop. I'm able to get a stereo audio output from mirack into my laptop. Cool, but... I'd like to route multiple tracks of audio if possible. So... the idea someone suggested earlier (NOT going to go back into the forum to find the exact quote) of implementing instances of AU in which small patches can be loaded sounds like it would suit my workflow, as I'd be able to use AUM to host instances of mirackAU in it and use AUM to route multiple outputs into my DAW on my laptop. Or record into whatever AU compatible host DAW on my iPad.
It's unfortunate that the developer(s) responsible for making VCV Rack and its modules aren't being supportive of this port to a device which really opens up it's possibilities. I understand the hangups, but as an end-user, wish there weren't any. I had downloaded VCV Rack a long time ago, but other than open it up and nickname it "Free-aktor" I'd not embraced it as a serious tool. Then VCV Bridge (to host Rack as a VSTi) came along and made me reconsider its potential. News of mirack really appealed to me, as it seemed it would simplify crafting patches while away from the 'studio setup' and be able to open them later to record what I'd worked on. Seems that isn't the case, for now.
So anyway, I'm not going to hold my breath while wishing for VCV and mirack to be 100% cross-compatible. I'm not going to downgrade VCV on my computer, though I'm really starting to wonder if I'll NEED to use VCV Rack in the workflow I'm envisioning, as multiple instances of mirackAU hosted in AUM would do everything I thought I'd need VCV Rack/Bridge for... sans a few really interesting-looking modules.
Thanks for the port, @mifki . You have my support.
Yes, miRack is using multithreading. I don't have too much experience with AUv3 but I don't believe this alone makes it incompatible with AUv3 hosts. As I mentioned before, the real problem is that using two CPU cores doesn't leave any to other apps (apart from newer iPad pros with more cores). Multithreading can also be disabled, but then miRack will be able to support twice smaller patches. I believe a lot of you guys here (and of other music producers) use iPad Pros, so this should be less of an issue. I'm now experimenting with AB support and will let you know how it goes (however, AB has a policy that an app should work well on old devices too, this may be a problem).
Now that there are so many incredible Auv3 plugins, I rarely touch standalone apps with the exception of a few old standby's that I wish would be ported.
That said, Mirack is a unique beast that I think probably makes the most sense to exist as a standalone. I would certainly welcome it as an Auv3 if that's the way things go (mainly because it would be wonderful to build custom fx modules in AUM or apematrix..)
The main thing I hope to see is fully fledged, multi-channel audio and midi routing options. If it was easy to route audio in and out then If it is more efficient to run it as standalone, then I'd be happy to use it that way.
I know people will pipe in about the whole IAA deprecation thing, but I think it gets blown out of proportion.
You mean to/from other apps or hardware?
@mifki : I hope you won't forget about non-pro iPads that have good performance such as iPad gen 6 and more recent.
@mifki This is minor, but shouldn't be overlooked IMO. Currently, I'm running iOS 13 in Dark Mode. Opening the "Acknowledgements" menu yields black text on a dark gray background... Illegible.
Again interesting stuff. Look forward to see how the app evolves.
Yep, this will be fixed in the next update.
Absolutely. But that means I will not do anything that would cause performance to degrade on any devices. Obviously, older devices won't be able to run patches as big or run as many apps simultaneously as more powerful devices.
yes
For example, the ability to route hardware from channels 1&2 from my audio interface into a waveshaper, channel 3 to an envelope follower, etc.. route ios instruments as well, and then route the outputs to any available channels of an interface.
in the modular realm isn't it all about connectivity?
I don't mean to sound greedy. I'm happy as it is, just dreamin' :-)
Yes... Whether via an internal multi-out audio driver within the standalone app, or whether via separately instantiated AUv3 plug-ins, ultimately I hope to utilize a different mixer and effects than the modules featured within mirack/VCV.
I don't foresee myself ever building tremendous, processor-intensive patches designed to play back a full "strictly modular" arrangement (drum sequencer, synthesizers, etc.) done entirely within mirack. A bit much to expect from my processor AND to expect to be able to wrap my head around, really.
I personally prefer the approach I've learned by way of Reaktor: build "ensembles" and instantiate them as VSTi/fx within a DAW. At the end of the day, I'm hoping to be able to record what sounds I manage to get mirack to make, and continue to work with those recordings elsewhere.