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
I think that's the clever thing. If you drag out in any direction you get the vertical or horizontal scale which you can then slide along to change the value in a comfortable space.
That's a difficult question. Technically it's not a problem, but I don't really like the situation when some modules support polyphony and some don't, and I don't want to release a "polyphony update" and adding (*terms and conditions apply, may not be available in all modules). So I want to investigate other possibilities, for example, automatic instantiation of additional copies of any module when needed. It won't be as efficient as modules specifically optimised for polyphony, but again only some of them are. If nothing else, then custom module builder feature that I mentioned here before, will also help, you'll be able to either create a poly module containing multiple mono modules inside, or a single mono module with multiple modules inside which will be easier to reuse and duplicate.
This, and the fact that mono synths do exist and aren't something bad, are the reasons it's not high priority (yet).
Literal edge cases I guess... probably would be tricky to get right?
Thanks for the detailed answer. It seems like a reasonable idea.
I remember an old module capable of sending MPE instructions to mono modules in vcv rack. Too long ago to remember the name. That was before vcv going polyphonic.
My favorite implementation of knob UI is in Thor (Propellerhead). It's vertical-only, which to me reduces confusion, and there's a line that pops up and shows the value as you move the knob around.
That said, I think it would be brilliant to let the user select between vertical-only, horizontal-only, etc. modes in the global settings.
Just realized somebody else posted the exact same video I was going to post.
This feels like an historic moment, omg all channels work, in and out. This is the best way to do euro on iPad, nothing like it.
MiRack 3.50 is out 🎇🎉
What’s New Version 3.50
== APP FEATURES ==
MIDI out works via CoreMIDI, Audiobus and AUv3. For AUv3, a dedicated MIDI Processor AU type is also available.
In particular, Expert Sleepers ES-8/9 audio interfaces and expanders are now fully supported, and allow to integrate miRack and hardware Eurorack equipment.
Added SHIFT toolbar button to access secondary function of certain module controls. It's used in number of new Bidoo modules, in Squinky Labs mixer to solo multiple channels, and other places in the future.
Improved rendering of lights and some module controls.
== MODULES ==
Expert Sleepers encoders for use with ES-5, ES-40, ESX-8GT and ESX-8CV Eurorack modules.
Added bId°° (Bidoo) module pack. It's a great collection of modules with weird names by Sébastien Bouffier, including several powerful sequencers - perfect for use with the new MIDI out functionality.
Valley module pack updated to the latest version. New module Feline - stereo version of a filter section from Interzone module.
Added an option to Host Sync module menu to change clock output rate (instead of a fixed BEAT output). This can also be used for connection to Clocked module for more reliable timing. Set CLOCK output to Beat / 4 or Beat / 8, connect to BPM input of Clocked, and set Clocked mode to P4 or P8 accordingly.
Fixed an issue with Frozen Wasteland Quad Algorithmic Rhythm module, it's now working properly.
For MIDI keyboards that do not support per-note aftertouch but support channel pressure, it will be used for AFT output of MIDI module.
This could have been 4.0! What an epic update!
This app is so freekin' amazing it makes my head spin. Thank you @mifki !!!
Well... It was nice knowing you, outdoors.
😂😂
ha!
First time I’ve almost wished lockdown would be permanent.
i feel very bad because i paid just ridiculous 10€ for this app... i want pay for this update :-)
A tip jar is definitely in order.
I also try to contribute to the module developers when I can. They’re partners in this in every way as well.
MiRack was epic at v1, these updates are outstanding.
Such a great app. Each update seems to make this app so much more useful. Like Novation Circuit the popularity of this app is by having a great product and then just making it like 10 better with well thought out and user driven updates. Well done
Thanks for all the good feedback
Off to the App Store for a glowing review!
the best getting better
TBH, MiRack and VCV has been a massive educational tool for me, specifically pertaining to whether or not to buy into Eurorack. I plan to get a semi modular (Neutron or a second hand SV1) in October to begin flirting with modular and to pair with the cv outs on my Mono Station and Keystep.
However, while vcv has more hardware-clone units (for now) that I can test before I buy (Mutable Instruments / Grayscale / EricaSynths) I really wish to get away from behind my laptop. MiRack offers this hella-freedom on iPad.
Now that MiRack has midi out, and it's gonna get better, I may just get the Neutron/SV1 and not bother with the rest of modular. Or, most likely, hold off for a much more discrete and educated purchase of Eurorack modules.
All this to say... Muchas gracias @mifki . Keep up the good work, can't wait for more (hardware clones) modules.
HUGE update ! Thank you @mifki
Thanks for this brilliant update! I don’t even know what to wish more
@mifki this is just amazing. High praise to you.
Pandora’s box has been opened!
I’ve sat on the fence snce it was first released, brought but left it waiting for this specific update, now its time to finally dive into MiRack!
I think this is finally going to push me into starting to explore this app! Can't wait, should be a real eye opener. @mifki big kudos
mifki said: "poly module containing multiple mono modules inside"
I've been studying and experimenting with constructing virtual "voice card synths" using a sort of a "poly module" methodology, by utilizing the Layer mixer Module of Drambo. However, Drambo is not particularly accommodating to being used this way.
You got my attention when you mentioned the possibility of a poly module for miRack.... Based on my Drambo experience, I think the "poly module" might be an optimal initial solution for adding comprehensive poly capabilities to miRack.
The following is my view of how an "optimized" poly module could work....
A poly module is essentially a "round robin" controlled, "voice layer" container, that allows the user to create a number of separate "voice racks". One voice rack per each layer, and each voice rack represents one polyphonic voice. The user has the ability to choose the number of voice layers that the poly module will contain, and the number of voice layers determines the number of polyphonic voices that can be played at the same time.
I personally don't see any reasons why a poly module couldn't function well within an overall monophonic host, provided the following capabilities are incorporated into the design....
A basic poly module "should" require external "meta controls", that can be assigned to simultaneous controlling of the parameters of multiple identical modules on each voice rack layer in the poly module. This feature enables the user to control all same-type parameters of multiple voices, from a single controller. Meta controls eliminate the need for the user to open each voice rack and make independent adjustments to multiple modules in each voice rack.
Although, an aspect of creativity only achievable with the use of a poly module, is being able to vary each voice rack in various ways, so each polyphonic voice can produce a different sound character (color).
This is a video of a simple 3-voice layer module I made using Drambo, the only variation between voices here, are the filter settings.
Far more complex poly synths can be created by placing completely different module configurations in each voice rack (layer).
Another requirement for a basic poly module, is providing a method to apply external ADSR control that responds polyphonically. This could be by use of a meta controller that controls each ADSR and Amp on the voice rack level. Or (preferred) it could be in the form of an external module specifically designed to apply poly ADSR control to the output of the poly module.
Audio volume from a poly module increases as the number of simultaneously played voices increases, a methodology of accommodating for this effect could be built into a poly module.
I like the idea that a poly module could have both a single (mixed) audio output, but also individual audio outputs from each voice rack. Individual outputs could allow the user to further process voice output monophonically in different ways, before mixing to a final output, or other creative use.
Edit:
I also like your idea of a copy feature for populating additional poly module racks.
A user could basically start by creating a single-voice poly module. Then use a "duplicate rack to new voice" feature, to add additional voices by copying the modules to each new voice rack.
In miRack, it's simple enough to connect up sequencer and clock modules, then connect up 3 or more oscillators, then hook them up with VCAs, filters, etc. to get a sequencing polyphonic synth.
There's also a Quad MIDI input module which can be used for building a 4-voice polyphonic synth for playing from your MIDI controller.
I can see the appeal of the equivalent of a quad VCO or something like that for easier patching of a polysynth, though, because right now, for, say, a 4-voice polysynth, you need to hook up 4 oscillators, 4 envelope modules, 4 filters, etc. - at least 12 modules.
OTOH, more voices than that, I start thinking I'll just go fire up OB-Xd, D1, or other dedicated polysynth app, because it starts to be more trouble than its worth.
I haven't yet worked much with miRack... because it isn't polyphonic.
The concept of a "poly module containing multiple mono modules inside", is familiar to me because of my experiments using the layer mixer in Drambo.
The image that came to mind when @mifki mentioned a poly module. Was a module that could be opened and closed...
When closed it would be a module on the regular miRack rack. But when opened.. I'm envisioning a full screen rack where a synth can be constructed. Adding each additional voice provides a new empty rack. One rack per voice.
After the poly module is filled with voice racks, it can be closed, and takes up no more space that a regular rack. All the interior modules become hidden from view.
A closed poly module would need some method to link meta controls for controlling the internal modules. That could be accomplished in a number of ways.
For me.... A polyphonic miRack would become something I'd be much more interested in investing time in to learn and explore.
I own lots and lots of Apps. When Drambo released it was the first App I really spent a lot of time exploring. If Drambo had been monophonic, it wouldn't have held my attention.
I primarily play polyphonic keyboard improvisationally. So mono synths although cool, don't inspire me in the same way that a modular polysynth will.