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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Comments
@Krupa
I’ll add that tuning to my list for the next update then!
Does the “scale chords” list that comes up when you tap on a harmonic minor scale in the scales tab show what you’re looking for?
That’s wonderful, thank you, and yes, you’re right, just getting to the scale and then using the ‘scale chords’ bit is pretty much identical to what I was thinking - it took a me a moment to find it but it was in the ‘focus’ mode of the circle’s that I was thinking, but it’s probably all best left as it is
nice one 👍
@TonalityApp The more I think about it I do feel that the Chord Pads could use a 'midi thru' function?
The Chord & Scale Identification and Grand Staff AUv3's already have this 'midi thru' functionality in place!
By giving the Chord Pads 'Midi Thru' it would simplify midi-routing by allowing the user to send the actual chord directly to the destination without having to route both the 'Keyboard' and 'Chords & Pads' to the destination to 'preview' the chord before assigning it to the pad. (ie. just route the keyboard to Chords Pads and route Chords Pads to the destination).
And maybe the 'Chord Indentifier' module could be integrated to the Chord Pads module when adding new pads?
(ie. tap + and the 'Chord Identifier' could be used to detect the notes that are being played and allow quick assign to the pads?).
When the keys are shown in the Chord Pads the currently detected scale & chord could also be shown?
(This would make it a lot easier, eat least for me to memorize chords that 'sound good' to my ears?!).
Needless to mention but Tonality is my go-to app for triggering chords and has become one of my essential tools.
Cheers!
I would throw a big +1 on both ideas of the midi thru and incorporating the chord identifier into pads.
Could see it really helping with workflow and making it easier to enter/edit chords on the fly
Really surprised how much I use this app already though. Nabbed it on a whim while it was on sale just to try the chord pads but it’s been sooo much more useful than I would have ever thought. Love your work ❤️
@Samu @gusgranite Hey! Have you tried the quick assign mode? You can hold down on any pad and incoming MIDI will be used to set the chord (it will be identified as well). By default the border of the pad turns red and the tentatively identified chord will display until you tap the pad again to commit it. There are a few more options and nuances described in the chord pad settings – let me know if anything is unclear or if this isn't the workflow you had in mind. Another option would be to open an instance of the chord ID and just use drag and drop on the chords that come up (hold down on the chord label on the left). I'm happy to discuss more, just wanted to see if any of these existing options work first.
MIDI thru can definitely be added – just stuck it on my list.
Edit: here's an outdated demonstration. The process is a bit better now but hope this gives an idea of what I'm talking about.
I use the 'quick-assign' most of the time, the detected chord is just hidden under my finger before I lift it
Sometimes I use the 'Manual Mode' with 'Remove in Quick Assign' enabled and long-tap on the pad to add notes.
This way I can see the chord and when Midi Thru comes it'll be perfect!
Thanks, that will make it easier to actually 'hear' the chord when adding new pads
The main reason I wished for the chord detection to be always active when the keyboard is shows was simply for ease of use.
My music-theory is still very lacking so a feature that detects the scale based on added chords could also be handy?
(When tapping the 'Choose a Key' it could have a 'detect key based on current pads'?).
In the stand-alone there's the nice 'auto strum' on guitar chords (the little play button) that could be nice as a performance option for the pads? (It's a bit different that the randomize attack and velocity currently available for pads).
And since there's a LOT of settings in the AUv3 it could be nice to have some kind of 'save as default' that would be used for new instances.
And one last thing (for now) an option to send the 'scale selector' sound to the midi output instead of using the built in LOUD e-piano sound (It always scares me LOL).
Feel free to add if it makes sense, but you don't have to...
Cheers!
@TonalityApp you might have tagged me by accident but I like it! 😃
Yeah no idea how I managed that, my apologies!
Ahh gotcha. Where would you envision the chord detection displaying on screen? I like these other ideas too - once again adding them to my ever-growing list
Above the piano keys when the keyboard is shown.
That area (the red square) could be used as 'status display' or something similar?
Cheers!
Yeah that could be cool, kinda like the display in Logic. It causes some difficulties with small window sizes (a lot of people like to use the AU at the smallest possible size), but I'll think about it.
Thanks for answering the questions! I found the answer to mine right above here
Hey all! Finally had a bit of time to implement some of the smaller feature suggestions. @Krupa, @Samu: the latest beta has the DADGCD tuning, MIDI thru in the chord pads, and stops playing the internal piano in the AUv3 circle of fifths selector.
It also (optionally) allows you to view the Forte number, prime form, and interval vector of any chord or scale (even if it's not in the database). Atonal music concepts sure lead to a lot of new feature ideas...
Hope to get around to more suggestions soon(ish)!
Nice one @TonalityApp , that’s amazing, great to see what I’ve been figuring out in my head laid out so clearly!
Thank you 🙏
btw, did you name that tuning yourself or is that a recognised nomenclature? (D7sus4)
Glad you find it useful! I ended up naming it myself because I couldn't find any standard nomenclature. I'm happy to change it if you have one though
The latest beta overhauls accidental handling throughout the app, so no more duplicate enharmonic results. Instead, there is a toggle to set the "disambiguation accidental" which will be used if #/b cannot be determined from context. A nice side effect is that transposing chord pads will display roots appropriate for the current key (if one is set). If you get a chance let me know how it works for you! There may be a few kinks to work out so also let me know if anything seems off. Note that some results may be unexpected initially (for example, if you search for the root A#, A#m will appear but the major chord will show as Bb unless you have theoretical keys enabled. I like this better than the old behavior of just not showing the major chord at all though.)
The option to show only unique "parent" scales is next – any ideas for icons representing this feature? I'm also thinking about a setting for the "exact match/bullseye" toggle in which searches that match everything except omittable notes will still show up.
It’s a great name, I’ll help me to just have that as a label in my mind
Anyone else have trouble seeing Tonality in AUM? Even after a restart? Just doesn’t appear.
Are you sure you're using a 'Midi Track' in AUM?
ie. in AUM create a 'Midi Track' then select Audio Unit Midi Processor and you should see them.
If you create an 'Audio Track' you will not see them...
Ooof! There it is! 🙏
Tonality v9.0 is now available! Highlights include:
As always, let me know if you have any questions or issues. I still have a long backlog of feature requests, but I am working on them!
Thank you for the huge update! 🙏
I have a request : would it be possible to add a guitalele tuning ADGCEA ?
Thank you!
Very welcome and sure! Pretty soon I'll just allow for arbitrary custom tunings
@TonalityApp SUPER!
As an aside would you look at Chordez (IAA app) and see how you might include easy access to chord subs and other additions. NOT to say you haven’t incorporated some. I just like how they’ve handed ALL the chord substitutions. Much love for what you’ve created
I haven’t followed this thread for nearly a year, and saw Tonality just received a major update.
Are any of our AB Forum YouTubers planning a guide to the upgrade? It seems like a subject worthy of a deep revisit!
Thank you for your tireless work on this, @TonalityApp!
@audiblevideo Definitely! I still want to redo a lot of the chord pad editing workflow, including how it handles alterations/extensions/substitutions and scale chords/borrowed chords. Thanks for the tip!
Welcome as always!
@TonalityApp Thank you so much! 😃
Custom instrument/tuning creation is now available!
Additionally, the preset browser has been improved and you can now export an entire pad set as a MIDI file. Section markers (verse, chorus, etc.) can be added to pads from the voicing editor.
Wow the app that keeps on giving, possibly one of the best purchases I’ve ever made.
@TonalityApp I think I've bumped into a glitch with the Chord Pads AUv3.
It seems that the setting for 'Include secondary dominants' is 'sticky' during a session?!
Meaning if create a set with the secondary dominants and then try to create a set without them they are still created?!
I need to un-load and re-load the Chords & Pads AUv3 in order to be able to create a set without them...
Not a biggie but still a 'glitch'.
Looking forward to the additional AUv3 with circle of 5ths, all chords in one place will be super nice
Yup, thanks for the bug report. I'll fix it soon.
Glad you're liking it so far!