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 3.8x can now act as AUv3 host

2

Comments

  • wimwim

    I tried Rozeta XOX to do a bit of sequencing. It works as long as each step has only one note on it. Any step with overlapping notes doesn’t play at all. I get that because miRack is mono, only one note can play, but it doesn’t seem like no note should play at all.

    Maybe I’m missing something?

  • dendydendy
    edited October 2023

    Hey.. where is IAP store in miRack ? :-D i see in settings just "restore purchases" but can't find some actuall list of available purchases :)

    Edit: Ach found i i need to jump into module which is available as IAP (AUv3 module atm only) and by it from there .. i would suggest later when there will be more IAPs it would be good idea to list them in settings - i believe it will have also impact to increase of sales casue now it is a kinda hidden..

  • mifkimifki

    miRack 3.81 is now available (subject to App Store caching, etc.) fixing the reported crashes and the MIDI output issue (like the one mentioned above with Rozeta X0X). Let me know if any more plugins don't work.

    Also, it's now possible to learn notes/CCs in MIDI Trigger Input and MIDI CC Input modules when they're connected to MIDI AUs. Another small improvement here is that those modules will ignore already assigned notes/CCs when learning. Together, this makes it easy to assign outputs of MIDI Trigger Input module when it's connected to say Rozeta X0X - you just press learn on each output port while X0X is playing and it'll learn the next not yet assigned note.

  • mifkimifki

    @dendy said:
    Edit: Ach found i i need to jump into module which is available as IAP (AUv3 module atm only) and by it from there .. i would suggest later when there will be more IAPs it would be good idea to list them in settings - i believe it will have also impact to increase of sales casue now it is a kinda hidden..

    I wanted to give an option to see each of the paid modules and read their manuals before purchasing, and (re)using the module browser was the easiest solution at this point. There will be a dedicated place listing IAPs once there's more of them.

  • sevenapesevenape

    @mifki said:

    @dendy said:
    Edit: Ach found i i need to jump into module which is available as IAP (AUv3 module atm only) and by it from there .. i would suggest later when there will be more IAPs it would be good idea to list them in settings - i believe it will have also impact to increase of sales casue now it is a kinda hidden..

    I wanted to give an option to see each of the paid modules and read their manuals before purchasing, and (re)using the module browser was the easiest solution at this point. There will be a dedicated place listing IAPs once there's more of them.

    Are you planning more paid modules a bit like the premium modules in the vcv rack library?

  • wimwim

    @mifki said:
    miRack 3.81 is now available (subject to App Store caching, etc.) fixing the reported crashes and the MIDI output issue (like the one mentioned above with Rozeta X0X). Let me know if any more plugins don't work.

    Rozeta XOX works perfectly now. 👍

  • wimwim
    edited October 2023

    Hi @mifki - note configuration in the midi trigger input module isn’t saving in the standalone version. I haven’t tested in the AUv3 yet.

    [edit] it seems it’s only not saving if the input is an AU midi FX.

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • mikewbmikewb

    Love the idea of premium module IAP's. Want to keep supporting your work. BTW any plans on bringing the NYSTHI simpler tape control to mi-rack. Is it there somewhere and I am just missing it?

  • bygjohnbygjohn

    @mikewb said:
    Love the idea of premium module IAP's. Want to keep supporting your work. BTW any plans on bringing the NYSTHI simpler tape control to mi-rack. Is it there somewhere and I am just missing it?

    NYSTHI came to this forum a while back, and said there won’t be any updates to the MiRack modules as the code base has changed so much for VCV2. He also said he was close to moving away from VCV, as well. They are closed source, so unless @mifki has come to an arrangement on that, I doubt there’ll be any updates.

  • wimwim
    edited October 2023

    @d4d0ug said:
    I’m really confused. Are there any tutorials on basic use of the host modules out there?

    They just suddenly appeared. It'll be some time before tutorials show up. I hope to write up a detailed Wiki page with examples, but in the meantime this may help.

    GENERAL

    • There's a single module for all AUv3 plugin types (Instrument, Effect, Midi Effect).
    • You only need the big module if you have lots of parameters you want to control.
    • Plugins that rely on host timing (most Midi FX and anything with a synced delay, LFO, etc) need either the Clocked module or Link module for sync. It's best just to be in the habit of adding Clocked to the patches to avoid unexpected behavior.
    • You do not need to patch clock to the module. It will get the signal automatically.
    • The jacks on the module are for inputs only. Note, Gate, and Velocity from a midi controller or other module go into these. Control for AU parameters and/or midi CC's can go into here too. Each input is configurable with the configure button. Midi outputs from plugins will be covered below.

    INSTRUMENT PLUGINS

    • Patch the outputs to FX, mixer or the audio output module like you would any other sound source module.
    • Patch a sequencer Gate and V/Oct input. These jacks normally appear by default in the module. If not, configure two jacks for them. You can also add a Velocity input if applicable.
    • In the case of an external controller or midi effect, the patch will come from a Midi Input or Midi CC Input module set to the midi source.
    • To use midi output from the plugin you'll use a separate Midi Input, Midi Trigger Input, or Midi CC Input module set to receive from the plugin. See MIDI EFFECT PLUGINS below.

    AUDIO EFFECT PLUGINS

    • Audio input goes to the Input jacks, output to the output jacks ... easy!
    • Patch any modulators you like from LFO's etc. into jacks, and configure them for the parameters you want to modulate. Midi Learn is available and works about like AUM's midi learn works.
    • Remember that synced delays, etc. require the Clocked or Link module. Even if you aren't using sync, the module is likely to be expecting a sync source and may crash or not work right without it.
    • To use midi output from the plugin you'll use a separate Midi Input, Midi Trigger Input, or Midi CC Input output set to receive from the plugin. See MIDI EFFECT PLUGINS below.

    MIDI EFFECT PLUGINS
    Midi Effect plugins are a little more complex to set up.

    • Midi effects must be used in conjunction with a Midi Input, Midi Trigger Input, or Midi CC Input module to get their output to go anywhere.
    • First add the AUv3 host module and load the midi effect into it. (Note comments above about Clocked or Link module.)

    • You don't patch outputs from the midi effect plugin. You set a Midi Input, Midi Trigger Input, or Midi CC module to receive from the plugin, then the output from there to what you want to control.

      • Tap the LCD display of the module and you'll see any midi capable plugins in your patch available as sources.
      • Patch Gate, V/Oct (notes), Velocity, CC, etc. depending on what the plugin outputs to the inputs of what you want it to control.

    • Midi inputs and audio inputs to midi effects work the same way as they do for instrument plugins and audio effect plugins.

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • mifkimifki

    @wim said:
    Hi @mifki - note configuration in the midi trigger input module isn’t saving in the standalone version. I haven’t tested in the AUv3 yet.

    [edit] it seems it’s only not saving if the input is an AU midi FX.

    This is now fixed in 3.82 alongside with restored iOS 12 support.

  • wimwim
    edited October 2023

    EXAMPLE: Rozeta XOX to > @mifki said:

    @wim said:
    Hi @mifki - note configuration in the midi trigger input module isn’t saving in the standalone version. I haven’t tested in the AUv3 yet.

    [edit] it seems it’s only not saving if the input is an AU midi FX.

    This is now fixed in 3.82 alongside with restored iOS 12 support.

    It sure is! Thanks!
    It even repaired a patch I had closed last night before the fix.

    But c'mon ... nearly 12 hours to fix it?? You need to step up your game. 😉😂

  • HotStrangeHotStrange

    @wim said:

    @d4d0ug said:
    I’m really confused. Are there any tutorials on basic use of the host modules out there?

    They just suddenly appeared. It'll be some time before tutorials show up. I hope to write up a detailed Wiki page with examples, but in the meantime this may help.

    GENERAL

    • There's a single module for all AUv3 plugin types (Instrument, Effect, Midi Effect).
    • You only need the big module if you have lots of parameters you want to control.
    • Plugins that rely on host timing (most Midi FX and anything with a synced delay, LFO, etc) need either the Clocked module or Link module for sync. It's best just to be in the habit of adding Clocked to the patches to avoid unexpected behavior.
    • You do not need to patch clock to the module. It will get the signal automatically.
    • The jacks on the module are for inputs only. Note, Gate, and Velocity from a midi controller or other module go into these. Control for AU parameters and/or midi CC's can go into here too. Each input is configurable with the configure button. Midi outputs from plugins will be covered below.

    INSTRUMENT PLUGINS

    • Patch the outputs to FX, mixer or the audio output module like you would any other sound source module.
    • Patch a sequencer Gate and V/Oct input. These jacks normally appear by default in the module. If not, configure two jacks for them. You can also add a Velocity input if applicable.
    • In the case of an external controller or midi effect, the patch will come from a Midi Input or Midi CC Input module set to the midi source.
    • To use midi output from the plugin you'll use a separate Midi Input, Midi Trigger Input, or Midi CC Input module set to receive from the plugin. See MIDI EFFECT PLUGINS below.

    AUDIO EFFECT PLUGINS

    • Audio input goes to the Input jacks, output to the output jacks ... easy!
    • Patch any modulators you like from LFO's etc. into jacks, and configure them for the parameters you want to modulate. Midi Learn is available and works about like AUM's midi learn works.
    • Remember that synced delays, etc. require the Clocked or Link module. Even if you aren't using sync, the module is likely to be expecting a sync source and may crash or not work right without it.
    • To use midi output from the plugin you'll use a separate Midi Input, Midi Trigger Input, or Midi CC Input output set to receive from the plugin. See MIDI EFFECT PLUGINS below.

    MIDI EFFECT PLUGINS
    Midi Effect plugins are a little more complex to set up.

    • Midi effects must be used in conjunction with a Midi Input, Midi Trigger Input, or Midi CC Input module to get their output to go anywhere.
    • First add the AUv3 host module and load the midi effect into it. (Note comments above about Clocked or Link module.)

    • You don't patch outputs from the midi effect plugin. You set a Midi Input, Midi Trigger Input, or Midi CC module to receive from the plugin, then the output from there to what you want to control.

      • Tap the LCD display of the module and you'll see any midi capable plugins in your patch available as sources.
      • Patch Gate, V/Oct (notes), Velocity, CC, etc. depending on what the plugin outputs to the inputs of what you want it to control.

    • Midi inputs and audio inputs to midi effects work the same way as they do for instrument plugins and audio effect plugins.

    Wow thank you for this

  • hghonhghon

    @wim said:

    @d4d0ug said:
    I’m really confused. Are there any tutorials on basic use of the host modules out there?

    They just suddenly appeared. It'll be some time before tutorials show up. I hope to write up a detailed Wiki page with examples, but in the meantime this may help.

    GENERAL

    • There's a single module for all AUv3 plugin types (Instrument, Effect, Midi Effect).
    • You only need the big module if you have lots of parameters you want to control.
    • Plugins that rely on host timing (most Midi FX and anything with a synced delay, LFO, etc) need either the Clocked module or Link module for sync. It's best just to be in the habit of adding Clocked to the patches to avoid unexpected behavior.
    • You do not need to patch clock to the module. It will get the signal automatically.
    • The jacks on the module are for inputs only. Note, Gate, and Velocity from a midi controller or other module go into these. Control for AU parameters and/or midi CC's can go into here too. Each input is configurable with the configure button. Midi outputs from plugins will be covered below.

    INSTRUMENT PLUGINS

    • Patch the outputs to FX, mixer or the audio output module like you would any other sound source module.
    • Patch a sequencer Gate and V/Oct input. These jacks normally appear by default in the module. If not, configure two jacks for them. You can also add a Velocity input if applicable.
    • In the case of an external controller or midi effect, the patch will come from a Midi Input or Midi CC Input module set to the midi source.
    • To use midi output from the plugin you'll use a separate Midi Input, Midi Trigger Input, or Midi CC Input module set to receive from the plugin. See MIDI EFFECT PLUGINS below.

    AUDIO EFFECT PLUGINS

    • Audio input goes to the Input jacks, output to the output jacks ... easy!
    • Patch any modulators you like from LFO's etc. into jacks, and configure them for the parameters you want to modulate. Midi Learn is available and works about like AUM's midi learn works.
    • Remember that synced delays, etc. require the Clocked or Link module. Even if you aren't using sync, the module is likely to be expecting a sync source and may crash or not work right without it.
    • To use midi output from the plugin you'll use a separate Midi Input, Midi Trigger Input, or Midi CC Input output set to receive from the plugin. See MIDI EFFECT PLUGINS below.

    MIDI EFFECT PLUGINS
    Midi Effect plugins are a little more complex to set up.

    • Midi effects must be used in conjunction with a Midi Input, Midi Trigger Input, or Midi CC Input module to get their output to go anywhere.
    • First add the AUv3 host module and load the midi effect into it. (Note comments above about Clocked or Link module.)

    • You don't patch outputs from the midi effect plugin. You set a Midi Input, Midi Trigger Input, or Midi CC module to receive from the plugin, then the output from there to what you want to control.

      • Tap the LCD display of the module and you'll see any midi capable plugins in your patch available as sources.
      • Patch Gate, V/Oct (notes), Velocity, CC, etc. depending on what the plugin outputs to the inputs of what you want it to control.

    • Midi inputs and audio inputs to midi effects work the same way as they do for instrument plugins and audio effect plugins.

    You’re a trooper @wim great write up 👍👍

  • mifkimifki

    @wim said:
    But c'mon ... nearly 12 hours to fix it?? You need to step up your game. 😉😂

    😂 I remember the times when standard App Store review time was a week all too well. It's amazing this is even possible now.

  • wimwim
    edited October 2023

    Thanks @hghon, @HotStrange, and @d4d0ug .

    Good to know that there are still some people who are willing to read and don't just say "Thanks, but please make me a video". 😂

  • LuxthorLuxthor

    @wim said:
    Thanks @hghon, @HotStrange, and @d4d0ug .

    Good to know that there are still some people who read and don't just say "Thanks, but please make me a video". 😂

    So, there is no chance for a video at all?! 🤣

  • wimwim
    edited October 2023

    Ha! I can't even stand to watch them, much less make them.

  • LuxthorLuxthor

    So there is a chance! 🤩

  • bygjohnbygjohn

    @wim said:

    @d4d0ug said:
    I’m really confused. Are there any tutorials on basic use of the host modules out there?

    They just suddenly appeared. It'll be some time before tutorials show up. I hope to write up a detailed Wiki page with examples, but in the meantime this may help.

    GENERAL

    • There's a single module for all AUv3 plugin types (Instrument, Effect, Midi Effect).
    • You only need the big module if you have lots of parameters you want to control.
    • Plugins that rely on host timing (most Midi FX and anything with a synced delay, LFO, etc) need either the Clocked module or Link module for sync. It's best just to be in the habit of adding Clocked to the patches to avoid unexpected behavior.
    • You do not need to patch clock to the module. It will get the signal automatically.
    • The jacks on the module are for inputs only. Note, Gate, and Velocity from a midi controller or other module go into these. Control for AU parameters and/or midi CC's can go into here too. Each input is configurable with the configure button. Midi outputs from plugins will be covered below.

    INSTRUMENT PLUGINS

    • Patch the outputs to FX, mixer or the audio output module like you would any other sound source module.
    • Patch a sequencer Gate and V/Oct input. These jacks normally appear by default in the module. If not, configure two jacks for them. You can also add a Velocity input if applicable.
    • In the case of an external controller or midi effect, the patch will come from a Midi Input or Midi CC Input module set to the midi source.
    • To use midi output from the plugin you'll use a separate Midi Input, Midi Trigger Input, or Midi CC Input module set to receive from the plugin. See MIDI EFFECT PLUGINS below.

    AUDIO EFFECT PLUGINS

    • Audio input goes to the Input jacks, output to the output jacks ... easy!
    • Patch any modulators you like from LFO's etc. into jacks, and configure them for the parameters you want to modulate. Midi Learn is available and works about like AUM's midi learn works.
    • Remember that synced delays, etc. require the Clocked or Link module. Even if you aren't using sync, the module is likely to be expecting a sync source and may crash or not work right without it.
    • To use midi output from the plugin you'll use a separate Midi Input, Midi Trigger Input, or Midi CC Input output set to receive from the plugin. See MIDI EFFECT PLUGINS below.

    MIDI EFFECT PLUGINS
    Midi Effect plugins are a little more complex to set up.

    • Midi effects must be used in conjunction with a Midi Input, Midi Trigger Input, or Midi CC Input module to get their output to go anywhere.
    • First add the AUv3 host module and load the midi effect into it. (Note comments above about Clocked or Link module.)

    • You don't patch outputs from the midi effect plugin. You set a Midi Input, Midi Trigger Input, or Midi CC module to receive from the plugin, then the output from there to what you want to control.

      • Tap the LCD display of the module and you'll see any midi capable plugins in your patch available as sources.
      • Patch Gate, V/Oct (notes), Velocity, CC, etc. depending on what the plugin outputs to the inputs of what you want it to control.

    • Midi inputs and audio inputs to midi effects work the same way as they do for instrument plugins and audio effect plugins.

    Thanks, @wim, excellent write up.

  • hghonhghon

    @wim said:
    Thanks @hghon, @HotStrange, and @d4d0ug .

    Good to know that there are still some people who are willing to read and don't just say "Thanks, but please make me a video". 😂

    With you on that 👍 a well written guide coveys the information faster, and when you want to remember something from it you can scan it in seconds to get the info you need. Naturally I saved what you wrote into a note 😄

  • HotStrangeHotStrange

    @hghon said:

    @wim said:
    Thanks @hghon, @HotStrange, and @d4d0ug .

    Good to know that there are still some people who are willing to read and don't just say "Thanks, but please make me a video". 😂

    With you on that 👍 a well written guide coveys the information faster, and when you want to remember something from it you can scan it in seconds to get the info you need. Naturally I saved what you wrote into a note 😄

    That’s the best selling point for manuals and written overviews. I love a good video but sometimes it’s nice to have something to reference immediately

  • royorroyor

    @wim Very helpful write up.. your time + effort are greatly appreciated.. thanks..

  • [Deleted User][Deleted User]
    edited October 2023
    The user and all related content has been deleted.
  • wimwim
    edited October 2023

    @d4d0ug said:
    Having trouble achieving polyphony linking a sequencer auv3 midi effect to a drum machine auv3.

    There’s only one Vc/Oct input so not sure what I’m missing here. Any thoughts?

    I don't know for iOctachron, but the way I did it with Rozeta XOX is to use a Midi Trigger Input module rather than a midi input. Each of the trigger's was set to a note coming from XOX. In the target AUv3 I set up the notes that I needed to trigger. Here's how I set up XOX playing Ruismaker:

    TIP: enable velocity from the midi trigger input module menu to get velocity over to the target app.

    And here's an example to show some of those same outputs patched to the gate/trigger of miRack modules to replace the hi-hats:

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • soundsgoodbrosoundsgoodbro

    It’s great update! Thanks to mifki! Is any info about polyphony support in future updates?

  • lasselulasselu

    @mifki
    I'm having problems.
    Everything works as expected in the standalone version but in the AUv3 version (used in AUM) I can't select any AUs, the menus for selecting AUs only contain miRack...
    If I save a patch in the standalone version and open it in the AUv3 version the AUv3 module says "NOT FOUND" under the window for the AU.

    Anyone else seeing this?

    Also, randomly when I open the AUv3 version it says that I haven't purchased the AUv3 modules and I have to do it again (although the App Store sees that I already have them and asks if I want to re-download them)

Sign In or Register to comment.

© Vanilla Keystone Theme 2024