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.

Quantum from midiSequencer dev is available now!!!

1192022242530

Comments

  • @TimothyClyde said:

    @midiSequencer said:

    @TimothyClyde said:
    Another problem (I think) I have found in the logic of the reverse step sequence.
    With 2 equal length tracks, when the master (fwd) triggers the reverse track, the reverse track skips to step 1 instead of step 16. This results in step 1 being triggered twice and the reverse track then runs one step behind.

    Anyone confirm?

    Yep - msg'd you - but the sync interferes with the reverse loop - will fix that.
    Can't see an issue with your chord velocity too - so send me some more details pls.

    1 Setup a default rack
    2 Activate synth (I just tried animoog and sunriser)
    3 Set one step to chord
    4 Select Vel
    5 Pull all steps to zero vel
    6 Play

    The step with the Chord still plays at full volume

    Switch to Mixer
    Need to go to 0% to affect the volume of chord step

    Hope that helps
    TimC

    Ok see what you mean.
    In MidiSequencer, chord velocity used to be relative - I changed it in Quantum to absolute because you'd end up with too small a range if it was step velocity x chord velocity. Same for gate%.

    The more I think about it the more this should go back to MidiSequencer way : 0..50..100% and each chord added note be a simple multiplier of the step velocity.

    I will make a small change though - gate % in midiSequencer was 0..200..400% - so will make it a simpler 0..50..100% like velocity.

    This way all chord notes are relative to the step note (length & velocity).
    I put this in for the next patch.

  • @bleep said:

    @midiSequencer said:
    Yep - msg'd you - but the sync interferes with the reverse loop - will fix that.

    I have also earlier reported problems with reverse loops and parts. Perhaps you are able to fix that in the same go?

    Create 1 seq with parts A and B, both run on steps 1-4 (transpose B to hear a difference). Set play mode to ">", one part after the other. If A is set to play in reverse, then you hear the problem after the first loop; A gets stuck on its end step.

    yep its on my list to be fixed for next update.
    Keep posting & I will keep fixing!

  • edited October 2017

    @Carnbot said:
    @midiSequencer Not sure if this has been discussed but is there a way to use Quantum with say a BCR2000 and have it update the rotary lights with the fader positions?

    also is this possible when using BCR in AB3 midi?
    I've been trying to setup the BCR as input and output but can't seem to get it to update the rotary lights currently. :)

    I actually have a BCR2000 so reading the manual now. Parameter feedback looks like the area but not sure if its only the faders on the BCF2000 ...

  • @midiSequencer said:

    @Carnbot said:
    @midiSequencer Not sure if this has been discussed but is there a way to use Quantum with say a BCR2000 and have it update the rotary lights with the fader positions?

    also is this possible when using BCR in AB3 midi?
    I've been trying to setup the BCR as input and output but can't seem to get it to update the rotary lights currently. :)

    I actually have a BCR2000 so reading the manual now. Parameter feedback looks like the area but not sure if its only the faders on the BCF2000 ...

    Yes I think it's referred to as parameter feedback. I think Model 15 and Animoog has this enabled, need to check if they are still working with the BCR2000.

  • @Dchild said:
    @midiSequencer thanks for the detailed response. Still can't get my head around NRPN? Can you explain how I might go about setting up mutes in the BSP editor?

    I couldn't work out how to set up the BSP (or BS) to send the NRPNs Quantum needs either. Googling about, it looks like it may be a limitation in the way Arturia has this set up. Tony, if you could double check Arturia's MIDI Control Center to make sure we're not just missing something, that would be awesome.

  • Looking at the screenshot again, I wonder if this should work for the simpler NRPNs. I admit this is just nerdy curiosity at this point. CCs + Learn work plenty well for me. :)

    First some additional NRPN info Tony sent me a while back.

    • NRPN (non-registered parameter number) is a two byte (14 bit) extensions to midi CC's (which are single byte - 7bits).
    • They are in fact three or four CC's (99 & 98, 06 & 38), but the 38 is optional.
    • 99 & 98 form the MSB (top 7 bits) and LSB(bottom 7 bits) of the control. So 99 0 98 1 is control 1; 99 1 99 2 is control 129.
    • 06 & 38 are the two byte (14 bits again) data values. 06 the top 7bits (MSB) & 38 the lower 7 bits (LSB).
    • 38 is optional, in which case 06 (7 bits) are used for values 0..127 only.
    • The data (06 or 38) can be processed without a control (99/98) in which it applies to the last control.

    So, now I'm wondering for something like:
    0,1,c PlayControls where c is 0=stop, 1=play, 2=pause, 3=reset. All other values ignore.

    In MMC, if you set a knob to LSB to 0 and MSB to 1, when you turn the knob will it send values 0-127 on CC6?

    But, even it the BS does send the value as CC6, there's apparently no facility to do stuff like:
    0,16,c,d Main Screen faders - where c = fader 1..fader 16. d=value 0..127 because there's no place it could also send a discreet value for CC38. There would need to be a place to set a fixed value for CC6 and then the knob might send a variable value for CC38.

    That said, the last line in the quote above has me wondering if there are other ways to do it:

    The data (06 or 38) can be processed without a control (99/98) in which it applies to the last control.

    Like, set one knob to set the target (99/98[MSB/LSB]) and the other knobs can just send regular CC6 for value. And another knob for CC38 when required.

    @midiSequencer, am I interpreting that last line correctly? Can you sort of prime-the-pump with 99/98 alone and the send 6 and/or 38 separately?

  • @syrupcore said:
    Looking at the screenshot again, I wonder if this should work for the simpler NRPNs. I admit this is just nerdy curiosity at this point. CCs + Learn work plenty well for me. :)

    First some additional NRPN info Tony sent me a while back.

    • NRPN (non-registered parameter number) is a two byte (14 bit) extensions to midi CC's (which are single byte - 7bits).
    • They are in fact three or four CC's (99 & 98, 06 & 38), but the 38 is optional.
    • 99 & 98 form the MSB (top 7 bits) and LSB(bottom 7 bits) of the control. So 99 0 98 1 is control 1; 99 1 99 2 is control 129.
    • 06 & 38 are the two byte (14 bits again) data values. 06 the top 7bits (MSB) & 38 the lower 7 bits (LSB).
    • 38 is optional, in which case 06 (7 bits) are used for values 0..127 only.
    • The data (06 or 38) can be processed without a control (99/98) in which it applies to the last control.

    So, now I'm wondering for something like:
    0,1,c PlayControls where c is 0=stop, 1=play, 2=pause, 3=reset. All other values ignore.

    In MMC, if you set a knob to LSB to 0 and MSB to 1, when you turn the knob will it send values 0-127 on CC6?

    But, even it the BS does send the value as CC6, there's apparently no facility to do stuff like:
    0,16,c,d Main Screen faders - where c = fader 1..fader 16. d=value 0..127 because there's no place it could also send a discreet value for CC38. There would need to be a place to set a fixed value for CC6 and then the knob might send a variable value for CC38.

    That said, the last line in the quote above has me wondering if there are other ways to do it:

    The data (06 or 38) can be processed without a control (99/98) in which it applies to the last control.

    Like, set one knob to set the target (99/98[MSB/LSB]) and the other knobs can just send regular CC6 for value. And another knob for CC38 when required.

    @midiSequencer, am I interpreting that last line correctly? Can you sort of prime-the-pump with 99/98 alone and the send 6 and/or 38 separately?

    you dudes are so hardcore

  • edited October 2017

    @Littlewoodg said:

    @syrupcore said:
    Looking at the screenshot again, I wonder if this should work for the simpler NRPNs. I admit this is just nerdy curiosity at this point. CCs + Learn work plenty well for me. :)

    First some additional NRPN info Tony sent me a while back.

    • NRPN (non-registered parameter number) is a two byte (14 bit) extensions to midi CC's (which are single byte - 7bits).
    • They are in fact three or four CC's (99 & 98, 06 & 38), but the 38 is optional.
    • 99 & 98 form the MSB (top 7 bits) and LSB(bottom 7 bits) of the control. So 99 0 98 1 is control 1; 99 1 99 2 is control 129.
    • 06 & 38 are the two byte (14 bits again) data values. 06 the top 7bits (MSB) & 38 the lower 7 bits (LSB).
    • 38 is optional, in which case 06 (7 bits) are used for values 0..127 only.
    • The data (06 or 38) can be processed without a control (99/98) in which it applies to the last control.

    So, now I'm wondering for something like:
    0,1,c PlayControls where c is 0=stop, 1=play, 2=pause, 3=reset. All other values ignore.

    In MMC, if you set a knob to LSB to 0 and MSB to 1, when you turn the knob will it send values 0-127 on CC6?

    But, even it the BS does send the value as CC6, there's apparently no facility to do stuff like:
    0,16,c,d Main Screen faders - where c = fader 1..fader 16. d=value 0..127 because there's no place it could also send a discreet value for CC38. There would need to be a place to set a fixed value for CC6 and then the knob might send a variable value for CC38.

    That said, the last line in the quote above has me wondering if there are other ways to do it:

    The data (06 or 38) can be processed without a control (99/98) in which it applies to the last control.

    Like, set one knob to set the target (99/98[MSB/LSB]) and the other knobs can just send regular CC6 for value. And another knob for CC38 when required.

    @midiSequencer, am I interpreting that last line correctly? Can you sort of prime-the-pump with 99/98 alone and the send 6 and/or 38 separately?

    you dudes are so hardcore

    They sure are. I am so intrigued with just ‘Linking two racks’ now after two weeks and I’m now wondering, what more can this amazing app do? Wow.

    My God.. :o

  • new racks should come into being empty and stopped yeah?

  • @wellingtonCres said:
    new racks should come into being empty and stopped yeah?

    Not empty IMO, but that is subjective.
    Under “Setup” you can un-check “Autoplay new racks if song playing”

    Works for me. I wouldn’t like it your way.

  • @RajahP said:

    you dudes are so hardcore

    They sure are. I am so intrigued with just ‘Linking two racks’ now after two weeks and I’m now wondering, what more can this amazing app do? Wow.

    My God.. :o

    you can try 3 or more! Automate to add some randomness - try the different song modes too - some switch play on selection...

  • @wellingtonCres said:
    new racks should come into being empty and stopped yeah?

    @midiSequencer said:

    @RajahP said:

    you dudes are so hardcore

    They sure are. I am so intrigued with just ‘Linking two racks’ now after two weeks and I’m now wondering, what more can this amazing app do? Wow.

    My God.. :o

    you can try 3 or more! Automate to add some randomness - try the different song modes too - some switch play on selection...

    Automate, as in having the faders automated?

  • @RajahP said:

    @wellingtonCres said:
    new racks should come into being empty and stopped yeah?

    @midiSequencer said:

    @RajahP said:

    you dudes are so hardcore

    They sure are. I am so intrigued with just ‘Linking two racks’ now after two weeks and I’m now wondering, what more can this amazing app do? Wow.

    My God.. :o

    you can try 3 or more! Automate to add some randomness - try the different song modes too - some switch play on selection...

    Automate, as in having the faders automated?

    Question seconded.

  • @lukesleepwalker said:

    @RajahP said:

    @wellingtonCres said:
    new racks should come into being empty and stopped yeah?

    @midiSequencer said:

    @RajahP said:

    you dudes are so hardcore

    They sure are. I am so intrigued with just ‘Linking two racks’ now after two weeks and I’m now wondering, what more can this amazing app do? Wow.

    My God.. :o

    you can try 3 or more! Automate to add some randomness - try the different song modes too - some switch play on selection...

    Automate, as in having the faders automated?

    Question seconded.

    Think he's referring to follow actions.

  • @syrupcore said:

    @lukesleepwalker said:

    @RajahP said:

    @wellingtonCres said:
    new racks should come into being empty and stopped yeah?

    @midiSequencer said:

    @RajahP said:

    you dudes are so hardcore

    They sure are. I am so intrigued with just ‘Linking two racks’ now after two weeks and I’m now wondering, what more can this amazing app do? Wow.

    My God.. :o

    you can try 3 or more! Automate to add some randomness - try the different song modes too - some switch play on selection...

    Automate, as in having the faders automated?

    Question seconded.

    Think he's referring to follow actions.

    In song mode?

  • @Carnbot said:

    @midiSequencer said:

    @Carnbot said:
    @midiSequencer Not sure if this has been discussed but is there a way to use Quantum with say a BCR2000 and have it update the rotary lights with the fader positions?

    also is this possible when using BCR in AB3 midi?
    I've been trying to setup the BCR as input and output but can't seem to get it to update the rotary lights currently. :)

    I actually have a BCR2000 so reading the manual now. Parameter feedback looks like the area but not sure if its only the faders on the BCF2000 ...

    Yes I think it's referred to as parameter feedback. I think Model 15 and Animoog has this enabled, need to check if they are still working with the BCR2000.

    Yeah have been checking Animoog and Model 15 tonight with BCR2000 and they both work with parameter feedback so at least it's possible :)

    Not sure how they did it though of course...

  • edited October 2017

    @RajahP said:

    you can try 3 or more! Automate to add some randomness - try the different song modes too - some switch play on selection...

    Automate, as in having the faders automated?

    You can easily automate the faders - just midi learn them. Enable Learn/Out (main page or mixer) and have your motorised faders move when you move them on Quantum & v.v. It even allows you to swap scenes on your hardware controller.

  • edited October 2017

    Just implemented an Elektron feature much requested in Quantum - skip step every nth loop.
    I've extended this to allow you to mute or skip.
    So with n=2 (as in pic) the step 3 is skipped every 2nd loop (=every other loop).
    You can dial in n from 1(=every loop) to 20 - and use All or Sel to set individual, all or selected steps.
    A loop is counted for every pass of end (or start if in reverse).
    This is also per part (so each part can also count loops & have different skip/mute settings)....

    Let me know if this is correct (I don't have any Elektron gear)!

  • edited October 2017

    @midiSequencer said:
    Just implemented an Elektron feature much requested in Quantum - skip step every nth loop.
    I've extended this to allow you to mute or skip.
    So with n=2 (as in pic) the step 3 is skipped every 2nd loop (=every other loop).
    You can dial in n from 1(=every loop) to 20 - and use All or Sel to set individual, all or selected steps.
    A loop is counted for every pass of end (or start if in reverse).
    This is also per part (so each part can also count loops & have different skip/mute settings)....

    Let me know if this is correct (I don't have any Elektron gear)!

    Oh this is nice. One thing I miss about the Digitakt I used to own were conditional triggers (e.g., play a step every 4th bar; play the step 30% of the time; etc). Can't wait to try this out and dive into the sequencer more as well. I tried the sequencer for a day but then got sidetracked and didn't get to go deep into it.

  • @ipadthai said:

    Oh this is nice. One thing I miss about the Digitakt I used to won were conditional triggers (e.g., play a step every 4th bar; play the step 30% of the time; etc). Can't wait to try this out.

    I'm doing just loops - do bars make any sense? Don't have the hardware to check... and the manual is confusing!

  • edited October 2017

    The Elektrons do it by loop as well. Bars make less sense when you can have variable length patterns next to each other.

    This is a reallllly awesome feature addition. Thank you!

  • edited October 2017

    @midiSequencer said:

    @ipadthai said:

    Oh this is nice. One thing I miss about the Digitakt I used to won were conditional triggers (e.g., play a step every 4th bar; play the step 30% of the time; etc). Can't wait to try this out.

    I'm doing just loops - do bars make any sense? Don't have the hardware to check... and the manual is confusing!

    Loop is fine I assume. By default a bar in Digitakt is 16 steps, with a max of 4 bars. Im happy with any conditional/probability stuff you add.

  • @ipadthai said:

    @midiSequencer said:

    @ipadthai said:

    Oh this is nice. One thing I miss about the Digitakt I used to won were conditional triggers (e.g., play a step every 4th bar; play the step 30% of the time; etc). Can't wait to try this out.

    I'm doing just loops - do bars make any sense? Don't have the hardware to check... and the manual is confusing!

    Loop is fine I assume. By default a bar in Digitakt is 16 steps, with a max of 4 bars. Im happy with any conditional/probability stuff you add.

    Yeah, it's the same. Q defaults to 16 steps with a max of 64 (or 4 bars). If you put a 2/1 trig condition on step 1 of track in an Elektron box with the track length set to 8 steps, you'll here it every 16 steps. Or every 14 steps with the track set to 7 steps. Or 30 steps if the track is set to 15 steps...

  • @midiSequencer said:
    Just implemented an Elektron feature much requested in Quantum - skip step every nth loop.
    I've extended this to allow you to mute or skip.
    So with n=2 (as in pic) the step 3 is skipped every 2nd loop (=every other loop).
    You can dial in n from 1(=every loop) to 20 - and use All or Sel to set individual, all or selected steps.
    A loop is counted for every pass of end (or start if in reverse).
    This is also per part (so each part can also count loops & have different skip/mute settings)....

    Let me know if this is correct (I don't have any Elektron gear)!

    This looks great!
    Actually Elektron is working the other way around: instead of skipping or muting a step every n loop, Elektron’s conditional triggering allow you to play a step once every n loops. I would expect this feature to be implemented in the probability parameter of the step: you could add a possibility to play the step from 0 to 100% like now and add a 1 to n loops.
    For instance 1 to 4 loops would allow you to add a drum fill at the end of a 64 steps bar

  • edited October 2017

    I found this video which explains Elektron’s conditional trigs :
    The manual is already difficult to understand when you have the hardware !

  • edited October 2017

    @Sygma said:

    This looks great!
    Actually Elektron is working the other way around: instead of skipping or muting a step every n loop, Elektron’s conditional triggering allow you to play a step once every n loops. I would expect this feature to be implemented in the probability parameter of the step: you could add a possibility to play the step from 0 to 100% like now and add a 1 to n loops.
    For instance 1 to 4 loops would allow you to add a drum fill at the end of a 64 steps bar

    I've just added that too - so you have these trigger conditions (where n is on a rotary):
    Off - ignore
    Play - play step only on the nth loop, skip otherwise
    Skip - skip step only on the nth loop, play otherwise
    Mute - mute step only on the nth loop, sound otherwise

    I can see this opening up later to offer more options... Feel free to enlighten me!

  • @midiSequencer said:

    @Sygma said:

    This looks great!
    Actually Elektron is working the other way around: instead of skipping or muting a step every n loop, Elektron’s conditional triggering allow you to play a step once every n loops. I would expect this feature to be implemented in the probability parameter of the step: you could add a possibility to play the step from 0 to 100% like now and add a 1 to n loops.
    For instance 1 to 4 loops would allow you to add a drum fill at the end of a 64 steps bar

    I've just added that too - so you have these trigger conditions (where n is on a rotary):
    Off - ignore
    Play - play step only on the nth loop, skip otherwise
    Skip - skip step only on the nth loop, play otherwise
    Mute - mute step only on the nth loop, sound otherwise

    I can see this opening up later to offer more options... Feel free to enlighten me!

    Absolutely brilliant Tony, thank you so much. This is a game changer for me

  • @midiSequencer said:

    I've just added that too - so you have these trigger conditions (where n is on a rotary):
    Off - ignore
    Play - play step only on the nth loop, skip otherwise
    Skip - skip step only on the nth loop, play otherwise
    Mute - mute step only on the nth loop, sound otherwise

    I can see this opening up later to offer more options... Feel free to enlighten me!

    Maybe Play- play Step only on the nth loop, mute otherwise.

    The "skip otherwise" option above causes the rhythm to go out of sync doesn't it? Because you're skipping over a step and playing the next step instead. I would more often want the step to stay there as a rhythmic place keeper but control whether it plays or is muted.

  • @yowza said:

    Maybe Play- play Step only on the nth loop, mute otherwise.

    The "skip otherwise" option above causes the rhythm to go out of sync doesn't it? Because you're skipping over a step and playing the next step instead. I would more often want the step to stay there as a rhythmic place keeper but control whether it plays or is muted.

    Not one to remove options - you now have these trigger conditions (where n is on a rotary):
    Off - ignore
    PlayMute - play step only on the nth loop, mute otherwise
    PlaySkip - play step only on the nth loop, skip otherwise
    Skip - skip step only on the nth loop, play otherwise
    Mute - mute step only on the nth loop, sound otherwise

    so nth means 1st, then nth, then n2th, then n3 etc.
    E.g. PlayMute n=3 would play on the 1st loop, mute on the 2nd & 3rd, play on the 4th loop etc.
    Mute n=3 would mute on 1st, nth, n*2th etc
    But in all cases the trigger occurs in the 1st loop.

    The PlaySkip & Skip alter the rhythm (create for variation) whilst the others just have mutes.

    Again I can extend these easily...

  • Tony - I've been teaching music for a number of years and I always talked about how math is music and music is math. This app has reminded me of this in the best ways as I had forgotten that lesson for myself. Thanks again - this thing is incredible. And I'm just making 80's funk grooves over here...

Sign In or Register to comment.