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

12426282930

Comments

  • @RJB said:

    @midiSequencer said:

    @RJB said:
    Have you made up some tasty demo files so we can de-construct this beast?

    you looking for something in particular?

    How about examples to go along with the Sessions in the manual, especially Session 4 and 5.

    sure - transposing sequences & automation using actions.

  • edited November 2017

    Apple must love reviewing my app - 2.5 hours from submission to approval (20mins of that in review).

    Should be filtering through to iTunes soon....

  • @midiSequencer said:

    sure - transposing sequences & automation using actions.

    Great, and any of your demo songs that have lots going on, like probably all of them. :D

  • @RJB said:

    @midiSequencer said:

    sure - transposing sequences & automation using actions.

    Great, and any of your demo songs that have lots going on, like probably all of them. :D

    a lot were created on midiSequencer, but yes I aim to do more audio sessions - its why I created Quantum :)

  • @midiSequencer a video showing how you construct some of the complex sessions would be lovely. Specially building something looking closer to a song :)
    Not a tutorial per se but just a video of you messing about and making something. Doesn't even need text explanation. Just raw video :)

  • edited November 2017

    @gonekrazy3000 said:
    @midiSequencer a video showing how you construct some of the complex sessions would be lovely. Specially building something looking closer to a song :)
    Not a tutorial per se but just a video of you messing about and making something. Doesn't even need text explanation. Just raw video :)

    I'm liking the rhythms generated using the new trigger conditions, so my next audio session video will feature those (have a few on the go) . I dearly want to start on groove templates & patterns as I'm now needing to build up bigger song structures so its less through-composed/noodled.

  • @midiSequencer said:

    @gonekrazy3000 said:
    @midiSequencer a video showing how you construct some of the complex sessions would be lovely. Specially building something looking closer to a song :)
    Not a tutorial per se but just a video of you messing about and making something. Doesn't even need text explanation. Just raw video :)

    I'm liking the rhythms generated using the new trigger conditions, so my next audio session video will feature those (have a few on the go) . I dearly want to start on groove templates & patterns as I'm now needing to build up bigger song structures so its less through-composed/noodled.

    This is exactly why I wanted the Trigger conditions so much : new version of Midisequencer is now perfect for me ! I am just waiting for the new UI now :)

  • @Sygma said:

    This is exactly why I wanted the Trigger conditions so much : new version of Midisequencer is now perfect for me ! I am just waiting for the new UI now :)

    saving the UI for my long xmas holidays - easier at the moment for me to pull new functionality out of the hat.

  • @gonekrazy3000 said:
    @midiSequencer a video showing how you construct some of the complex sessions would be lovely. Specially building something looking closer to a song :)
    Not a tutorial per se but just a video of you messing about and making something. Doesn't even need text explanation. Just raw video :)

    Agreed... :smiley:

    I love Animoog's demo track Momentum by Sascha Dikiciyan, and recall him saying he sequenced using the dead Phaedra... I just kept thinking "I wanna learn how to do that with MidiSequencer" (today with Quantum too lol)
    My results are too experimental as of now :dizzy:

  • @senhorlampada said:

    @gonekrazy3000 said:
    @midiSequencer a video showing how you construct some of the complex sessions would be lovely. Specially building something looking closer to a song :)
    Not a tutorial per se but just a video of you messing about and making something. Doesn't even need text explanation. Just raw video :)

    Agreed... :smiley:

    I love Animoog's demo track Momentum by Sascha Dikiciyan, and recall him saying he sequenced using the dead Phaedra... I just kept thinking "I wanna learn how to do that with MidiSequencer" (today with Quantum too lol)
    My results are too experimental as of now :dizzy:

    great track - very professional - but a lot done outside of IOS. I will see if I can get you the sequenced parts though..

  • @midiSequencer said:

    great track - very professional - but a lot done outside of IOS. I will see if I can get you the sequenced parts though..

    lol... i know... :smiley: But it's the sequence that matters :heart: :lol:


  • A midi fx tutorial (first test-version) ...

  • @ccs2 said:
    A midi fx tutorial (first test-version) ...

    interesting - what are you showing here - lots going on?

  • @midiSequencer said:

    @ccs2 said:
    A midi fx tutorial (first test-version) ...

    interesting - what are you showing here - lots going on?

    Agree. Love this tute approach but needs just a bit more info.

  • edited November 2017

    The pics are showing

    a) interconnecting audiobus3 and Aum on midi and audio levels:

    Midi: Odessa Midi Suite, Quantum Sequencer, MidiFlowAdapter, Aum midi grid
    Audio: Thumbjam hosted as IAA in audiobus routed to an Aum channel. An audio unit channel in Aum.

    b) Midi fx: Odessa Arpeggiator, Quantum's own midi fx

    On the connection grid in Aum, the oArp goes to mfAdapter which forwards the notes to Quantum, which needs to be prepared for recording, applying midi fx and passing thru to ab3 and back to Aum.

    Implementing it this way because: sending midi notes out from Aum (Odessa) thru Quantum where the notes get altered by fx and can be sent to a destination of your choice.

    Cheers & greetings

  • edited November 2017

    @ccs2 said:
    The pics are showing

    a) interconnecting audiobus3 and Aum on midi and audio levels:

    Midi: Odessa Midi Suite, Quantum Sequencer, MidiFlowAdapter, Aum midi grid
    Audio: Thumbjam hosted as IAA in audiobus routed to an Aum channel. An audio unit channel in Aum.

    b) Midi fx: Odessa Arpeggiator, Quantum's own midi fx

    On the connection grid in Aum, the oArp goes to mfAdapter which forwards the notes to Quantum, which needs to be prepared for recording, applying midi fx and passing thru to ab3 and back to Aum.

    Implementing it this way because: sending midi notes from Aum (Odessa) thru Quantum where the notes get altered by fx and can be sent to a destination of your choice.

    Cheers & greetings

    so you're using Quantum as a velocity to midi channel switcher to Odessa's arp? In realtime (midithru) or recording though? Would be nice to hear this!

    I've just put in recording chords to arpeggios in Quantum (v1.5 coming soon) - that might allow you to use Chordian say to generate patterns.

  • edited November 2017

    Yes, thanks for that :) with the other fx' (echo, etc. - Quantum's midi fx system is very sensitive) and the time functions per steps, f.e. the vel. while playing/w/(&w/out recording)

    ps: Open ab3, go to midi page, add Aum(Port1) in output, Quantum in input. In the next row add Quantum in output and MFAdapter in input.

    Go to the ab3 audio page and add Aum in output, and Thumbjam in input next to Aum (+).
    Tap the Aum icon, add a channel, open Odessa Arpeggio in input.

    Tap the Quantum icon in the ab sidebar, and add a new rack. Tap midi input and record (o), select 'note auto advance' and 'record single notes'. Go to 'Devices', tap the 'Input' icon, deselect 'Ignore Transpose', set 'Midi Thru' to 'On'.

    Go to 'Setup', select Midi Fx Global(x), Ableton Link (Phase).
    Tap (fx), drag and drop an fx and power it on.

    Go back to Aum, into the menu, 'Midi Route': Odessa Arpeggio@Ch2:Midi Out -> MF Adapter In 1. Keyboard -> Odessa Arpeggio@Ch2, IAA Port 1 -> Thumbjam.

    Open Odessa Arp, tap the keyboard icon, and the infinity/hold icon, play a note.

    Caveat: To establish the connection, MidiFlowAdapter needs to be opened at that point, what seems to be related to IAA things (with load and swipe up to delete) remaining from ab3 clearing.

    ... we'll find that sequence (now) ...

  • @ccs2 said:
    Yes, thanks for that :) while recording, and w/ the other fx' (echo, etc. - Quantum's midi fx system is very sensitive) and the time functions per steps.

    ps: Open ab3, go to midi page, add Aum(Port1) in output, Quantum in input. In the next row add Quantum in output and MFAdapter in input.

    Go to the ab3 audio page and add Aum in output, and Thumbjam in input next to Aum (+).

    Tap the Aum icon, add a channel, open Odessa Arpeggio in input.

    Tap the Quantum icon in the ab sidebar, and add a new rack. Tap midi input and record (o), select 'note auto advance' and 'record single notes'. Go to 'Devices', tap the 'Input' icon, deselect 'Ignore Transpose', set 'Midi Thru' to 'On'.

    Go to 'Setup', select Midi Fx Global(x), Ableton Link (Phase).
    Tap (fx), drag and drop an fx and power it on.

    Go back to Aum, into the menu, 'Midi Route': Odessa Arpeggio@Ch2:Midi Out -> MF Adapter In 1. Keyboard -> Odessa Arpeggio@Ch2, IAA Port 1 -> Thumbjam.

    Open Odessa Arp, tap the keyboard icon, and the infinity/hold icon, play a note.

    Caveat: To establish the connection, MidiFlowAdapter needs to be opened at that point, what seems to be related to IAA things (w/ load and swipe up to delete) remaining from ab3 clearing.

    still would be nice to hear a recording ;)

  • edited November 2017

    Listen to Neutraline 0 byCrz on hearthis.at

  • Amazing app!

    Apologies if this has already been covered in this thread but I'm trying to midi map each Step/Fader/Swing etc to my midi controller for each Sequencer (so I can control 2 lines at the same time from a controller). When I click learn, it gives me all the options to map to sequencer 1, but when I add a second sequencer and click learn, there are no options to midi learn the second sequencer.

    I cant spot anything in the manual about this and I may just be being a noob.

    Any advice would be great.

    Cheers

  • I could be wrong but I think you map to the control fader function itself such as Swing so when you switch between different sequences you can control swing for each one. I think you still have to select which sequence is being controlled first then your mapped swing controller will work with whichever sequence is selected. There might be a way to midi learn which sequence is selected.
    I'm sure Tony will chime in and set us straight.

  • @no1normal said:
    Amazing app!

    Apologies if this has already been covered in this thread but I'm trying to midi map each Step/Fader/Swing etc to my midi controller for each Sequencer (so I can control 2 lines at the same time from a controller). When I click learn, it gives me all the options to map to sequencer 1, but when I add a second sequencer and click learn, there are no options to midi learn the second sequencer.

    I cant spot anything in the manual about this and I may just be being a noob.

    Any advice would be great.

    Cheers

    midi learn (i.e. using midi CCs) acts on currently selected sequence. So if you want to control two or more sequences, or one not selected use NRPNs. These are basically two midi CCs together (cc99 then cc98) - see this link for an explanation: http://www.philrees.co.uk/nrpnq.htm

    Here is the current list of NRPNs - note the sequencer ones at the end. However, I don't have them mapped to the drawn parameters like swing - so will add this for the next update.

    Note: NRPNs are absolute values only - no Scaling or Relative (these only work on Learnt CCs)
    0,1,c PlayControls where c is 0=stop, 1=play, 2=pause, 3=reset. All other values ignore.
    0,2,c Transpose x where x= c-64. So valid input range is 40..88 to represent -24..24 range in Quantum. Outside this range will be clamped
    0,3,c,d Tempo x bpm where x = c+d*128 - so 14bit but clamped to range 1..240.
    0,4,c Song mode c where c= 0=All,1=Link,2=Solo,3=Pick,4=Free,5=Poly. All other values ignore.
    0,5,c,d Time Signature c/d where c=1..16 and d=2,4,8,16,32,64. All other values ignored(so both c & d must be valid).
    0,6,c Song Volume c where c=0%..100%. All other values ignored
    0,7,c Metronome where c is 0=off, 1+=on
    0,8,c Link Fader control where c=off, 1+=on
    0,9,c Midi Out where c is 0=off, 1+=on
    0,10,c Cycle where c is 0=off, 1+=on
    0,11,c Record In where c is 0=off, 1=chords, 2=steps
    0,12,c Audition where c is 0=off, 1+=on
    0,13,c Song Mute where c is 0=off, 1+=on
    0,14 Song Solo (will act like solo button press)
    0,15,c Shift sequence Left/Right c steps where c>0 for shift right, c<0 for shift left. Only c = -1,0 & 1 considered. Works best on Rel mode. Cycle mode will delay shift until next loop
    0,16,c,d Main Screen faders - where c = fader 1..fader 16. d=value 0..127 (but may be altered - e.g. notes in a scale)
    0,17,c Mixer Panel page 0=1..12, 1+=13..24 - only if currently visible
    0,18,c,d Mixer Panel fader c=1..24 for consequetive sequence part, d=0..100 (for 0..100% volume) - only applied if valid seq part
    So if Seq1 has 3 parts, Seq 2 has 2 values for c are (1=S1P1,2=S1P2,3=S1P3,4=S2P1,5=S2P2 all other values ignored)
    0,19,c Tempo x bpm where x = c - so 7bit but clamped to range 1..127.
    0,20,c Select Range c where c is 0(1..16),1=(17..32),2=(18..48),3=(49..64) - if valid (i.e. has to be a sequence of that length)

    ----- Sequence/Part parameters
    x,y,c,d Sequence a Part b where x=a4+b (so 5=Seq1A,6=Seq1B..8=Seq1D,5=Seq2A, etc.. 28=Seq6D)
    x,0 Seq/Part x Part Select (ABCD buttons of sequence a)
    x,1,c Seq/Part x Tempo Division, where c=Tempo division (1=1/1 etc)
    x,2,c Seq/Part x Start Step, where c=step 1..64 only. If >end step, will clamp to endStep.
    x,3,c Seq/Part x End Step, where c=step 1..64 only. If seq length will clamp to that(e.g. 16)
    x,4,c Seq/Part x loop type (0=FWD,1=F+1,2=F+2,3=F+3,4=F+4,5=F+5,6=F+6,7=F+7,8=REV,9=BNC,10=BN
    ,11=RND,12=RND,12=BWN,13=F1,14=STP)
    x,5,c Seq/Part x play/stop c is 0=stop, 1=play, 2=pause, 3=reset. All other values ignore.
    x,6,c Seq/Part x transpose c where c= c-64. So valid input range is 40..88 to represent -24..24 range in Quantum. Outside this range will be clamped
    x,7,c Seq/Part x volume c where c=0%..100%. All other values ignored
    x,8,c Seq/Part x invert c where c=0 for OFF, 1+=ON
    x,9,c,d Seq/Part x reflect + key c where c=0 for OFF, 1+ for ON. and the key d=0..127 for note c-2 to g8
    x,10,c Seq/Part x override channel where c=0(use step), 1..16 (override to this value for all steps)
    x,11,c Seq/Part x Timewarp navigator where c=0(OFF), 1+(ON)
    x,12,c,d Seq/Part x Accent Beat where c=0(OFF),1+(ON) and d=value (if on)0..100
    x,13,d,e Seq/Part x Time Signature d+e where d=1..16, e=2,4,8,16,32,64
    x,14,c,d Seq/Part x Step Mute where step = c (1..64) where d=0 is off, 1=on

  • @yowza said:
    I could be wrong but I think you map to the control fader function itself such as Swing so when you switch between different sequences you can control swing for each one. I think you still have to select which sequence is being controlled first then your mapped swing controller will work with whichever sequence is selected. There might be a way to midi learn which sequence is selected.
    I'm sure Tony will chime in and set us straight.

    thats right... :)

  • @ccs2 said:

    Listen to Neutraline byCrz on hearthis.at

    nice - it sort of cuts out just as this ambient piece gets started though!

  • Thanks very much for the quick and detailed response. Will try this tonight.
    Once again congrats on the app. Hoping to make it the heart of my IOS rig

  • @midiSequencer yeah, that was only the intro :blush:
    As @fjcblanco said there's reward in learning and I too am enjoying learning Quantum sequencing, right now I'm getting to grips with midi fx and in that context I'd like to ask you if the parameters of the fx section could be mappable one day?
    Thanks!

  • @no1normal said:
    Thanks very much for the quick and detailed response. Will try this tonight.
    Once again congrats on the app. Hoping to make it the heart of my IOS rig

    I'm not in front of the app at the moment but 99% sure there a button in the learn screen allowing you to use MIDI channels to differentiate between target sequencers. So cc11 ch1=fader1, seq1 and cc11 ch2=fader1, seq2, etc.

  • edited November 2017

    @ccs2 said:
    @midiSequencer yeah, that was only the intro :blush:
    As @fjcblanco said there's reward in learning and I too am enjoying learning Quantum sequencing, right now I'm getting to grips with midi fx and in that context I'd like to ask you if the parameters of the fx section could be mappable one day?
    Thanks!

    most definitely - especially echo which I use a lot to arpeggiate my melodies..
    As I'm adding NRPN on swing etc, will be sure to expose fx too.

Sign In or Register to comment.