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.

Xequence midi sequencer ?

1373840424352

Comments

  • @SpookyZoo said:

    @RajahP said:

    @SpookyZoo said:
    @SevenSystems
    Congrats on the update. Never saw that error while testing, glad you got it sorted.

    BTW, in relation to our conversation about different midi file types (0 & 1), I had asked if you knew of any tool to change a midi file type 0 to type 1.

    Anyhoo I found a way that works nicely.

    If importing a type 0 file into Xequence, all data is combined onto a single track. However, I found that if I load this midi file type 0 into a fresh Cubasis project then mixdown and export that midi file (I shared it straight from Cubasis into the Xequence folder via the Files app).

    I can then load that Cubase midi mixdown into Xequence with all data correctly created and spread over their individual tracks. Basically a type 1 midi file.

    Thought I'd post it here, just in case that is useful info for others who will be importing midi files.

    Seems to be working for BM3’s Import issue also (mixing down in Cubasis) ... Great..

    :)

    Cool!

    Did you try that just now?

    Yep, confirmed... Thank you..

  • Looking forward to this! Have you tested with Xynthesizr?

  • edited October 2018

    @SevenSystems said:

    @Jumpercollins said:
    Just got the IAP, this app just keeps getting better and better, cheers @SevenSystems looking forward to trying it out with my Circuit. Store feedback added. Hopefully the update to the update will be here by morning.

    Thanks very much! And the update-to-the-update has just been approved. THANK YOU APPLE! 🍏

    @cuscolima said:
    Is it possible to record the CC input message generated by an external application? Is there also an autodetection of incomming CC messages?..and how can I do that?

    Yes and yes, and you don't need to do anything, it's all automatic!

    Thanks but in this case I have a little problem with my ipad pro (2017) because no CC are recorded. I have done exacltly the same on my iphone7 and it work very well, the CC are recorded and I can see the traces. Any suggestion?

    EDIT : in fact, on my iphone I can record only one CC per track at a time...so promising but not completely here yet. I have however to mention that we have here, and in my opinion, a REAL game changer (forbidden word, I know...)

  • In fact, only CC 1 can be recorded...

  • @cuscolima said:
    In fact, only CC 1 can be recorded...

    Thanks for the report, will check today and get back to you.

  • @cuscolima said:
    In fact, only CC 1 can be recorded...

    I just tried to record various other controllers and it seemed to be working fine; are you sure that you've either configured the corresponding controller on the Xequence instrument, or that "Auto-add Controllers" is enabled in Settings?



  • edited October 2018

    @SevenSystems I was getting the impression yesterday that in multitrack mode channels that only have midi are ignored. Doing some more tests today and it looks like its more complicated than that.
    This is repeatable however
    In multitrack mode trying to record just rozetta lfos in aum doesnt work. Nothing is seen or recorded but if you turn off multitrack then three controllers are leant and the data recorded (I love this feature). This is just midi cc data
    I started with a new xequence project and routed rozetta lfos in aum to xequence destination
    Something not quite right it seems
    Ipad mini 2 ios12
    Iphone se ios12 - the same

  • @Richtowns interesting, thanks... will check on that shortly, I might actually have skipped the new source detection code for controllers.

  • @SevenSystems Auto cc descover does work however if you set up the tracks manually to record from Xequence Destination and then midi channel. Then enabling multitrack then the autodiscovery of controllers does work in multi mode. It must be a combination of autodiscover channels and cc's at the same time (you know, maybe)

    But on my iphone se ios 12 I had no options to select a multitrack source!! Xequence Destination wasnt available. So this workaround doesnt, um, work

    One, probably unimportant last thing, I noticed a difference between the iphone and ipad. By default the ipad has 3 midi sources, network session 1, audiobus and Xequence destination. The iphone does have network session 1!

    Happy to help, did I mention I love this app

  • @SevenSystems said:

    @cuscolima said:
    In fact, only CC 1 can be recorded...

    I just tried to record various other controllers and it seemed to be working fine; are you sure that you've either configured the corresponding controller on the Xequence instrument, or that "Auto-add Controllers" is enabled in Settings?

    Yes, I have configured everything as you wrote but still it doesn’t work. I can only see the modulation slide moving...not the volume, pan, etc



  • @cuscolima: is there actually any automation recorded for i.e. Volume? I see from your screenshot that you have "MIDI In" disabled, so no inputs from external controllers should ever get recorded, and no live MIDI input from external controllers will be recognized.

  • @Richtowns said:
    @SevenSystems Auto cc descover does work however if you set up the tracks manually to record from Xequence Destination and then midi channel. Then enabling multitrack then the autodiscovery of controllers does work in multi mode. It must be a combination of autodiscover channels and cc's at the same time (you know, maybe)

    But on my iphone se ios 12 I had no options to select a multitrack source!! Xequence Destination wasnt available. So this workaround doesnt, um, work

    One, probably unimportant last thing, I noticed a difference between the iphone and ipad. By default the ipad has 3 midi sources, network session 1, audiobus and Xequence destination. The iphone does have network session 1!

    Happy to help, did I mention I love this app

    Thanks :)

    Note that you can only select those sources as multitrack inputs that are actually enabled in Settings -> MIDI / Recording -> MIDI Input -> Sources. You probably have different sources enabled there on your different devices. Be sure to enable all sources that you want to use.

  • @SevenSystems said:
    @cuscolima: is there actually any automation recorded for i.e. Volume? I see from your screenshot that you have "MIDI In" disabled, so no inputs from external controllers should ever get recorded, and no live MIDI input from external controllers will be recognized.

    I have Rosetta lfo in AUM running three oscillators with CC 1, CC 7 and CC 10 on channel 1. In Xequence, I can see the “modulation” slider moving and I can record it. I cannot see the volume and the pan sliders moving and cannot record them. Midi in is activated and set to Xequence destination.

  • @cuscolima said:

    @SevenSystems said:
    @cuscolima: is there actually any automation recorded for i.e. Volume? I see from your screenshot that you have "MIDI In" disabled, so no inputs from external controllers should ever get recorded, and no live MIDI input from external controllers will be recognized.

    I have Rosetta lfo in AUM running three oscillators with CC 1, CC 7 and CC 10 on channel 1. In Xequence, I can see the “modulation” slider moving and I can record it. I cannot see the volume and the pan sliders moving and cannot record them. Midi in is activated and set to Xequence destination.

    Could you share the Rosetta and/or AUM preset, and the Xequence project, so I can have a closer look? I would appreciate it! (you can PM me with a link or I can send you my email address.)

  • @SevenSystems thanks so much for the update and the multi-track IAP
    Was too tired yesterday to log here to post this :lol:

    Now I can 'backup' my ol' midi info for MC-303, EA-1, ER-1 and EMX. Xequence is now the groovebox mastermind :wink:

  • @Richtowns said:
    @SevenSystems Auto cc descover does work however if you set up the tracks manually to record from Xequence Destination and then midi channel. Then enabling multitrack then the autodiscovery of controllers does work in multi mode. It must be a combination of autodiscover channels and cc's at the same time (you know, maybe)

    Thanks so much, problem found and fixed, update will be available in the next couple of days.

    I have no idea why, but I explicitly disabled auto-adding controllers for multitrack recording back when I started implementing it. So, it was an easy fix: :)

  • @SevenSystems on iPhone SE is this normal? Is there a way to see the other items in the menu tabs which hide behind the transport buttons?

  • edited October 2018

    @MusicMan4Christ wow, thanks for the report, that's extremely odd. It looks like on your iPhone SE, the top toolbar buttons do not have enough space and thus flow into the next line. This does not occur on my iPhone SE with exactly the same settings. What iOS version are you on?

    EDIT: To help you out until this is fixed, can you try selecting a "shorter number" both in the Q menu and in the BPM menu, so that the buttons do not occupy that much space? That might fix the issue temporarily.

    EDIT 2: Best fix for now: DISABLE THE PANIC BUTTON in Settings -> MIDI / Recording!

  • Thanks! IOS 12 or latest. Noted on the ideas. :)

    @SevenSystems said:
    @MusicMan4Christ wow, thanks for the report, that's extremely odd. It looks like on your iPhone SE, the top toolbar buttons do not have enough space and thus flow into the next line. This does not occur on my iPhone SE with exactly the same settings. What iOS version are you on?

    EDIT: To help you out until this is fixed, can you try selecting a "shorter number" both in the Q menu and in the BPM menu, so that the buttons do not occupy that much space? That might fix the issue temporarily.

    EDIT 2: Best fix for now: DISABLE THE PANIC BUTTON in Settings -> MIDI / Recording!

  • @MusicMan4Christ alright. I've fixed this in the current development version, though on 4" iPhones there's absolutely no way all buttons can fit into the top toolbar. So the solution for now is (don't laugh) :

  • Looks great to me! :) <3 <3 <3

    @SevenSystems said:
    @MusicMan4Christ alright. I've fixed this in the current development version, though on 4" iPhones there's absolutely no way all buttons can fit into the top toolbar. So the solution for now is (don't laugh) :

  • Ok, new update solved it all. Beautiful beautiful

  • Great to see bank select finally added, just bought the unlimited track IAP as I can now make more use of Xequence in one of my main workflows.

  • edited October 2018

    Looks great, I want use it, but it's useless for me without it being ab;e to slave to midi clock.. And Ableton Link is not a solution.

  • I just did a test recording 52 bars of 16 channel midi, with automation, coming from Groove Rider GR-16, with auto add. It recorded perfectly, adding all the channels as they came in. I then set each to output back to GR-16. The playback was perfect, including automation. Great job @SevenSystems! This is going to be very, very useful.

    The only thing I could maybe hope for is for output instruments to be set up automatically with the channel number and cc’s set up. The only way I could find to output the recorded midi was to manually set up 16 output instruments, then change the recorded tracks to them. Not a big deal, but it would be a time saver.

    Thanks again for this great update!

  • @cuscolima said:
    Ok, new update solved it all. Beautiful beautiful

    Great, thanks for your help with debugging! :)

    @busker glad you're sorted and thanks for the support.

    @wim very happy to hear it working well even with large amounts of incoming data. The truth is that Multitrack Recording is the first feature that I added purely because of user demand and that I thus didn't have a clear vision for, so I was a bit unsure if I'd hit the nail on the head this time ;) Nice it's all being stable and usable.

    About the automatic MIDI output setup: it's not always trivial to do this automatically, however yes, there might be ways to improve it, especially in combination with MT recording. Will look into that.

  • YAY!
    Multitrack recording.

  • This is working pretty well for me know, discovering everything. Very nice.
    I have found a problem though @SevenSystems
    When recording everything goes well until the recorded data touches the rightmost edge of the max zoom area. Then it stops recording. Is is just me?
    Let me know if I need to explain a bit better but to reproduce I just click record in multitrack mode and after about 50 bars the recording automatically stops!

  • @Richtowns said:
    This is working pretty well for me know, discovering everything. Very nice.
    I have found a problem though @SevenSystems
    When recording everything goes well until the recorded data touches the rightmost edge of the max zoom area. Then it stops recording. Is is just me?
    Let me know if I need to explain a bit better but to reproduce I just click record in multitrack mode and after about 50 bars the recording automatically stops!

    Yes, that's a known limitation, the song is considered to end 64 bars after the last existing part... if you need to record for longer, please just draw a long empty part before recording (say, 200 bars). I should probably include this in the FAQ, as it's come up before.

  • Great. Thanks. Yes, defo one for the faq
    Im really over the moon with Xequence. Just spent twenty minutes editing midi and found it quite enjoyable. That's quite something.

    The only tinsey wincey thing that felt like a restiction was the one bar restriction when editing, splitting, moving tracks in the track view.
    Congratulations on an excellent app

Sign In or Register to comment.