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.

MOZAIC - Create your own AU MIDI plugins - OUT NOW!

17677798182108

Comments

  • Does anyone know if the @OnTimer events occur asynchronously with the @OnMidi* events, i.e. could both potentially be fired at the same time or are they guaranteed to be fired serially?

  • @MisplacedDevelopment All Mozaic Events are fired separately and don‘t interrupt each other

  • @_ki said:
    @MisplacedDevelopment All Mozaic Events are fired separately and don‘t interrupt each other

    Thanks, I was hoping that was the case!

  • Novation LaunchKey MKIII is a great controller but sadly the pad functionality is reduced when not connected with Ableton Live.
    The 16 pads work in two modes: Drum and Custom
    Drum is not configurable, it transmits CC from 36 to 51 on channel 10, only one color.
    Custom is configurable through the Components software by connecting it to the mac / pc and you can configure note and color per key but global channel (from 1 to 16). Nothing else.
    When connected to the iPad, the Launchkey is displayed as two units: Launchkey MIDI and Launchkey DAW. It transmits and receives on both ports.
    In Drum, by sending cc from 36 to 51 to channel 10 of the controller from any software on the Launchkey DAW port, it is possible to turn on or off the lights of the pads and through velocity you can change color.
    Is it possible through Mozaic to make each pad become an on / off button with light on / off?
    In practice, at every pressure sent by LaunchKey in Drum mode on channel 10 of the Launchkey MIDI port, Mozaic should respond alternately by sending the same note on channel 10 but on the LaunchKey DAW port (or at least I think).
    Perhaps there is an easier way and you don't even need Mosaic but my brain is... clouding.

  • wimwim
    edited November 2020

    @Tatobx said:
    Novation LaunchKey MKIII is a great controller but sadly the pad functionality is reduced when not connected with Ableton Live.
    The 16 pads work in two modes: Drum and Custom
    Drum is not configurable, it transmits CC from 36 to 51 on channel 10, only one color.

    I think you mean notes, not CC's.

    Custom is configurable through the Components software by connecting it to the mac / pc and you can configure note and color per key but global channel (from 1 to 16). Nothing else.
    When connected to the iPad, the Launchkey is displayed as two units: Launchkey MIDI and Launchkey DAW. It transmits and receives on both ports.
    In Drum, by sending cc from 36 to 51 to channel 10 of the controller from any software on the Launchkey DAW port, it is possible to turn on or off the lights of the pads and through velocity you can change color.
    Is it possible through Mozaic to make each pad become an on / off button with light on / off?
    In practice, at every pressure sent by LaunchKey in Drum mode on channel 10 of the Launchkey MIDI port, Mozaic should respond alternately by sending the same note on channel 10 but on the LaunchKey DAW port (or at least I think).
    Perhaps there is an easier way and you don't even need Mosaic but my brain is... clouding.

    Yes, and it's fairly easy. You route the Launchkey directly to the app you're playing. In parallel, you route it to Mozaic. Mozaic's output should be routed to the Launchkey DAW port (if indeed that's the port you need to send to).

    The LaunchKey is going to send a note-on/note-off combination every time a pad is pressed. The first note-on received means it's "on", the next means it's "off". The Mozaic script just needs to keep track of whether the "switch" should be on or off and send the appropriate commands to the Launchkey.

    Controlling the LEDs is a bit more complicated than just sending note on/note off. I'm looking at the documentation now and putting together a short "untested" script as an example. I should have it fairly soon.

  • wimwim
    edited November 2020

    Here's a "theoretical" script. I don't have a device to test it on.

    @Description
      Toggle Launchkey pad lights on and off.
      Example only: NOT tested.
      Route Launchkey in parallel to the app to be played and to this script.
      Route this script to the "Launchkey DAW" port (I think).
    @End
    
    @OnLoad
    
      // You can set the pad colors individually in the arrays below.
      // Colors can be found in the Launchkey MK3 Programmers Reference Manual
      // 21 is a shade of green. 0 is black. 
    
      oncolor[36] = [21,21,21,21,21,21,21,21,21,21,21,21,21,21,21,21]
      offcolor[36] = [0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]
    
      // You can also set color behavior by midi channel below
      // Stationary color = midi channel 10 (mozaic 9)
      // Flashing = midi channel 11 (mozaic 10)
      // Pulsing = midi channel 12 (mozaic 11)
      colorchannel[36] = [9,9,9,9,9,9,9,9,9,9,9,9,9,9,9,9]
    
      ResetNoteStates FALSE
    @End
    
    @OnMidiNoteOn
    
      // Check to be sure notes received are from the pads
      // This will need enhancement if custom channels or notes are used.
      if MIDIChannel = 9 and MIDINote >= 36 and MIDINote <= 51
    
        // Toggle the note state between TRUE and FALSE
        SetNoteState MIDIChannel,MIDINote,(not GetNoteState MIDIChannel,MIDINote)
    
        if GetNoteState MIDIChannel,MIDINote = TRUE
          SendMIDINoteOn colorchannel[MIDINote], MIDINote, oncolor[MIDINote]
        else
          SendMIDINoteOn colorchannel[MIDINote], MIDINote, offcolor[MIDINote]
        endif
      endif
    
    @End
    
  • @wim said:
    Here's a "theoretical" script. I don't have a device to test it on.

    ```

    Wow, thanks @wim for your work
    the script work only on OFF command
    the pads remain in the color I set in the OFF state
    I tried to understand the logic of the script and changed some parameters but the result I get leads me to a permanent OFF or ON state

  • wimwim
    edited November 2020

    @Tatobx said:

    @wim said:
    Here's a "theoretical" script. I don't have a device to test it on.

    ```

    Wow, thanks @wim for your work
    the script work only on OFF command
    the pads remain in the color I set in the OFF state
    I tried to understand the logic of the script and changed some parameters but the result I get leads me to a permanent OFF or ON state

    oops.

    Please try changing

    if GetNoteState MIDIChannel,MIDINote = TRUE
    

    To

    if (GetNoteState MIDIChannel,MIDINote) = TRUE
    
  • @wim said:
    oops.

    Please try changing

    Ohhh Great!!! Now it works perfectly :)
    This script will be useful to many people because at the moment there is no other solution to configure the LEDs and being able to do it directly from the iPad is priceless.
    Now my first row of pads is flashing if I arm the track recording. Crazy!!!
    Thank you so much

  • @Tatobx said:

    @wim said:
    oops.

    Please try changing

    Ohhh Great!!! Now it works perfectly :)
    This script will be useful to many people because at the moment there is no other solution to configure the LEDs and being able to do it directly from the iPad is priceless.
    Now my first row of pads is flashing if I arm the track recording. Crazy!!!
    Thank you so much

    Sweet! I didn't really expect it to work without a device to test on.

    Did you find the programmer's reference so that you can look up the numbers for the colors?

  • @wim said:

    Sweet! I didn't really expect it to work without a device to test on.

    Did you find the programmer's reference so that you can look up the numbers for the colors?

    Yes, I found it and I also saw that potentially other things could be done but for the moment that's fine

  • @McD, @_ki, @brambos

    So I finaly finished my MultiChannelProgramChanger script. When I started making this script it was to be part of the ControlChain.

    https://forum.audiob.us/discussion/35373/controlchain-for-mozaic

    It had to wait for longer arrays. Then some mistakes with saving old versions over newly updated code made me put it aside for a while...
    Since this program change table holds so many records it was important to allow exchange of all the data with newer versions of the script.
    Now that this function works reliably it is save to invest your time in finding the best patch combinations for all your synths.

    Working with the ControlChain I found the need to selectivly disable some messages in the midi stream, like notes or midi clock.

    So here is MidiCensor.

    Download at patchstorage

  • @Alfred said:
    It had to wait for longer arrays.

    What? Arrays beyond 1024? Was there an update? I have touched Mosaic in months.
    I might make something I have envisioned because I really need something to work on since
    I've bought everything I'll never need.

  • Yes, it was quiet a while by now. I got confused with all the labeling code.
    Since all problems are solved now you can finaly play with it.
    You seemed a little upset that I kept my program changer for myself.

  • @McD said:

    @Alfred said:
    It had to wait for longer arrays.

    What? Arrays beyond 1024? Was there an update? I have touched Mosaic in months.
    I might make something I have envisioned because I really need something to work on since
    I've bought everything I'll never need.

    Maximum cells for arrays is still 1024.

  • Sorry guys, just noticed I botched the upload. Now you can download the MultiChannelProgramChanger. A year late, but here it is anyways.

  • @brambos: are there such a thing as multiout midi plugins?

  • @espiegel123 said:
    @brambos: are there such a thing as multiout midi plugins?

    You can use MIDI channels for this I would guess?

  • edited December 2020

    @Krupa said:

    @espiegel123 said:
    @brambos: are there such a thing as multiout midi plugins?

    You can use MIDI channels for this I would guess?

    Kinda. In some cases, there are complicating factors that make using midi channels messy (though doable) in some cases and a more elegant solution would be to be able to direct the output through different wires to simplify downstream setup.

  • @espiegel123 said:
    @brambos: are there such a thing as multiout midi plugins?

    Fugue Machine is multi-midi out.

  • In AUM MIDI Generator/controller to MIDI consumer Instruments/Recorder (AUv3/IAA apps)
    are "point-to-point" associations and not BUS'es. And any source can be configured with point-to-point connections to multiple targets. So, the bus concepts are not limiting for MIDI
    links. One those point to point links you will still get the MIDI "bus" of 16 channels" and MPE traffic.

    Now, the better question for me are the design limits for MIDI in other prominent DAW's.
    Can a single Mozaic instance be applied to 3-4 instruments in these DAW's easily or are you
    forced to run with one-to-one instances of MIDI FX to Instrument?

  • Actually I also wanted this already, I use MIDI channels but they can be limiting and messy sometimes. In my case, I'd like to have 16 channels mapped 1:1 to tracks in AUM plus one channel controlling LEDs on MIDI controller. This way I need to sacrifice one AUM channel, which is not a big deal, but would be more straightforward if it has a separate MIDI output.

  • wimwim
    edited December 2020

    @McD said:
    Now, the better question for me are the design limits for MIDI in other prominent DAW's.
    Can a single Mozaic instance be applied to 3-4 instruments in these DAW's easily or are you
    forced to run with one-to-one instances of MIDI FX to Instrument?

    There's no one answer to that. Each DAW has different implementations. All are hamstrung in many ways. None have as much flexibility as AUM, Ape Matrix, and Audiobus.

  • I’m still hoping that amazing Mozaic sale that just passed will bring a new wave of code ideas, and ultimately scripts on Patchstorage. It Might take a little time, but I have to imagine a slew of new people purchased the app. So hopefully there will be more Mozaic codes being created and thought up. As if 190 of them wasn’t enough... lol. I truly love Mozaic.

  • @brambos: any chance of a Mozaic companion plugin that is just for putting together custom u.i.s but has no scripting? Such an app maybe also has options as to how it’s widgets respond to incoming MIDI so that Mozaic scripts can puppet string them? I’d love to be able to build an all on the same screen collection of dials, buttons and sliders that can control the various controls of all the various synths and effects in frequently used setups.

  • edited December 2020

    @wim said:

    @_ki said:
    @wim Cool idea 👍🏼 and sorry i forgot about the Hypno Sequence. It also was missing on the Mozaic script list on the wiki, so i just added it.

    Thanks for adding it.

    Do you prefer we update the list ourselves when we post a script, or to maintain the page yourself? Either way is fine with me. B)

    Just want to say.. Big thanks for the Simple Scaler script..

    Nice..

  • I spent a lot of yesterday evening playing around with Seq8 and a Launchpad Mini & absolutely loved it! Oddly, though, when I use other MIDI generators (including other instances of Mozaic) it resulted in strange timing anomolies where it would play a bar through once and then would play cell 1 and 2 of the bar the second time around before starting the bar again. It produces a crazy syncopated rhythm that's a time signature I can't begin to fathom. Anyone have any ideas why that might be the case? The only changes I made to the script was changing the note values to correspond to Ruismaker.

  • I'd like to make a script, but it's my first attempt and after 20 minutes with the manual and some frustration, I can't find out how to do this thing. I could spend more time, but my motivation to do music - at all - is low at the moment so I'd rather not spend a lot of time learning this right now, if at all possible.

    Maybe there's already something on patchstorage, but I'm finding it hard to find.

    So... I'd like to have one button on a hardware controller mapped to CC20 that will send a value of 0 when pressed the first time, 1 the second time, 2 the third time etc. So increasing by 1 each time.

    The reason for this is that Digistix has thankfully added the ability to select patterns by midi control. But it's specifically a CC20 value per pattern, and what I'd like is an 'advance to next pattern' control, so that there's only one button to hit in a live performance.

    Probably it would be good to add a decrease button too, but if I could see the script for the increase version, hopefully I could work that out myself.

    Anyone know of such a script, or at least something similar that I could attempt to wrestle into shape?

    thank you!

  • wimwim
    edited December 2020

    @SimonSomeone said:
    I'd like to make a script, but it's my first attempt and after 20 minutes with the manual and some frustration, I can't find out how to do this thing. I could spend more time, but my motivation to do music - at all - is low at the moment so I'd rather not spend a lot of time learning this right now, if at all possible.

    Maybe there's already something on patchstorage, but I'm finding it hard to find.

    So... I'd like to have one button on a hardware controller mapped to CC20 that will send a value of 0 when pressed the first time, 1 the second time, 2 the third time etc. So increasing by 1 each time.

    The reason for this is that Digistix has thankfully added the ability to select patterns by midi control. But it's specifically a CC20 value per pattern, and what I'd like is an 'advance to next pattern' control, so that there's only one button to hit in a live performance.

    Probably it would be good to add a decrease button too, but if I could see the script for the increase version, hopefully I could work that out myself.

    Anyone know of such a script, or at least something similar that I could attempt to wrestle into shape?

    thank you!

    What is the highest number you’d want it to increase to? And would you want it to start over at zero when it goes past that number? Also, what would be coming from the button on the controller? Some buttons send a note or CC at 127 when pressed down and zero when released. Can you be more specific about what will be coming from this button.

    I have a sample script ready to go except for those details. Actually, I really only need details about what would be coming from the hardware controller. The rest is easily customizable in the script already.

Sign In or Register to comment.