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 ?

1…3637394142…52

Comments

  • RichtownsRichtowns

    FYI Im on ios12 “old” pro 9.7. No problems so far. Mini 2 updated ok too, also ios 12, opened new project, restored purchases, drew some music.
    Bad luck for some people and you @SevenSystems

  • RichtownsRichtowns

    @Jumpercollins without the iap all the data goes to one track (merged i suppose). The multitrack iap splits it into respective (midi) channels

  • [Deleted User][Deleted User]

    No crash here

  • wimwim

    @SevenSystems said:

    @wim said:
    Thanks for this EPIC update only WEEKS after the MASSIVE previous update. You’re gonna have to call the next one GAMECHANGING. :D

    Haha, you're the first one to notice! :D I'm gonna pull it now probably though, a crash right on startup for appearently EVERYONE except ME and my TESTERS isn't too good publicity ;)

    It is indeed EPIC though!

  • [Deleted User][Deleted User]

    @CracklePot said:

    @SevenSystems said:
    @CracklePot sorry to hear. It must have been some incompatibility between the current version of Xequence and your last saved project. Didn't get any problems myself, nor any reports from the beta team, so this is surprising to me.

    Did the error occur immediately after opening Xequence after the update, or did you first do something (tap a button, etc.)?

    Also, by "It stopped with the error after that", do you mean that the application stopped working, or that the error stopped occuring?

    Thanks!

    I launched the app right after updating it. I did have an old project that was auto loading. The error gave a choice to continue or quit and restart. It recommended quitting. I tried that the first couple of times, but the error was reported upon launching the app still, so I then chose to continue. I made a new project and quit, then relaunched the app. It now is working normally. I also suspect it was something fishy with my last project, but it seems to load that project fine now if I open it.
    Anyway, everything is working fine. Just wanted to stave off any panic if anyone else gets the same error immediately after updating.

    Thanks again. You are a champion among iOS developers. B)

    Same error

  • [Deleted User][Deleted User]

    @SevenSystems will there be an host button added to the app so I can quickly return to my host AUM. Currently I have to click on home button then choose app, this is pretty annoying IMO. Hope it can be implemented.

  • ruggedsmoothruggedsmooth

    Updated and purchased IAP with no errors
    Haven’t tried the multi tracking yet

    @SevenSystems is a top dev and thank you for always responding to forum questions!

  • SevenSystemsSevenSystems
    edited October 2018

    @everyone: Problem hopefully found and fixed (race condition), uploading 1.9.1 now and hoping for an expedited review. THANKS everyone for the reports!

    (it only occured for some people because it depends on the exact order of events that happen almost simultaneously, with a few microseconds deciding if the crash occurs or not, AND it only happens for old installations with the old folder structure. So, extremely hard to find, simulate, and fix. Fortunately I'm 10 cups of coffee today so I think I got it sorted!)

  • cuscolimacuscolima

    Works perfectly here (ios12). This channels autodetection is amazing and so convenient for example with something like Gestrument...beautiful

  • [Deleted User][Deleted User]

    I’m so dumb I can’t figure the multitrack recording setup lol

    @SevenSystems

    Could you post some screen shots or something showing an AB3 / Fugue Machine / Xequence multi record. I must be close, but all the midi is still going to one track.

    :D

  • SevenSystemsSevenSystems
    edited October 2018

    @Fruitbat1919 said:
    I’m so dumb I can’t figure the multitrack recording setup lol

    @SevenSystems

    Could you post some screen shots or something showing an AB3 / Fugue Machine / Xequence multi record. I must be close, but all the midi is still going to one track.

    :D

    Would this help? ;)

    http://seven.systems/xequence/manual/#multitrack-recording

    (if anything is still unclear then ask away!)

    (note that if you record from Audiobus, you have to create a SEPARATE MIDI lane for each source app and select a different Xequence MIDI In for each. Maybe this should be added to the manual...)

    (note that specifically for Fugue Machine, you have to configure it to actually send its different playheads to separate MIDI channels or Audiobus ports)

    (I didn't test Fugue Machine through Audiobus btw, it might not be possible. But it does work outside of Audiobus).

  • SevenSystemsSevenSystems
    edited October 2018

    @Fruitbat1919 I just tested it through Audiobus and it is possible. Just create a separate MIDI lane for each Fugue Machine playhead (there's 4), put Xequence in the Output and select MIDI In [1, 2, 3, 4] correspondingly.

  • [Deleted User][Deleted User]

    @SevenSystems said:

    @Fruitbat1919 said:
    I’m so dumb I can’t figure the multitrack recording setup lol

    @SevenSystems

    Could you post some screen shots or something showing an AB3 / Fugue Machine / Xequence multi record. I must be close, but all the midi is still going to one track.

    :D

    Would this help? ;)

    http://seven.systems/xequence/manual/#multitrack-recording

    (if anything is still unclear then ask away!)

    (note that if you record from Audiobus, you have to create a SEPARATE MIDI lane for each source app and select a different Xequence MIDI In for each. Maybe this should be added to the manual...)

    (note that specifically for Fugue Machine, you have to configure it to actually send its different playheads to separate MIDI channels or Audiobus ports)

    (I didn't test Fugue Machine through Audiobus btw, it might not be possible. But it does work outside of Audiobus).




  • SevenSystemsSevenSystems

    @Fruitbat1919 how odd, I just tested this. Can you try playing with the settings inside Fugue Machine a little?

  • JumpercollinsJumpercollins

    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.

  • cuscolimacuscolima

    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?

  • SevenSystemsSevenSystems

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

  • RajahPRajahP

    Brilliant.. but how do you export a multi-track midi file, it only shows up as a 1track file in Cubasis for now..

    This is a Multi-Track recording of a GR-16 project.. nice..

  • [Deleted User][Deleted User]

    @SevenSystems said:
    @Fruitbat1919 how odd, I just tested this. Can you try playing with the settings inside Fugue Machine a little?

    Tried changing all sorts of settings and now giving up lol. It works fine for me without AB3 :)

  • SevenSystemsSevenSystems

    @RajahP said:
    Brilliant.. but how do you export a multi-track midi file, it only shows up as a 1track file in Cubasis for now..

    When exporting a MIDI file, Xequence creates separate MIDI tracks PER INSTRUMENT, NOT per track! (this is intentional, but I might add an option to use tracks instead some day).

    So, to have your tracks separate in the exported MIDI file, just create a new instrument for each track, and then assign each track to its own instrument. That should do the trick.

  • RajahPRajahP
    edited October 2018

    @SevenSystems said:

    @RajahP said:
    Brilliant.. but how do you export a multi-track midi file, it only shows up as a 1track file in Cubasis for now..

    When exporting a MIDI file, Xequence creates separate MIDI tracks PER INSTRUMENT, NOT per track! (this is intentional, but I might add an option to use tracks instead some day).

    So, to have your tracks separate in the exported MIDI file, just create a new instrument for each track, and then assign each track to its own instrument. That should do the trick.

    Ok.. Thank.. BRB...

    Edit..

    Sweet.. Thanks..

  • SevenSystemsSevenSystems

    @RajahP said:

    @SevenSystems said:

    @RajahP said:
    Brilliant.. but how do you export a multi-track midi file, it only shows up as a 1track file in Cubasis for now..

    When exporting a MIDI file, Xequence creates separate MIDI tracks PER INSTRUMENT, NOT per track! (this is intentional, but I might add an option to use tracks instead some day).

    So, to have your tracks separate in the exported MIDI file, just create a new instrument for each track, and then assign each track to its own instrument. That should do the trick.

    Ok.. Thank.. BRB...

    Edit..

    Sweet.. Thanks..

    You're welcome! ;) I agree it's maybe not very intuitive, the decision between separating by arranger tracks or by instruments was very close.

  • RajahPRajahP

    @SevenSystems said:

    @RajahP said:

    @SevenSystems said:

    @RajahP said:
    Brilliant.. but how do you export a multi-track midi file, it only shows up as a 1track file in Cubasis for now..

    When exporting a MIDI file, Xequence creates separate MIDI tracks PER INSTRUMENT, NOT per track! (this is intentional, but I might add an option to use tracks instead some day).

    So, to have your tracks separate in the exported MIDI file, just create a new instrument for each track, and then assign each track to its own instrument. That should do the trick.

    Ok.. Thank.. BRB...

    Edit..

    Sweet.. Thanks..

    You're welcome! ;) I agree it's maybe not very intuitive, the decision between separating by arranger tracks or by instruments was very close.

    Well, it works.. Congrats.. this is a game changer for me...

    Later.. time to record...

    Thanks..

  • SevenSystemsSevenSystems

    @RajahP great to see happy customers.

  • CracklePotCracklePot
    edited October 2018

    I am very super-duper happy! :)
    New 1.9.1 update is live, BTW.

  • reziduerezidue

    Nice job on these updates. It’s really interesting reading about people’s workflows. I keep buying the IAP as they come out even if I don’t have much time lately to work on music. I enjoy supporting and you do a great job listening to your customers while quickly delivering.

  • SevenSystemsSevenSystems

    @CracklePot said:
    I am very super-duper happy! :)
    New 1.9.1 update is live, BTW.

    Yep, Apple did a great job with the "emergency review".

  • SpookyZooSpookyZoo
    edited October 2018

    @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 file into Xequence with all data correctly created and spread over their individual tracks. Basically now a type 1 midi file.

    I then get to do all my midi editing in my preferred editor, Xequence! :)

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

  • RajahPRajahP
    edited October 2018

    @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..

    :)

  • SpookyZooSpookyZoo

    @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?

Sign In or Register to comment.