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
Keeping a close eye on this :-)
Once it gets
AU/AB
Set of starter presets (for learners)
CPU meter
Manual
It’s going to fly !
For me just about the only thing it needs now is a built-in audio recorder and maybe at some point a module to capture the audio input. I'm having a blast with it
Then for now audio loop back is your friend ;-)
What are the 3 icons for ( top right) any ideas ? ;-)
@mifki
Since there’s no way to change buffer size I assume it’s fixed.
Can you tell what the buffer size is? Also if you have any info about the round trip latency (midi in - audio out) when no external audio interface used at various sample rates (44.1, 48)?
Love the ‘elastic’ timing of seqs can be built, any chance of a midi out module in the future?
Thanks!
Audio buffer size will be configurable in the next version. I'm hoping to do some measurements as well if I have time.
MIDI out has been requested by some users and will happen eventually but is not a high priority at the moment.
Yeah, time has been such a premium lately.
I appreciate your willingness to address this. My idea of downgrading my version of VCV to 0.6.2c was due to my experience of having attempted to send a mirack patch to my laptop and it not loading properly into VCV version 1.x. Some of the modules I'd used in mirack weren't available. I'd put it down to them having been updated in newer versions of VCV (Specifically, Audible Instruments... the Mutable clones) were the modules I'd deduced were not cross compatible.
I'll give transferring from iPad to MacBook another try, see what works or doesn't work. The fact that you're willing to address this issue is HUGE. Thank you very much for that.
Anyone ;-)
1) The multiple-arrow icon needs to be selected in order to move modules. (With it off, you move knobs/values instead.)
2) The crosshairs-looking icon is for precision adjustment. (Turn it on and move a knob. You now have finer control over it than with it off.)
3) The arrow pointing at a zero, from what I can tell, is used to reset knobs/values to their "zero" or default value.
This is what I've put together in a matter of trial and error just now in a matter of asking myself the very question you'd put forth.
You can still move modules without having the multiple-arrow icon selected by touching a blank space on the module. I wish not having the icon selected would just move knobs and cables. @mifki is this a bug?
I just re-downloaded and did a clean-installation of VCV Rack v1.1.5 before sending a mirack patch via iCloud to my laptop to test. Opened the package that had been sent over, double-clicked on the 'patch.vcv' file inside it... got a series of messages that I was missing modules... went to the VCV home page, added what modules I was able to... confirmed that modules which have not been updated for use in VCV 1.x are not downloadable. On the bright side, it was only ONE of the modules I'd used in the patch (developer: 8mode) that would not load.
However, when I attempted to route audio, all I got was crackle. I decided to attempt via VCV Bridge into Ableton Live, and still, crackle, only here I could see a CPU meter. Spiking and reporting upwards of 600% of my processor being used. Closing VCV took it back down to 3%. Reopened VCV, futzed with some of its settings (Low CPU mode, etc.) and still... nothing but crackle.
Opened the patch again on my iPad and concluded: "Looks like I'd be better off hosting patches on my iPad than attempting to host them within Ableton Live on my aging laptop."
To be SURE that the issue was with VCV overloading my laptop's CPU, I created a new patch. (Hardly.) Took an instance of the Braids clone and plugged it's output directly into the audio device, routed it to the VCV Bridge, and... JUST ONE OSCILLATOR, droning, without ANY modulation or knob movements, apparently was too much to ask from my computer. Closed every other app but Live and VCV, and even then, it was still suffering of glitching. Unfortunate, that. I had no idea (because I'd yet to create a patch in VCV Rack) as to how CPU-intensive the program is. Reminded me of when I'd first tried running Reaktor 5 ensembles on a laptop back in 2006 and ended up eventually upgrading to an 8-core MacPro tower, which sadly, is no longer in my studio to test on.
Anyway. Wanted to report that most of the modules I'd used ARE, in fact, cross-compatible. This is good, though my computer appears to be incapable of handling what I've asked it to process.
And so... I'm casting a vote in favor of multiple audio outputs from mirack, which I'll pipe into Live via my iConnectAUDIO4+
Cheers )
Very nice overview thanks.
I think it may be loading wrong audio parameters and that may be causing these issues. I’ll do some testing and fix it if that’s the case. miRack still uses the same original vcv file format so there’s no reason not to support export to it as not much additional work is required.
For what it's worth, I had just done a clean installation of VCV Rack, and hadn't made any adjustments to my audio driver settings other than to select it, and then later select the option to route to the VST Bridge (MIDI, did not try the "fx" or audio) plugin.
I'm not certain these issues are being caused by loading of audio parameters saved in the mirack file, as I did a test with a single oscillator in a freshly-created 'new file' initiated on my laptop, to test CPU usage. It remained relatively low, but was still subject to crackling. I didn't make an effort to change settings of my audio device, as audio from other sources in Live wasn't problematic. Anyhow... if your tests yield an issue of the sort you suspect, and you are able to fix it... Great!
Indeed, once I "show packet contents" of the mirack-exported file, a file named patch.vcv shows up. I could see these files being accidentally overwritten or mistaken for other patches. It would be an improvement to have a .vcv file that preserves the filename of the mirack export.
Thanks again. I'm looking forward to diving into Fernando Soler Fernández's VCV tutorial series on YouTube, to learn more about both the featured modules and how to create patches... be it in mirack and/or VCV Rack.
Ok, I've identified several issues around vcv 1.0 compatibility, they'll require some work which I'll do probably after recording, AB, all that more often requested stuff.
In VCV RACK turn off cpu usage indication. I find that this will introduce “crackling” no matter how small the patch is on my iMac.
I am loving this. I just need some templates like real basic. I could not connect the virtual keyboard to anything and it was total user error. Basic drum and basic synth with a micro hint at which cables can go where.... I get it tho ideally start from scratch to learn....
Basic synth ;-)
https://filebin.net/pwkmsxsmltlnxeqy/Basic_Synth_1.zip?t=0i4ipgtr
I mean turn it off to stop the “crackling”!!
A public statement on the hostile actions of Wes Milholen (Grayscale) towards miRack project
Wow, so surreal... Sorry, you have to put up with that gaslighting behaviour.
I just can't help but wonder why he got involved in an open source project if he's so closed off to the spirit of sharing that is inherent to it. Your point that Mirack will bring attention (and sales) to VCV is true. I am a VCV user and value both. Since Mirack was released, I've purchased several VCV modules. it's clear that they each have their strengths.
I'd be shocked if there were mirack users who weren't aware that this is a fork of VCV. Nobody is under the illusion that it is one person's invention. So sad when egos get in the way of the bigger picture..
What is ultimately baffling to me is that there was a massive shrug at creating a version for ios from the VCV developer. Then when it happens (properly and legally) and proves to be a success, they're making a stink about it.
If it hurts them so much, why didn't they do it themselves? Tbh, the idea that Mirack is going to hurt VCV is absurd.
@medium, is the only way to comment by authenticating via Google or Facebook?
Anyway, the only similarity I can recognize is the functionality, not the visual appearance.
As the discussion seems to be between developers with totally different viewpoints, a good (moderated) talk to Wes might help.
People can have all kinds of matters to cope with and in this case, it's most likely not about graphics, layouts and visual identities. They are all completely different and the only similarity, i.e. functionality, is obviously derived from the function, not from the design.
If Wes could protect a button, a knob, a switch and a connector as his own intellectual property then he certainly would but one thing is obvious: With the same arguments he's enumerated when criticizing your work, the inventors of the knob, the button, the switch and the connector could criticize him for stealing their intellectual property.
And no, Wes did not invent them!
Maybe he's just p*issed that he wasn't asked in the first place?
And in the case of miRack, it's about money?
From the medium post:
I don't agree at all. The similarity of visual identity is that of a modular synthesizer, not a similarity between Wes' and your core modules.
Again, this is clearly not the case. You've obviously spent a lot of time developing your own visual identity using very different UI widgets that only resemble functionality, not design.
Why?
This is exactly what you did.
There have been many similar disputes in history (See Apple's trademark violations from both other companies and Apple themselves) but when design similarities had to be identified, in most cases the judges have tried to find rational reasons for evaluating something rather irrational like the user experience.
But I cannot see a single explanation why Wes thinks that you have stolen his work.
And again, the visual identity is the one of a modular system, not something specific that Wes has invented. Wes could attack hardware synth module developers based on the same reasoning.
Wes' criticism seems like he's trying to construct a case of violation of the CC BY-NC license and the Fundamental CC BY-NC-ND license for a completely different reason than what he says.
Hopefully Apple isn't like YouTube, which defaults to simply taking things down and puts the onus on the content creator to prove that the complaint is unjust.
Or like my State tax board which just sends you a demand for payment and then makes it almost impossible to prove they're wrong. (No joke. They even admitted they made a mistake in my case and that of about 500,000 others a few years ago. Yet, they still made every one pay up or submit every last bit of proof.)
I guess vcv rack thinks they own all os based euro rack rights lol absurdity.
Mirack is an iOS version of a Modular synth, based on an open source project , what’s the problem?
That dude is just being toxic to his own community. If anything Mirack will surely promote VCVrack in some form or another. Anyway if it's only the fundamental plugins, there are better modules out there.
To clarify, "open source" does not mean anyone can use the source for anything. There are different types of open-source licenses.
@mifki seems conscientiously to be living up to the the licensing and to be working hard to avoid any ambiguity.
But don't be under the false impression that you can do anything you want with any open source source you find. Many open-source projects either restrict commercial use or require any derivatives be fully open source.
I mention that because many people don't realize this.
The community around VCVRack is obviously very cooperative and constructive, it just seems that one individual is about stating an exception.
Whatever his motivation is, yes, this will get him nowhere for sure.
Certainly!
And nothing stops @mifki from giving back to the community by releasing e.g. a future audio recorder and player as an open source module for VCV Rack.