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
Something like core audio modules in VCV rack to get the audio out of miRack to other devices and software over separate channels.
.> @vov said:
An audio recorder would allow for creating audio files to use in other apps.
The audio is already present at your audio outputs, just like on a real modular system
No I don’t need those. I’m talking about this one.
@mifki not sure if it has been mentioned already but since this app is not hosted please can we have ableton link start/stop. 👍
And Audiobus with state saving
(at some point without much hassle)
Came across this nice patch on YouTube.
https://youtu.be/XSrlDzLYuaE
Several people asked about future possibility of hosting AUv3 modules inside miRack.
I personally don't really like this idea because I'd prefer miRack to stay focused on Eurorack format / be seen as a Eurorack synth and not turn into a universal DAW. However if such support is done as just one of the modules, I don't see any problems with it and may even consider developing such a module myself.
Yup, I think we are all imagining it like the vst host module in vcv.
Sounds like a great idea!
Wouldn’t be more efficient for now just to port more VCV modules?
I tend to agree. After creating whatever monster patch in miRack, sooner or later I'll want to record/export my work and continue in my DAW of choice anyway. I find it quite likely to happen that adding AUv3 support will take much more time to get rock-solid than it may seem at first. Indeed AUv3 support would be great but I'd prefer if the focus would stay on modules and audio file import and export for now.
I have great respect of what @mifki has already done and I really hope that he'll continue with this kind of dedication for a while. Thank you @mifki
Every developer I know that has added AUv3 hosting has found it a nightmare that took far longer than they anticipated and has eaten up loads of time.
I would prefer that it be a separate thing myself
A au host like audio bus but the instruments set up like in rack, everything nice n neat and accessible on one page. Hoping that @Michael considers it 😎
That being said, loading mirack into Audiobus is def high on my wish list hehe
Don’t know if this is feasible but I’d pay for a separate AUv3 app (miRack Connect?) that could be loaded in AUM/Audiobus/GB/ApeMatrix/Cubasis etc. and would receive the miRack output. Rather than expecting the entire miRack app to be an AU, which seems like a daunting task and not really a good fit in a small AU window. We could then chain our plugins/fx to it and add other synth apps to the mix.
Just as iaa in Audiobus is what in talking about
I don’t think I’d ever want to load AU in MiRack but that’s just me.
IAA’s are failing more and more often and it’s a dying system. Can’t tell you how many I can’t use because of constant load failures or lack of state saving. I’d much rather use miRack in standalone, but have a separate AU app that can receive the audio and honor transport controls in AUM if that’s even possible.
+1 for audio export would be great and I agree that more modules and workflow type modifications are more important to me than ab or auv3 integration. To me its one of those apps that is a bit of an island and the priority is keeping it like it is, super fast and efficient.
I would like to see the knobs being controlled by midi and having midi learn but just because external controllers give it a more euroracky type experience imho but Im not in a hurry.
This is such an amazing accomplishment and Im still a bit surprised it has been done and done real well. Its just Awesome.
Ditto about being able to see knobs moving when they are mapped to midi CC.
I haven't found IAA to be becoming less reliable. Even once IAA goes away (which won't be soon), there will still be a place for monster standalone apps that don't make sense as AUs.
Some of the most reliable apps I use are IAA. I think the dev's decision to have this be standalone are beneficial to the app. As an AU, he absolutely would not manage the performance he is getting out of less-than-Pro iPads.
Hey, one of the beta-testers reported degraded performance after upgrading iPad Pro 11" to iPadOS. Has anyone else noticed this?
@mifki Im certainly not a power user (yet) but I didnt notice any change going from 12 to 13 with my Pro 1st gen 9.7 fwiw
Running 13.1.1 iPadOS 10.5 Pro. Haven’t noticed any degradation at all so far.
One thing, whenever I start mirack it opens Up to the files folder And wants me to select either iCloud or on my device, is there a way to default it to one or the other to avoid picking the same folder every time ?
@mifki iPad Pro 9.7 (2016) latest iPadOS 13.1.1 I haven’t had any degraded performance issues since updating that are noticeable to date.
That person (I guess he's from here too) was saying only his 11" iPad Pro is affected, so other model reports do not help sorry.
Can you record a video of this to make sure I understand what's happening? Also is it on new iPadOS or not?
Ok, here is my opinion about this topic.
Just don't go that way.
One reason:
If i good remember, miRack is internally locked to 44khz and it is resampling to device sample rate just final output - this would be first and major issue if you introduce AU hosting. Nanostudio 2 used same strategy at beginning (simply because it is standard solution used by desktop hosts), but in iOS world in combination with AU plugins this doesn't work. Many plugins implements improperly sample rate handling, they ignore sample rate set by host and they use always device sample rate. You can imagine issues which arise from this. At the end you will realize, that you need to give up and rework internal processing to adapt (in realtime - because sample rate switches between 44 and 48 on all devices with jack connector when you plug/unplug headphones ) to device sample rate.
In general - AU hosting introduces crashes, problems, and lot of work including lot of communication with plugin devs. Until you will be not sure you have months for fine tuning this feature - don't do it. There is lot of unreliable plugins and you will spend lot of precious dev time by trying to solve why "this particular plugin is not crashing my app".
Keep miRack away from AU hosting, keep it closed platform - it helps you keep it stable, efficient - and invest that time rather to adding app features and more interesting modules. Hands away from AU hosting.
Sure will after work, but ya it is iPadOS
Let some time pass. Right after the Update the os is doing still stuff in the background (See battery life)... performances can be influenced by this also i think. So ask him to wait a day and see if these degraded performance will continue