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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

miRack by mifki Limited - Live!!!

1697072747582

Comments

  • edited August 2020

    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

  • edited August 2020

    @mifki said:

    @despego said:
    By the way. Is polyphony on the roadmap? MPE?

    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).

    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.

  • edited August 2020

    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.

  • edited August 2020

    @GovernorSilver said:
    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.

    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.

  • edited August 2020

    @horsetrainer said:

    @GovernorSilver said:
    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.

    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...

    No, he didn't. Somebody else did. I think you just caught his reply to that other person.

    BTW, what you are describing sounds a lot like the Metamodule feature in Sunvox, yet another modular app.

    Honestly, if you're only interested in polysynths, there's no need to look at miRack. There are so many excellent polysynth apps to choose from already.

  • @GovernorSilver

    This is the post I was referencing (7th post down from top of page 71 of this thread).

    (bolding mine)

    @mifki said:

    @despego said:
    By the way. Is polyphony on the roadmap? MPE?

    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).

  • edited August 2020

    @horsetrainer said:
    @GovernorSilver

    This is the post I was referencing (7th post down from top of page 71 of this thread).

    (bolding mine)

    @mifki said:

    @despego said:
    By the way. Is polyphony on the roadmap? MPE?

    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).

    Ah, but that was in response to this post - all I'm saying is the dev is not the person who brought polyphony into the conversation:
    https://forum.audiob.us/discussion/comment/837924/#Comment_837924

    I saw a similar thing in an app called Skrum. Maybe others can confirm.

    Wondering too why it didn’t catch on other apps.

    By the way. Is polyphony on the roadmap? MPE?

  • Great update, this app is a now a major force, look forward to exploring the sequencers with midi out. :)

  • This is not me, but here's somebody's test of miRack to real Eurorack integration, using Expert Sleepers module(s). Not the most exciting demo musically but does demonstrate functionality

  • this update is great. are there any module that can change the pitch of the midi note going out of miRack to other apps? i’d love to modulate that

  • That video is @bobbfett He posted earlier. Pure magic.

  • @eross said:
    this update is great. are there any module that can change the pitch of the midi note going out of miRack to other apps? i’d love to modulate that

    I’m sure there are better ways but here’s one way to create a big one-finger chord (assuming you like C and G, other notes can be interesting). It uses the Submarine SS-212 for the third and fifth and the Submarine SS-221 for the lower octave.



  • @Carnbot said:
    Great update, this app is a now a major force, look forward to exploring the sequencers with midi out. :)

    Topograph and µGraph are very handy with midi out. Here shown driving Ruismaker:

    And with Music Thing Turing machine driving Bassalicious 2 for a bass line:

  • @xor said:

    @eross said:
    this update is great. are there any module that can change the pitch of the midi note going out of miRack to other apps? i’d love to modulate that

    I’m sure there are better ways but here’s one way to create a big one-finger chord (assuming you like C and G, other notes can be interesting). It uses the Submarine SS-212 for the third and fifth and the Submarine SS-221 for the lower octave.



    agh very cool. does seem like a lot of stuff to setup, but i’ll give it a whirl. thanks for the screenshots. that helps alot

  • Thanks @wim will check those out :)

  • Amazing! Thank you @mifki ! :smiley:

  • I know I shouldn't be surprised that we can pass CV between instances of miRack, since it's just virtual voltages, like audio.

    And yet it's still quite surprising.

    With multiple ins and outs this could get very weird (note to self: try this in apeMatrix). Not sure of the utility, except perhaps that you could break complex patches into separate components and still have access to CV that can vary from static to audio rate. MIDI out is a fantastic addition, but you can't get audio-rate modulation happening the way.

    Oh, and using GlitchCore to cut up CV is weird, possibly pointless, but fun....

    @mifki One minor request: both AUM and apeMatrix list multiple ins and outs as stereo pairs rather than individual channels. Would it be possible to have an alternate skin for the input and output modules that lists channels as 1-8 left and right pairs rather then 16 discrete channels? Really minor, but there's that second of cognitive dissonance when trying to do complex routings.

  • So, as I mentioned on Twitter, I've found a way to make miRack work in macOS DAWs that don't support v3 Audio Units (Ableton, FL Studio, etc.). Still 10.15+ only though. Anyone wants to test?

  • @mifki said:
    So, as I mentioned on Twitter, I've found a way to make miRack work in macOS DAWs that don't support v3 Audio Units (Ableton, FL Studio, etc.). Still 10.15+ only though. Anyone wants to test?

    I'd love to test on 10.14 ... sorry.

  • @mifki said:
    So, as I mentioned on Twitter, I've found a way to make miRack work in macOS DAWs that don't support v3 Audio Units (Ableton, FL Studio, etc.). Still 10.15+ only though. Anyone wants to test?

    Yes please

  • @mifki said:
    So, as I mentioned on Twitter, I've found a way to make miRack work in macOS DAWs that don't support v3 Audio Units (Ableton, FL Studio, etc.). Still 10.15+ only though. Anyone wants to test?

    Definitely. I have FL Studio, Live Lite, and GarageBand which aren’t working with MiRack currently.

  • edited August 2020

    GarageBand should already work.

    Anyway, here's a package - http://assets.mifki.com/mirack/miRackLegacyAU-0.92.pkg You should have miRack installed from the Mac App Store (confirm that it's showing in a DAW even if it can't be loaded), then install this package and there will be miRack Legacy and miRack FX Legacy AUs.

  • Another imo good implementation of fine control is iVCS3 (apesoft).
    Similar to miRacks current approach, but instead of a global 2way switch it has a continuous slider per knob which is handy for different applications like cutoff freq vs OSC freq

  • Wow, midi out!
    Does anyone know if it can be used with CV.OCD?

  • @mifki said:
    GarageBand should already work.

    Anyway, here's a package - http://assets.mifki.com/mirack/miRackLegacyAU-0.90.pkg You should have miRack installed from the Mac App Store (confirm that it's showing in a DAW even if it can't be loaded), then install this package and there will be miRack Legacy and miRack FX Legacy AUs.

    I tried it in Ableton 10.1 on MacOS 11.0 and besides the fact that you cannot resize the app window like the AUv3 it works fine !! Thank you !

  • Great idea re: virtual CV @aplourde. Need to try that.

  • @Philippe said:
    Wow, midi out!
    Does anyone know if it can be used with CV.OCD?

    Why not!!???

  • wimwim
    edited August 2020

    @mifki said:
    GarageBand should already work.

    Anyway, here's a package - http://assets.mifki.com/mirack/miRackLegacyAU-0.92.pkg You should have miRack installed from the Mac App Store (confirm that it's showing in a DAW even if it can't be loaded), then install this package and there will be miRack Legacy and miRack FX Legacy AUs.

    GarageBand wasn't working for me with the previous versions. If I deleted the app and reinstalled, it would work once, but not on subsequent GarageBand loads. Tested many times over.

    But! This new build is working perfectly in Live Lite 10, FL Studio, and GarageBand! This is outstanding. B)

    Multi-Out isn't working, but I expected that. That would be pretty cool to have though. FL Studio handles multi-out plugins this nicely in its mixer. I haven't tested miRack as an FX yet. Off to do that now and will report if I find any problems.

    Window resize would be nice if it can be done too, but not really a problem if not.

    [edit - all good with the FX plugin too. 👍🏼]

  • edited September 2020

    An improvisation featuring Marbles set to Raag Shri. Made sure to record it in the evening - supposedly that’s the ideal time to use this raag. Marbles is generating all the rhythm and pitch signals Plaits is used to play the base rhythm and pitches. Another Plaits is used to play the multiples of the base rhythm. A Rings is used to play divisions of the rhythm (I think).

    For some reason I had to manually tune Rings via the Frequency knob, because it seemed to like playing a whole step up from the two Plaits modules.

    @mifki question for you - The physical Marbles module has alternative operations that are activated by holding the buttons labeled E, N, O and J on the online manual, on the Mutable Instruments website. Is there support for this functionality in miRack? Somebody asked me about these button hold functions after he said he tried them.

Sign In or Register to comment.