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 2 Update Version 2.4.0

[Deleted User][Deleted User]
in General App Discussion
The user and all related content has been deleted.
«1345

Comments

  • audiblevideoaudiblevideo

    Great sequencer

  • Morgman73Morgman73

    Awesome!!

  • SevenSystemsSevenSystems

    Thanks @tja -- manual update will be online shortly!

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • SevenSystemsSevenSystems

    @tja said:

    @SevenSystems said:
    Thanks @tja -- manual update will be online shortly!

    Thanks for this fantastic - and free - update!
    🤗

    Thanks for the always wonderfully nitpicky help with beta testing! 😜

    The manual has also been updated, and can be found at the usual location both online and as a PDF:

    http://seven.systems/xequence2/en/downloads/

    Busy times in the gold-plated Seven Systems WHQ skyscraper for sure...

  • auxmuxauxmux

    How do I stop Xequence from creating multiple instruments / tracks when I have multi-record on? The auto-created instruments are all linked to the same channel output which is not what I want. I’d like to record individual channels from AUM and send back Xequence tracks to the same midi channels.

  • [Deleted User][Deleted User]
    edited November 2022
    The user and all related content has been deleted.
  • SevenSystemsSevenSystems

    @auxmux said:
    How do I stop Xequence from creating multiple instruments / tracks when I have multi-record on? The auto-created instruments are all linked to the same channel output which is not what I want. I’d like to record individual channels from AUM and send back Xequence tracks to the same midi channels.

    Normally, once the necessary tracks for each source (MIDI Port + Channel) have been auto-created, they should be re-used the next time you record something (i.e., Xequence should recognize that they're already there). If Xequence keeps creating new tracks for the same source(s), that could be a bug.

    Could you maybe share a screenshot of both your Xequence instruments screen and arranger screen so that I can see what might be going on?

  • auxmuxauxmux
    edited November 2022

    @SevenSystems I'm using AUM as host. While new tracks are only created once, the problem is they are being created as subtracks, so they have all the same destination and outgoing midi channel.

    Is there a way to do multi-record, where new tracks are created but they are not subtracks, so their outgoing ports/channels are independent?

  • SevenSystemsSevenSystems

    @auxmux said:
    @SevenSystems I'm using AUM as host. While new tracks are only created once, the problem is they are being created as subtracks, so they have all the same destination and outgoing midi channel.

    Is there a way to do multi-record, where new tracks are created but they are not subtracks, so their outgoing ports/channels are independent?

    Not automatically -- you'd have to create the corresponding instruments yourself once, and then go into each track's settings and assign the Multitrack Recording Source manually. Xequence will then re-use these tracks for each multitrack recording the same as if they had been created automatically.

  • auxmuxauxmux
    edited November 2022

    @SevenSystems said:

    @auxmux said:
    @SevenSystems I'm using AUM as host. While new tracks are only created once, the problem is they are being created as subtracks, so they have all the same destination and outgoing midi channel.

    Is there a way to do multi-record, where new tracks are created but they are not subtracks, so their outgoing ports/channels are independent?

    Not automatically -- you'd have to create the corresponding instruments yourself once, and then go into each track's settings and assign the Multitrack Recording Source manually. Xequence will then re-use these tracks for each multitrack recording the same as if they had been created automatically.

    Got it, thanks. How do I stop Xequence from creating new subtracks for recording after creating tracks manually? Because I was trying this approach, but new subtracks kept being created. Is there a setting to disable this? I tried to disable Automatically Manage Tracks but didn't appear to work.

  • SevenSystemsSevenSystems

    @auxmux said:

    @SevenSystems said:

    @auxmux said:
    @SevenSystems I'm using AUM as host. While new tracks are only created once, the problem is they are being created as subtracks, so they have all the same destination and outgoing midi channel.

    Is there a way to do multi-record, where new tracks are created but they are not subtracks, so their outgoing ports/channels are independent?

    Not automatically -- you'd have to create the corresponding instruments yourself once, and then go into each track's settings and assign the Multitrack Recording Source manually. Xequence will then re-use these tracks for each multitrack recording the same as if they had been created automatically.

    Got it, thanks. How do I stop Xequence from creating new subtracks for recording after creating tracks manually? Because I was trying this approach, but new subtracks kept being created. Is there a setting to disable this? I tried to disable Automatically Manage Tracks but didn't appear to work.

    That should not happen. Could you maybe make a short screen recording of it happening?

  • Tamir_Raz_MatazTamir_Raz_Mataz

    Wish it could host

  • ervinervin

    And yes, the AUM button has arrived!
    🙂👍

    I might be extremely limited in my thinking, but that one feature alone makes me happy. Everything else is icing on the cake AFAIC. Thank you 👊

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • SevenSystemsSevenSystems

    @JMmusic said:
    @SevenSystems Maybe a small bug.
    I was recording Rozeta Particles hosted in AUM into X2, and X2 crashed just as MIDI data started. Restarted X2 and got this warning message.
    Cleared it and restarted the recording with no issues. Closed the apps.
    The bug is that every time I open X2 now, the warning screen shows, even though I follow the message and Save As the project with a different name.

    Thanks a lot for the report.

    I've found a potential issue that could cause this warning -- are you possibly launching Xequence from another app (Audiobus or AUM), then never actually bringing it to the foreground, then removing it, then launching it again? This would cause an erroneous warning like that. I'll be fixing this in an update shortly.

    In the meantime, you should be able to get rid of the warning by ensuring that you bring Xequence to the foreground at least once.

    If you can reproduce the crash when receiving MIDI data, I'd be very happy to hear how you did it because it needs to be fixed! 😜

  • SevenSystemsSevenSystems

    @ervin said:
    And yes, the AUM button has arrived!
    🙂👍

    I might be extremely limited in my thinking, but that one feature alone makes me happy. Everything else is icing on the cake AFAIC. Thank you 👊

    I know the feeling when you tunnel-vision onto one specific issue that drives you crazy... it's all good! 😄

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • SevenSystemsSevenSystems

    @JMmusic said:

    @SevenSystems said:

    @JMmusic said:
    @SevenSystems Maybe a small bug.
    I was recording Rozeta Particles hosted in AUM into X2, and X2 crashed just as MIDI data started. Restarted X2 and got this warning message.
    Cleared it and restarted the recording with no issues. Closed the apps.
    The bug is that every time I open X2 now, the warning screen shows, even though I follow the message and Save As the project with a different name.

    Thanks a lot for the report.

    I've found a potential issue that could cause this warning -- are you possibly launching Xequence from another app (Audiobus or AUM), then never actually bringing it to the foreground, then removing it, then launching it again? This would cause an erroneous warning like that. I'll be fixing this in an update shortly.

    In the meantime, you should be able to get rid of the warning by ensuring that you bring Xequence to the foreground at least once.

    If you can reproduce the crash when receiving MIDI data, I'd be very happy to hear how you did it because it needs to be fixed! 😜

    Can’t get it to crash again, but I do keep getting this error, even without a crash. I just started a new project and setup a few instruments, pointed them to AUM, added some notes then closed both apps. Now i get the error pop up, but it didn’t crash. I just manually closed the app.

    Does this warning also occur if you:

    1) Kill (swipe up on the multitasking screen) Xequence
    2) Launch Xequence by tapping the home screen icon
    3) Kill Xequence again by swiping it up on the multitasking screen
    4) Launch Xequence again by tapping the home screen icon

    ?

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • SevenSystemsSevenSystems

    OK, thanks! Will be sorted in an update soon.

  • [Deleted User][Deleted User]
    edited November 2022
    The user and all related content has been deleted.
  • [Deleted User][Deleted User]
    edited November 2022
    The user and all related content has been deleted.
  • SevenSystemsSevenSystems

    @JMmusic said:
    Don’t make me go back to Cubasis with a crappy midi, editor and a huge bug in the CC recording/editing!

    Haha, thanks for the... compliment I guess! Maybe Steinberg wants to hire some lonely Irish backyard developer to give their MIDI editor a boost 😂

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • KrupaKrupa

    @Tamir_Raz_Mataz said:
    Wish it could host

    I’d love it if there was just a crappy gm sound set built in, it’d be an even more perfect environment for focusing on composition

  • SevenSystemsSevenSystems

    @Krupa said:

    @Tamir_Raz_Mataz said:
    Wish it could host

    I’d love it if there was just a crappy gm sound set built in, it’d be an even more perfect environment for focusing on composition

    OK, maybe I'll add "Offer crappy GM sound set as $3.99 IAP" to the roadmap (focus on "crappy", of course! 😆)

  • ik2000ik2000

    @Krupa said:

    @Tamir_Raz_Mataz said:
    Wish it could host

    I’d love it if there was just a crappy gm sound set built in, it’d be an even more perfect environment for focusing on composition

    Think it’s pretty simple to integrate with software like BS-16i standalone and map voices to each midi channel within Xequence. Save as a preset and boom… it’s pretty perfect as is.

  • KrupaKrupa

    @SevenSystems said:

    @Krupa said:

    @Tamir_Raz_Mataz said:
    Wish it could host

    I’d love it if there was just a crappy gm sound set built in, it’d be an even more perfect environment for focusing on composition

    OK, maybe I'll add "Offer crappy GM sound set as $3.99 IAP" to the roadmap (focus on "crappy", of course! 😆)

    Definitely, pc ISA sound card crappy for the ultimate in you’ve got to make the music good to get over the bad sounds 😁

  • [Deleted User][Deleted User]
    edited December 2022
    The user and all related content has been deleted.
Sign In or Register to comment.

© Vanilla Keystone Theme 2024