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 — now AUv3! — for Beginners

1…5678911»

Comments

  • bygjohnbygjohn

    @Gravitas said:

    @bygjohn said:

    @Gravitas said:
    Is it possible to create a Midi Thru in MiRack?
    I need to send midi notes and CC messages directly to my Volca Beats.
    Currently I can send the midi notes but not the CC messages.
    I’m using an external sequencer.

    This may turn out not to work - I’m not an expert, and I may well have got the wrong end of the stick. Wouldn’t be the first time…

    Could you patch the CCs through from a CC input module to a CC output module, alongside the Basic MIDI input and output modules?

    I looked at that and you have to assign
    the CC’s both on the inputs and outputs
    and not simply patch a midi input
    to a midi output and have the midi info
    being passed thru.

    Drat. Sorry.

  • GravitasGravitas

    @bygjohn said:

    @Gravitas said:

    @bygjohn said:

    @Gravitas said:
    Is it possible to create a Midi Thru in MiRack?
    I need to send midi notes and CC messages directly to my Volca Beats.
    Currently I can send the midi notes but not the CC messages.
    I’m using an external sequencer.

    This may turn out not to work - I’m not an expert, and I may well have got the wrong end of the stick. Wouldn’t be the first time…

    Could you patch the CCs through from a CC input module to a CC output module, alongside the Basic MIDI input and output modules?

    I looked at that and you have to assign
    the CC’s both on the inputs and outputs
    and not simply patch a midi input
    to a midi output and have the midi info
    being passed thru.

    Drat. Sorry.

    No worries.
    I was thinking that there maybe
    a way using MiRack standalone.
    I’m currently using AUM in the
    background to create a midi thru.

  • wimwim

    @Gravitas said:

    @bygjohn said:

    @Gravitas said:

    @bygjohn said:

    @Gravitas said:
    Is it possible to create a Midi Thru in MiRack?
    I need to send midi notes and CC messages directly to my Volca Beats.
    Currently I can send the midi notes but not the CC messages.
    I’m using an external sequencer.

    This may turn out not to work - I’m not an expert, and I may well have got the wrong end of the stick. Wouldn’t be the first time…

    Could you patch the CCs through from a CC input module to a CC output module, alongside the Basic MIDI input and output modules?

    I looked at that and you have to assign
    the CC’s both on the inputs and outputs
    and not simply patch a midi input
    to a midi output and have the midi info
    being passed thru.

    Drat. Sorry.

    No worries.
    I was thinking that there maybe
    a way using MiRack standalone.
    I’m currently using AUM in the
    background to create a midi thru.

    You could use MidiFire for that routing I suppose. It might be lower overhead than AUM.

  • GravitasGravitas

    @wim said:

    @Gravitas said:

    @bygjohn said:

    @Gravitas said:

    @bygjohn said:

    @Gravitas said:
    Is it possible to create a Midi Thru in MiRack?
    I need to send midi notes and CC messages directly to my Volca Beats.
    Currently I can send the midi notes but not the CC messages.
    I’m using an external sequencer.

    This may turn out not to work - I’m not an expert, and I may well have got the wrong end of the stick. Wouldn’t be the first time…

    Could you patch the CCs through from a CC input module to a CC output module, alongside the Basic MIDI input and output modules?

    I looked at that and you have to assign
    the CC’s both on the inputs and outputs
    and not simply patch a midi input
    to a midi output and have the midi info
    being passed thru.

    Drat. Sorry.

    No worries.
    I was thinking that there maybe
    a way using MiRack standalone.
    I’m currently using AUM in the
    background to create a midi thru.

    You could use MidiFire for that routing I suppose. It might be lower overhead than AUM.

    I don’t have Midifire.
    I’ll host it in either
    dRambo or AUM for now.

    Thanks for the suggestion.

  • catherdercatherder

    I notice that whenever I start miRack standalone, the transport is always running immediately. Is there a way to disable this and let miRack wait for me to press "start" ?

  • wimwim
    edited February 8

    @catherder said:
    I notice that whenever I start miRack standalone, the transport is always running immediately. Is there a way to disable this and let miRack wait for me to press "start" ?

    The transport in miRack (if you're talking about the play button in the app header) is more than a transport control, it affects UI elements and even knob behavior. Lots of things won't work if that's paused.

    Normally there's a clock module with a run button in patches. The run state will be saved with the project, so a patch can be opened in a non running "transport" state if saved with run off.

  • catherdercatherder

    @wim said:

    @catherder said:
    I notice that whenever I start miRack standalone, the transport is always running immediately. Is there a way to disable this and let miRack wait for me to press "start" ?

    The transport in miRack (if you're talking about the play button in the app header) is more than a transport control, it affects UI elements and even knob behavior. Lots of things won't work if that's paused.

    Normally there's a clock module with a run button in patches. The run state will be saved with the project, so a patch can be opened in a non running "transport" state if saved with run off.

    @wim thanks for help. That makes sense.

  • mifkimifki

    Yeah I realise that Play/Pause button in the toolbar may be confused, and will be even more so once I add proper transport controls to the toolbar (which would mean two play/pause buttons - one for transport, one for engine). I will maybe end up moving the engine pause button to a submenu, but I'm interested in suggestions on this.

  • wimwim

    @mifki said:
    Yeah I realise that Play/Pause button in the toolbar may be confused, and will be even more so once I add proper transport controls to the toolbar (which would mean two play/pause buttons - one for transport, one for engine). I will maybe end up moving the engine pause button to a submenu, but I'm interested in suggestions on this.

    Change it to a power button?

  • mifkimifki

    @wim said:

    @mifki said:
    Yeah I realise that Play/Pause button in the toolbar may be confused, and will be even more so once I add proper transport controls to the toolbar (which would mean two play/pause buttons - one for transport, one for engine). I will maybe end up moving the engine pause button to a submenu, but I'm interested in suggestions on this.

    Change it to a power button?

    Oh I must admit I haven't thought of this myself. That should do it!

  • hghonhghon

    Hi @mifki any updates on that controller surface module?

  • GravitasGravitas

    @mifki

    There seems to be a problem with MiRack recognising midi ports at the moment.
    I'm using the current AppStore version.

    I have a patch that sends midi clock out which I've been using in dRambo and AUM.

    It used to work up until recently and now instead of selecting
    the "Crave" midi out to sync the Crave sequencer
    I have to use the LaunchPad X midi port to sync the "Crave".

    It still works as midi auv3 when selecting Host App in AUM
    however using the Host App midi port doesn't work in dRambo or Cubasis 3.

Sign In or Register to comment.

© Vanilla Keystone Theme 2024