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.

Tonality - Music Reference by Bryce Hostetler - Updated with Midi and Auv3 support

191012141542

Comments

  • @TonalityApp said:
    @horsetrainer
    Out now (or soonish, don’t know how long it’ll take the App Store to update). Let me know if you have any suggestions.

    Cool! Will check it out when the update arrives. :)

    The Korg M3 workstation (I still have one in storage) had the best easy to use chord pads (IMO).
    It was very simple to assign chords to pads on the M3....

    1) Push the "Chord Assign" button.
    2) Play a chord by pressing the keyboard keys simultaneously, or by pressing the keys to make up the chord one key at a time.
    3) Press the pad your want to assign the chord to.
    4) The notes you played will now be played together as a chord every time you press that chord pad.

    The nice thing about the M3 chord pads, is it would let you play "any" eight notes, and assign it to a pad.

  • @horsetrainer

    The workflow I came up with should be similar:
    1) Hold down an empty pad
    2) Play any notes you want at any velocities, one at a time or together
    3) As soon as you release the key(s), the pad will be assigned (and identified if you want)

  • edited November 2019

    @TonalityApp said:
    @horsetrainer

    The workflow I came up with should be similar:
    1) Hold down an empty pad
    2) Play any notes you want at any velocities, one at a time or together
    3) As soon as you release the key(s), the pad will be assigned (and identified if you want)

    That should work. :)
    Thanks for adding the new feature. I've been looking for a simple AUv3 "quick assign" chord pad player for a while now.
    I'll provide you with feedback after I have a chance to check it out.

  • edited November 2019

    @TonalityApp said:

    The workflow I came up with should be similar:
    1) Hold down an empty pad
    2) Play any notes you want at any velocities, one at a time or together
    3) As soon as you release the key(s), the pad will be assigned (and identified if you want)

    That’s great ... I bought the app on the strength of your comments on the Black Friday thread, hoping to use Tonality as a chord trigger where I can enter exactly the notes I want to be triggered by each pad but so far it seems more fixed than I had hoped i.e. I can only select from named chords which is really not what I was after, and I can’t seem to edit all the notes if the edited chord covers a wide range I.e. 3 octaves or so ... and it’s currently not possible to scroll up and down if the chord is too big to be displayed on the keyboard, which means the chord cannot be edited properly.

    But if the above feature is in the pipeline that will be perfect for my workflow, though I would want to be able to easily add and remove notes from the chord afterwards, And be able to scroll through the whole chord no matter how large it is.

  • edited November 2019

    @craftycurate The reason most pads are restricted is that there are so many chords you can usually find one using the keyboard to search, and this allows you to have an idea of the harmonic structures you’re working with.

    With regards to the inability to edit wide voicings, what happens exactly?

    Edit:
    With regard to your most recent edit, the ability to add and remove notes will remain no matter how the chord pad was created. I see what you mean about large voicings, and I’ll see if I can find another display method. I just didn’t necessarily like scrolling around on a piano, so on larger screens I prefer seeing everything at once. Let me know if you have any ideas about that.

  • @craftycurate

    However, this is by no means the only way to make a pad, even in previous versions. Did you try the “create custom pad” option at the bottom? This allows you to put in any notes you want with no restriction.

  • edited November 2019

    @TonalityApp said:
    @craftycurate The reason most pads are restricted is that there are so many chords you can usually find one using the keyboard to search, and this allows you to have an idea of the harmonic structures you’re working with.

    However, this is by no means the only way to make a pad, even in previous versions. Did you try the “create custom pad” option at the bottom? This allows you to put in any notes you want with no restriction.

    With regards to the inability to edit wide voicings, what happens exactly?

    I’ve been using the Custom Pad option. So for example

    1. Create Custom Pad
    2. Enter Dm triad
    3. To extend the chord, I have to select one of the notes and use the Octave buttons, to force the keyboard to expand.
    4. Now I find I am not able to add notes that did not appear in the original note section. This is a huge problem. If I decide I want to make it a m6, I can’t because I can’t add B
    5. If I select every note in the first screen to get round this, the app says “that’s quite a chord you’ve got there”, and refuses to let me proceed.

    The chord voicings I use for ambient music are complex and extended and they need to be easily entered and edited.

    All I need is an editor that is really simple I.e. it lets me easily create custom chords with exactly the notes I need and places no restrictions whatsoever on that choice. I am still quite new with this app, so I apologise if it already does this, but the Chord Pad AUv3 doesn’t seem to let me do this at the moment. It looks like a great app for exploring chords generally but maybe I’m trying to make the app do something it’s not designed for?

  • @TonalityApp said:
    @craftycurate The reason most pads are restricted is that there are so many chords you can usually find one using the keyboard to search, and this allows you to have an idea of the harmonic structures you’re working with.

    With regards to the inability to edit wide voicings, what happens exactly?

    Edit:
    With regard to your most recent edit, the ability to add and remove notes will remain no matter how the chord pad was created. I see what you mean about large voicings, and I’ll see if I can find another display method. I just didn’t necessarily like scrolling around on a piano, so on larger screens I prefer seeing everything at once. Let me know if you have any ideas about that.

    Thanks for your quick responses. I nearly missed this update as it’s an edit to an earlier comment. Taking your points in order:

    I'm not sure I follow. I am sure I wasn't able to add notes to a chord in the voicing screen that were not selected in the initial one-octave note selector. Is this correct? If so, could this restriction be removed in Custom Pad view, or maybe add a toggle in the voicing screen to say "allow all notes" or "restrict notes to selected chord" or similar?

    If the keyboard was restricted to 4 octaves (or even 3), with some kind of scrollbar or < and > buttons to jump octaves that would be fine, as long as the octaves were clearly labelled with C1, C2, C3 etc underneath the notes.

  • @craftycurate
    Ahhh okay, I see what you mean, and actually accounted for it in the next update that’s out already! :D As of 6.3 you can add whatever notes you want even after selecting some on the first page (I might get rid of the first page entirely in the future). I thought people would know going in what notes they wanted, but it makes sense to want to extend it later on. This has been fixed!

    The “that’s quite a chord” prompt shouldn’t disable going on... did you maybe forget to add a label? That’s the only thing that should prevent moving on.

    For something like a Dm6, though, why not use that chord from the list of built in ones? Is it because you might like to extend it later? If so that makes sense and I will probably add an option to allow non-chord tones for built in chords as well as custom ones.

    One last thing - instead of having to move a note up or down to force the piano to display more octaves, what would be your preferred workflow?

    Thanks for the detailed responses!

  • @craftycurate said:
    I'm not sure I follow. I am sure I wasn't able to add notes to a chord in the voicing screen that were not selected in the initial one-octave note selector. Is this correct? If so, could this restriction be removed in Custom Pad view, or maybe add a toggle in the voicing screen to say "allow all notes" or "restrict notes to selected chord" or similar?

    Just got to this in my comment above (it's in 6.3)

    If the keyboard was restricted to 4 octaves (or even 3), with some kind of scrollbar or < and > buttons to jump octaves that would be fine, as long as the octaves were clearly labelled with C1, C2, C3 etc underneath the notes.

    And there's my answer to the question I asked in the comment above.

    We need to time this better :D

  • edited November 2019

    Thanks again for your prompt responses and openness to new ideas.

    @TonalityApp said:
    @craftycurate
    Ahhh okay, I see what you mean, and actually accounted for it in the next update that’s out already! :D As of 6.3 you can add whatever notes you want even after selecting some on the first page (I might get rid of the first page entirely in the future). I thought people would know going in what notes they wanted, but it makes sense to want to extend it later on. This has been fixed!

    Excellent - will look forward to it.

    The “that’s quite a chord” prompt shouldn’t disable going on... did you maybe forget to add a label? That’s the only thing that should prevent moving on.

    Have just checked - I made sure I'd added a label this time and was able to proceed with all notes selected. Sorry it's late here :#

    For something like a Dm6, though, why not use that chord from the list of built in ones? Is it because you might like to extend it later? If so that makes sense and I will probably add an option to allow non-chord tones for built in chords as well as custom ones.

    In this case, the Dm6 chord was just used as an example of not being able to add "off chord" notes in the voicing screen.

    One last thing - instead of having to move a note up or down to force the piano to display more octaves, what would be your preferred workflow?

    Ideas:

    • Have a "number of visible octaves" setting with +/- buttons, or 2 sets of +/- buttons, one to move each end of the keyboard by an octave
    • < and > buttons to shift the view by an octave
    • Maybe for "Custom Pad" the view could jump straight to what is currently the voicing page, with default of 3 octaves and no note restictions
    • Maybe long press on a note to drag it to a new location, or quick delete

    Thanks for the detailed responses!

    No worries - it's in all of our best interests to work with devs to help their apps be even more awesome :)

  • @TonalityApp said:
    We need to time this better :D

    Ha - our messages are crossing in the ether!

  • @craftycurate Of course! The whole goal here is to make it useful for people after all. I definitely appreciate the input; I'm always so focused on maintenance and features that it really helps to get an outside perspective on usability.

    Great ideas for editing! I'm already planning on skipping straight to the edit page for custom voicing, and I really like the other things you listed. I'll keep you updated!

  • @TonalityApp said:

    @craftycurate said:
    I'm not sure I follow. I am sure I wasn't able to add notes to a chord in the voicing screen that were not selected in the initial one-octave note selector. Is this correct? If so, could this restriction be removed in Custom Pad view, or maybe add a toggle in the voicing screen to say "allow all notes" or "restrict notes to selected chord" or similar?

    Just got to this in my comment above (it's in 6.3)

    If the keyboard was restricted to 4 octaves (or even 3), with some kind of scrollbar or < and > buttons to jump octaves that would be fine, as long as the octaves were clearly labelled with C1, C2, C3 etc underneath the notes.

    And there's my answer to the question I asked in the comment above.

    We need to time this better :D

    Hey buddy just want to say thanks, you have been the only developer I have found that is on top of every suggestion that us customers come with and no only that but your responses come quick and to the point. I bought the app even if I don't really know how to use it just to support you and I paid full price for it. You deserve to be successful with Tonality and any app you develop in the future if you are going to behave this way always. Thanks a lot

  • Just grabbed this, so my issue may be user error, but I'm experiencing a crash when trying to use 'MIDI Learn Mode' in Cubasis.

    1) Open Cubasis
    2) Add Chord Pads to a track
    3) Enable 'MIDI Learn Mode'
    4) Hold Pad
    5) Play a chord
    6) Plugin crashes...

    Latest OS and app v6.2.1 (Build 74)

  • @Prog1967 Thank you for the kind words! Let me know if you have any questions.

    @blakkaz Crashes are never user error. Let me look into it (I don’t have cubasis but I’ll see if any other hosts have that issue).

  • @Prog1967 said:

    @TonalityApp said:

    @craftycurate said:
    I'm not sure I follow. I am sure I wasn't able to add notes to a chord in the voicing screen that were not selected in the initial one-octave note selector. Is this correct? If so, could this restriction be removed in Custom Pad view, or maybe add a toggle in the voicing screen to say "allow all notes" or "restrict notes to selected chord" or similar?

    Just got to this in my comment above (it's in 6.3)

    If the keyboard was restricted to 4 octaves (or even 3), with some kind of scrollbar or < and > buttons to jump octaves that would be fine, as long as the octaves were clearly labelled with C1, C2, C3 etc underneath the notes.

    And there's my answer to the question I asked in the comment above.

    We need to time this better :D

    Hey buddy just want to say thanks, you have been the only developer I have found that is on top of every suggestion that us customers come with and no only that but your responses come quick and to the point. I bought the app even if I don't really know how to use it just to support you and I paid full price for it. You deserve to be successful with Tonality and any app you develop in the future if you are going to behave this way always. Thanks a lot

    +1 👍🏻

  • @blakkaz Okay when you say hold a pad is this an empty one or one with a chord assigned? Midi learn mode is for setting single note triggers, so only one note should be assigned. However it shouldn’t crash for more than one note (for example in AUM it just sets the trigger to be whatever note is sent first). I’ll have to look into this.

    The midi mode I think you’re looking for (assigning a whole chord to a pad) is in 6.3

  • Yeah, it seems I misunderstood what MIDI learn was for.

    It works perfectly when used as expected.
    But will crash if a chord is not already assigned.

  • @blakkaz said:
    Yeah, it seems I misunderstood what MIDI learn was for.

    It works perfectly when used as expected.
    But will crash if a chord is not already assigned.

    Ugh must be something I overlooked when I was trying to get the 6.2.1 patch out quickly the other day. Sorry about that. I know it’s fixed in 6.3

  • Apologies to everyone about the bugginess of the 6.x releases. Shouldn’t happen again

  • edited November 2019

    Cheers.

    It looks to be a very impressive app.
    I jumped in based on the price without really knowing what it actually does... :D

    My first impression is that some initial music theory knowledge is required to get the most out of it?
    I guess I was hoping I could just give it the key of my song and it could suggest some possible chords.

    Perhaps something to consider for a future update?

  • @blakkaz said:
    Cheers.

    It looks to be a very impressive app.
    I jumped in based on the price without really knowing what it actually does... :D

    My initial impression is that some initial music theory knowledge is required to get the most out of it?
    I guess I was hoping I could just give it the key of my song and it could suggest some possible chords.

    Perhaps something to consider for a future update?

    This would be great

  • @blakkaz Yeah parts are designed to be learning tools, but it becomes more powerful the more you know. Definitely something I’m considering. For now I’d recommend Suggester, which is another good app that, well, suggests chords.

    One thing you can try in Tonality though is the scale chords presets for the chord pads. They allow you to select a major or minor key from the circle of fifths and then have an auto-generated layout with some chords that “belong” in the chosen key. Let me know if you have questions as to how this works.

  • @TonalityApp, any plans to expand on the scale chords preset? A progression generator would be really cool where you pick a scale and it can generate some progressions to spark ideas. I’d even grab that as an IAP cos I could see where that could take a lot of work

  • @JackDwyerburger definitely. I’m probably going to fix some of the other stuff first though. Check out Suggester in the meantime!

  • @horsetrainer @craftycurate Has 6.3 showed up for you? It’s been approved by Apple and says it’s out but some of my test devices don’t seem to think so. I’m pretty frustrated with the App Store at the moment

  • App reviews are usually much slower during holidays so that might be why

  • @yowza It's not the review process though; it's already been approved by the review team.

  • @TonalityApp said:
    @horsetrainer @craftycurate Has 6.3 showed up for you? It’s been approved by Apple and says it’s out but some of my test devices don’t seem to think so. I’m pretty frustrated with the App Store at the moment

    I got the app pretty much due to your responsiveness in here and the general discussion, without actually having a plan for my usage of it, though I suspect I'll be using it in parallel with Suggester (which I already had).
    Just to confirm though: in the Swedish AppStore I just bought 6.2.1, so 6.3 is not here just yet.

Sign In or Register to comment.