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

17577798081

Comments

  • edited January 2021

    Does miRack have an All Pass Filter? Trying to build a phaser, and can't make due without one..

  • Downloaded VCV rack on my Mac. Bought some premium modules (love VULT). Now I don’t have a life anymore. What a rabbit hole. Damn.

  • edited January 2021

    @Charlesalbert said:
    Downloaded VCV rack on my Mac. Bought some premium modules (love VULT). Now I don’t have a life anymore. What a rabbit hole. Damn.

    Be sure to watch Omri Cohen's tutorials for the best creative ideas on using the newer modules VCV keeps adding (like the lovely hardware-based Instruo)

    https://www.youtube.com/channel/UCuWKHSHTHMV_nVSeNH4gYAg

  • T> @Aletheia

    saw the live yesterday on YT. Wow. I felt literally in love. Just hope to learn to be so prepared like him in a remote future.

  • This little app saved me a lot of money. I've always wondered about modular hardware - since it's all the rage - and now that I used the app, I realize that I can't stand modular.

  • edited January 2021

    @Charlesalbert said:
    T> @Aletheia

    saw the live yesterday on YT. Wow. I felt literally in love. Just hope to learn to be so prepared like him in a remote future.

    Go back in his video history to about the time when 1.0 was launched with polyphony and such and you'll understand loads. Back then he had a less complex setup and usually went module by module. You could even go earlier to check his tutorials on the Turing Machine or Clouds since those are real staples of the modular world.

  • No new updates or betas for a while... also no news from @mifki

    Anyone contacted him recently? Hope all is ok

  • edited February 2021

    There’s more activity on his forum, just read a post earlier, another GPL dispute 😬

    https://discuss.mirack.app/

  • The user and all related content has been deleted.
  • Löv the update, especially the expert sleepers calibrator, will test it tonight with es-9, hoping to calibrate v/Oct input. Fantastic update

  • OSC integration could be a very useful addition. Thanks to the developer.

  • Glad to see more updates, so much of this I haven't explored yet :)

  • Some great new modules in the update like BogAudio LPG. Also, the 32 parameters for automation, woo!

  • Hi! I am having major issues trying to sync miRack to AUM. I am getting a lot of skipping of clocks when trying to reset and clock different stuff from the different clock dividers and sequencers.

    I am trying to get a 24ppqn clock for Topograph and my hardware Grids, a bunch of different divisions for different step sequencers and a "master continuos reset" instead of a simple start at the beginning of playback, as I like building complex sequences that go back to the 1 maybe after 16, 32 or 64 steps.

    Im doing tests with this patch

    So trying to get Clocked to output my 24ppqn, a nice division to run a step sequencer at different ratios, and having a nice reset that brings everything back to the 1. But that reset is not working properly and every once in a while it either skips or seems to double trigger stuff so the sequencers keep offseting and going out of sync. Also I cannot, for the life of me, find a way to get the GridSeq to reset on the step 1, it always resets to step 2.

    If I am sending Bar output to Clocked reset input, it does sync better , but problem is that resets everything every bar, so I cannot get stuff longer than 4 or 8 steps depending on the resolution, which is a huge compromise.

    Is anyone encountering similar problems? It actually feels a bit more stable when using it standalone and using Ableton Link, but that is pretty annoying as it doesnt allow for more than one instance, and frankly, I would feel as I was underusing such an amazing tool if it cannot be used inside AUM properly. I am doing some "stress tests" by leaving a drum beat running for 15-20 minutes and every single time I get back to it, miRack has drifted from AUMs tempo :(

    Any info or help will be amazing! I am using a 6th Gen iPad running the latest OS

  • edited July 2021

    @pao I rarely use resets so not sure if I can help. But why not send a clock from Impromptu to Grids Run instead of the Run from Host? I typically use Impromptu as master clock synced from Host module and derive all other clocks from there.

    Also, is Impromptu set to use Momentary Run in right click settings?

  • wimwim
    edited July 2021

    @pao, I'm not sure what your settings are under the hood, but what I suggest is:

    • Set the host clock rate to Beat / 8 from the module menu. This will give you a more accurate clock to start with.
    • Set Clocked to use this rate by pressing the Mode + button until you see 8 in the BPM.
    • [Edit] Disconnect BPM from Clocked, and instead run clock from host module to BPM on Clocked.
    • Set Clocked to use Momentary RUN input
    • [Edit] Send Run from Clocked to Seq-B Topograph rather than from the host sync module. You'll get less variation if everything sync related is coming from one source. The host module is responsible for the master sync and reset, but everything else should come from Clocked.
    • You might consider setting Clocked to use "Reset when RUN is turned off".

    I haven't tested with your patch, but those are the steps I have taken in the past to get a good stable clock within MiRack.

  • Hi! Thanks for the rapid responses :smiley:

    Yeah, I have Clocked set to Momentary Run and Topograph is also running in momentary Run. I also use Reset when RUN is off in Impromptu, that way everything resets when it stops.

    Run isnt sending clock, right? Its just a logic signal, like a continuos gate (or maybe just a trigger that only happens when playback starts), so how would it work as a clock? Im clocking GridSequencer from Impromptu Clocked (either with different clock divisions so I get longer sequences, or straight from the main clock and a /4 to change rows).

    Again, is it possible to use Run from Clocked to clock Seq-8? I thought Run was just one tick to get things moving, not a continuos clock. I do get how having everything synced to one module would give more consistency. My main issue is that I feel that Clocked isnt working in a consistent way.

    I will test changing the clock resolution in the Host module and in Impromptu, I thought the Host clock rate only applied to its clock output, which I am not using, whereas BPM out was indepndent. Maybe this does make it work better

    Once again, thanks! Any more info will be amazing! Ill keep you updated :)

  • paopao
    edited July 2021

    edit

    If I clock Impromptu from the Host clock output, instead of BPM out, it does run in P8. Is this supposed to be more stable than the BPM out? So far seems to be working a bit more precise. Im going to leave my sequence running for some time and get back to it to see how it stands.

    (I cant still get that GridSeq to reset and do a straight 16step sequence, thats driving me nuts)

  • wimwim
    edited July 2021

    Sorry @Pao, I typed that wrong. I meant send run from Clocked to Topograph, not Seq-8.

    Oh, and don’t send BPM from the host sync module. Connect clock from the host module to BPM on Clocked instead. Sorry, I missed that. It’s been awhile.

    It should work with that fix.

  • haha no problem!

    Its been running for 28 mins with clock from the Host (instead of BPM) setting Clocked to p8 and the Host to /8 and its keeping sync great!!!

    Ooooh yeaaah this is amazing!!!! Thank you so much!

  • 👍

  • Ive just had the mooost fun and cool AUm/miRack/iPad session ive ever had! This is amazing!!! Hahaha thank you sooo much! Will post a video

  • @wim said:

    • Set the host clock rate to Beat / 8 from the module menu. This will give you a more accurate clock to start with.
    • Set Clocked to use this rate by pressing the Mode + button until you see 8 in the BPM.
    • [Edit] Disconnect BPM from Clocked, and instead run clock from host module to BPM on Clocked.
    • Set Clocked to use Momentary RUN input
    • [Edit] Send Run from Clocked to Seq-B Topograph rather than from the host sync module. You'll get less variation if everything sync related is coming from one source. The host module is responsible for the master sync and reset, but everything else should come from Clocked.
    • You might consider setting Clocked to use "Reset when RUN is turned off".

    If I set up Clocked like this, I get the number in BPM display go all wild when running and it's inconsistent.
    Weird, can't see why this mode doesn't work for me. I've double checked the steps...

  • @Carnbot So how I am using it now (and its working amazingly good, its even properly syncing stuff that was a bit funky):

    HOST set to clock rat /8
    Impromptu Clocked set to P8 (pressing the mode button)
    Impromptu set to Reset when Run stops
    Impromptu set to Momentary Run

    Start from HOST to Reset in Impromptu
    Run from HOST to Run in Impromptu
    Clock from HOST (not bpm, that was my error) to BPM in Impromptu

    I am personally using Impromptu to send a reset every 32 or 16 clocks, to send a x24 clock for Grids/Topograph, normal clock from Impropmptus main clock out (the one up right, not the three outs) and the third cdiv/mult output for a funky division or multiplication to run other sequencers. I am sending also clock and the reset from Impromptu (not the actual reset out, but the /32 or /16 clock from one of the three outs) to other clock dividers and it all works great now

  • edited July 2021

    @pao said:
    @Carnbot So how I am using it now (and its working amazingly good, its even properly syncing stuff that was a bit funky):

    HOST set to clock rat /8
    Impromptu Clocked set to P8 (pressing the mode button)
    Impromptu set to Reset when Run stops
    Impromptu set to Momentary Run

    Start from HOST to Reset in Impromptu
    Run from HOST to Run in Impromptu
    Clock from HOST (not bpm, that was my error) to BPM in Impromptu

    I am personally using Impromptu to send a reset every 32 or 16 clocks, to send a x24 clock for Grids/Topograph, normal clock from Impropmptus main clock out (the one up right, not the three outs) and the third cdiv/mult output for a funky division or multiplication to run other sequencers. I am sending also clock and the reset from Impromptu (not the actual reset out, but the /32 or /16 clock from one of the three outs) to other clock dividers and it all works great now

    It's strange that p-8 mode doesn't work for me. This is what I get wth these settings

  • ahhhh got it, it's a 2048 buffer bug.

    need to log this with the mirack Dev :)

  • edited July 2021

    I just picked up mirack yesterday and its awesome! I bought it mostly to use individual modules inside drambo (though I may also use it for larger feedback patches).

    When you modulate parameters in mirack there are two options: send audio/cv signals in via the audio inputs, or modulate the AUv3 parameters. I don't have a great feeling for the trade-offs between the two. I assume the audio/cv inputs are higher resolution? And there are only a few audio/cv inputs so with larger modules not all the available cv inputs can be mapped out.

    I'm curious what sort of logic other folks use when deciding whether to modulate via AU-param or audio. Is one more efficient processor wise? Does AUv3 param modulation work ok for some modules but not others? Things like this.

  • edited July 2021

    [I thought I was editing and instead quoted]

  • This new module Meander looks like it would be cool as a midi out source in AUM just got to figure out how to use it now !

  • So a new update for miRack, Christmas day for me!

    Meander looks a gorgeous sequencer for generative music, and looking at the description in the update log, it has been 30+ years in the making by Ken Chaffin.

Sign In or Register to comment.