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 update Polyhymnia? anyone know how this works?

2

Comments

  • The old Midiflow btw, not the AB3 one

  • @CracklePot said:
    Bought it and the IAP. Pretty excited to finally try this one. I have followed its rapid development since it was released, read all discussions and fanfare, and even interacted a bit with the awesome creator of this beauty.

    The addition of a Generative module is unexpected, but very interesting for me. I really like generative/algorithmic composing methods. Looking forward to exploring this new one.

    where is the generative module in Polyhymnia. do you have to buy Polyhymnia to use it?

  • This is just too much fun and keeps distracting me from development ;)

    The settings for this have been configured manually (no flask)... so with a little bit of manual effort you can really get some amazing results.

    (There's also some new features in this video which weren't quite ready for 1.7 but should be in 1.7.1 next week :))

  • @eross said:

    @CracklePot said:
    Bought it and the IAP. Pretty excited to finally try this one. I have followed its rapid development since it was released, read all discussions and fanfare, and even interacted a bit with the awesome creator of this beauty.

    The addition of a Generative module is unexpected, but very interesting for me. I really like generative/algorithmic composing methods. Looking forward to exploring this new one.

    where is the generative module in Polyhymnia. do you have to buy Polyhymnia to use it?

    It is a new feature in the latest update. You can use it, but saving requires the $2 IAP.
    I was so excited about @SevenSystems take on generative techniques that I bought the basic app and the IAP in one go. Didn’t even bother to try it or see what it was first, but based on what he did with the basic Midi sequencer idea, I know this is going to be good.

    I’m sure I’ll be spouting off about it all in the next few days once I get some hands on experience with it. :)

  • @SevenSystems said:
    @charleso thanks... let us know if it works as intended. If not, it'll be fixed ;)

    Concerning AU MIDI: This is unfortunately not very likely... what's definitely more likely though is support for AU synth hosting inside Xequence. But no definite time line yet...

    Boppad recording fine here, works great... Still getting around the app, haven’t figured out the generative stuff yet.

  • @SevenSystems said:
    This is just too much fun and keeps distracting me from development ;)

    The settings for this have been configured manually (no flask)... so with a little bit of manual effort you can really get some amazing results.

    (There's also some new features in this video which weren't quite ready for 1.7 but should be in 1.7.1 next week :))

    Bloody awesome. Great addition to what is already a top (and essential) music app :)

  • edited March 2018

    @CracklePot said:
    The IAP system in this app just shows that this dev is tying to improve and innovate, not just pump out more of the same in the same old way.

    Sure, fair enough. I will have a fiddle over the next few days, and see if more is better for me. :)

  • @tja said:
    OK, and sorry.
    I have a job that allows me to buy a coffee every day - and skipping that, allows to buy Apps instead.
    Please forgive, that I was not thinking.

    >

    No worries, it’s easy to misunderstand each other. I appreciate you clarifying. :)

    If the app suits my way of working, I will be happy to give up something else to buy into it some more.

  • @charleso said:
    Boppad recording fine here, works great... Still getting around the app, haven’t figured out the generative stuff yet.

    Wheeww, good to hear, I wasn't sure about it! Thanks.

  • is there a buy everything package deal?

  • I’m sorry to say this but I don’t find Xequence very intuitive to use at all. How do you get sound out of Polyhymnia demos? I see notes in the piano roll, I have an instrument on the track. Press play and the transport moves but no sound.

    I’ve never been more frustrated by a sequencer.

    Help!

  • The user and all related content has been deleted.
  • edited March 2018

    I already know that and if you read my post I have the track pointed to the instrument. I can get sound from the instrument ( left side keys) but no sound when the track plays.

  • The user and all related content has been deleted.
  • I got the demo to play but I’m not sure how. I ended up starting a new song and did everything over and it works so who knows, I must have messed up something the first time.
    I think what is still giving me a problem wrapping my head around this app is the separation of instruments and tracks. To me they should be the same thing.

  • When you are on a track with the piano roll, the keyboard is vertically along the left side and when you play those keys you hear the instrument on that track. Does that make sense?

  • @yowza said:
    I already know that and if you read my post I have the track pointed to the instrument. I can get sound from the instrument ( left side keys) but no sound when the track plays.

    Xequence' midi handling is as good as it get's, but it's still at the mercy of the different ways midi is handled in other apps. Try a different app. Check channels and routing. The usual stuff.

  • @yowza said:
    I think what is still giving me a problem wrapping my head around this app is the separation of instruments and tracks. To me they should be the same thing.

    It’s funny, I think this is genius. So easy to route arrangements to multiple synths and vice versa.

  • I got it to work but there is something about the layout and the way you navigate around the app that I don’t find very intuitive.

  • @gusgranite said:

    It’s funny, I think this is genius. So easy to route arrangements to multiple synths and vice versa.

    I understand what your saying but the app is so DAW like in almost every other respect except for the track/instrument dichotomy that it throws me off every time I try to use it.

  • The user and all related content has been deleted.
  • The user and all related content has been deleted.
  • edited March 2018

    Sorry, I guess I didn’t explain clearly.

    When I could not get the PolyHymnia demo to make sound while the transport was playing I was able to get sound from that keyboard so the instrument would work but the demo wouldn’t make any sound when playing. Not sure why.
    Does that make sense?
    I ended up having to delete the project and start all over and the demo would make sound.

  • The user and all related content has been deleted.
  • edited March 2018

    @yowza: Note that in the PolyHymnia demo file, one of the tracks is solo'd (the uppermost one), so you will not hear sound from any other track except if you solo them. You would have to zoom in vertically to see the actual solo / mute buttons, or open the track settings of a track. On muted / not solo'd tracks, the parts appear darker. I agree that this can be a bit confusing when zoomed far out. I think this is what has been happening in your case.

    Concerning the separation of tracks and instruments, this was a fundamental design decision from the start. As others have already pointed out, this makes separating different data types (notes, controllers) and even different parts of a performance very easy even if they use the same instrument (sound). It also allows for greater flexibility when arranging.

  • The user and all related content has been deleted.
  • @SevenSystems said:
    @yowza: Note that in the PolyHymnia demo file, one of the tracks is solo'd (the uppermost one), so you will not hear sound from any other track except if you solo them. You would have to zoom in vertically to see the actual solo / mute buttons, or open the track settings of a track. On muted / not solo'd tracks, the parts appear darker. I agree that this can be a bit confusing when zoomed far out. I think this is what has been happening in your case.

    I suspect you’re right, that’s the only thing that makes sense.

    Concerning the separation of tracks and instruments, this was a fundamental design decision from the start. As others have already pointed out, this makes separating different data types (notes, controllers) and even different parts of a performance very easy even if they use the same instrument (sound). It also allows for greater flexibility when arranging.

    I understand why you separated tracks/ instruments but my brain doesn’t work that way and I doubt if I would ever use it your way. I use a sequencer as a composing device more than anything so I’m most often manipulating notes, velocity, gates etc. I can’t remember the last time I automated cc’s for a filter for example.

  • @yowza I'm completely the opposite. Take a look at Alpha (included demo project). It contains more automation than notes :smiley:

  • @SevenSystems - I am trying to work out how to best use and manipulate PolyHymnia.
    Any chance of a 3m video showing what you (personally) can do with it?
    It is such a mega feature in Xequence, it would be great to have some tips and starting points etc.
    :p

  • @Mayo I think @gmslayton has a PolyHymnia video on his "Xequence Masterclass" roadmap :)

Sign In or Register to comment.