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
Also free: https://apps.apple.com/app/audiofile-calc/id337547274
hit the "write" button during playback.
I read the description and I cannot make heads or tails out of what this calculator is used for. I guess if I knew, I'd probably already be a customer of such an app. (shrug)
I didn’t even really read the description but immediately (by the screenshots) knew that I could figure out things like how long a song is if I have X bars and Y tempo. Not everyone needs that but I’ve had to make that calculation.
It's just a bunch of utilities for figuring out music related numbers. Like in the case where you want to sync a delay that's only in ms, or calculate the size a wav file will be at different sample rates and bit depth.
You mean to tell me that you don't need to know such things as knowing that 1ms latency is the same at 1.1 ft from the source at 70℉ and 50% humidity, but a whopping 1.2 feet at 85℉ and 98% humidity??? 😉
😂
Thank you Mister Jackson.
Thank-you very much for the OPTIONAL tempo sync @Rob_Jackson_Music ! 🙏🏼🙂👍🏼
I promise not to over-use synced mode.😉
(I personally wont use the temp synced option much, because it sorta puts the breaks on the length control, and that length control is the for me the most fun, expressive, pull-me-push-me control at the core of this very nice synthesiser it gives its unique feel and sound. It is good to have the option though, opens up other arrangement options.)
Cheers
Cheers @RiverbendSim
I also wanted to put a slightly different spin on it by having optional pseudo random note lengths across all 8 voices. Plus you can drift those values if you want to humanize it, so to speak.
Have to say though, my favourite new feature to test was poly aftertouch - worked really well for me with Animoog
Ooooooo I am for reeeal
Never meant to make the AppStore cry/ I self-oscillate a trillion times
Thanks for the tips Rob.
I will play with those drifty human values next time I take it for a spin.
Which will be just after my next coffee. 🙂☕️🎹🎶👍🏼
Multi layers of different internal delays, with a drift away robot, is really lovely so I will use the sync options more than I thought. 👍😀
Unfortunately none of my controllers has decent aftertouch abilities so I can’t explore the poly aftertouch.
Anyway, thanks again for the update.
Oooh thanks so much for the sync update. I can’t wait to try it.
You can use that Midi Poly Grid app as a poly aftertouch controller, Sim!
Full mpe for all synth apps would be the ideal, mind you:
https://apps.apple.com/us/app/midi-poly-grid/id1633882803
Cheers Gav.
I haven’t had a proper look at Midi Poly Grid yet. I have a couple of controller/pad apps that I quite like, but find myself not using because they are not Auv3, and I thought it might become another one of those…
Currently have an AUM project open with WoodTroller and Velocity KB hooked up to AnalogyGR and that’s pretty fun to play with. 🙂
Oh, @Rob_Jackson_Music , what do you think about maybe changing the colour of the word “Length”, or putting a midi-locked icon or something, when sync is activated? I just find myself wanting a visual indication of when my hand-brake is on. 😀
Yep, it could probably do with something like that - noted, thanks!
On a separate note (no pun intended...), shame the AUM and GB keyboards don't support virtual poly aftertouch. Not that hard (imho) to implement really. I struggled to find a suitable app to test with, then remembered Animoog (and Z) can send it.
For anyone else interested in the new expression stuff that doesn't have ANALOGyGR, it can be mapped to the mod wheel if you don't have channel or poly aftertouch. Personally, I prefer the mod wheel over channel aftertouch as every hardware channel AT keyboard I've tried, always feels a bit on / off with not much inbetween to me... It's part of the reason I added the expression Smoothing parameter.
When I first started ios music, I gobbled up all the free apps I could (like everyone I’m sure) and most got forgotten along the way, but I just recently came across these NOISE apps while scrolling midi stuff in AUM. NOISE melody is a keyboard that I thiiiiink has MPE/after touch? Can anyone confirm? And I’m assuming you can use that for free with the features mentioned?
I think you’re right @Squishy 👍
I’ve hade Noise Melody for years but never thought of loading it as a MIDI Processor and using it as a keyboard. Seems to work fine with GS Naada instruments which are MPE. Not got round to buying Robs app yet 🤔
Unfortunately the Noise apps are abandonware (wish ROLI would resurrect them) and I’m not sure they are available anymore.
If only there were some kind of MPE controller app with a multi-touch based interface with "radar", "ribbon" and keyboard surfaces. Maybe something where you touch the screen to play a note, move your fingers to change the sound. Now that would be something 😉
On a serious note, would you consider making another controller app @Rob_Jackson_Music ? Touchscaper really is one of my favorite apps - a revamp with auv3 support would be an insta buy for me (though at this point all your apps tend to be insta buys for me). I’d be happy for a Touchscaper iap for auv3 support.
Yes, I’ve thought so many times that there is a great need for a truly performance focused, flexible, MPE controller app that’s AUv3. There are various options, some better than others, none perfect.
@FizzyLizzy27 - thanks! Sadly, an AUv3 version of touchscaper would be more than a revamp - more like a total re-write for various technical reasons.
That said, I have been thinking (a lot...) about revisiting the idea of controller / performance-oriented apps. Watch this space...
@Gavinski you probably picked up on it, but I was directly copy/pasting the App Store description for Touchscaper. Not sure if you’ve used that, but it’s a great controller. I don’t see any of your videos covering it, and I see you talk a lot about unique MPE control apps. It’s only IAA but it seems up your alley.
@Rob_Jackson_Music I figured an auv3 revamp would be a lot of work - I’m glad to hear you’ve been considering something in that realm
In keeping with your simplified approach, I hope it's one-finger only, with lots going on under the hood to make it sound like someone playing with all ten fingers. 😉
My! What a genius plot twist the per voice delay parameters are. ❤️❤️❤️
Don’t understand ‘em and hope I don’t ever fully, so as not to ruin the fun. 😎
I have to take the chance to let you know that TouchScaper is one of my very very favourite apps too, and like most of its fans I would dearly love and Auv3 version.
(I would actually like TouchScaper to be the host).
It’s a very beautiful instrument. Thanks for making it. 🙏🏼
I had a heap of fun today testing various Auv3 controller apps with AnalogyGS.
My favourites were ChordPolyPad, or the xy pad in LK.
Not quite MPE, but very expressive MIDI.
I’m going back for more. 🙂✌🏻🎶
Many thanks folks - much appreciated!
So...
MPE
Just wanted to also take the opportunity here to respond to questions, suggestions and, ahem... slightly outdated assumptions regarding MPE, and why GR doesn't currently support it.
In case you don't know, since the last time I looked at MPE (around 5 years ago) a new 1.1 spec was published in April 2022. If you want to get into the weeds, it's on MIDI.org.
https://midi.org/mpe-midi-polyphonic-expression
The biggest change is basically this:
The specification describes a recommended way of using individual MIDI Channels to achieve per-note control without requiring Mono Mode (which would restrict polyphony to a maximum of 16 notes). This enables richer communication between increasingly expressive MIDI hardware and software.
I'd wager that just about every controller and synth app currently available on iOS that supports MPE is using mono mode, i.e. voices are adressed on a MIDI channel basis.
The new spec also introduces a new, and imho, complex configuration message which I suspect would be a huge breaking change for the way many developers have interpreted the more... err... open to interpretation 1.0 spec
When developing GR, I took the view that given the development effort required to support the new spec, vs. GR only being an 8 voice synth, that it just wasn't worth it, given that the additional development time would have to be reflected in the app price.
I also took the view that poly aftertouch was a decent compromise for note / voice level expression, especially due to the macro-like parameters, and GR was designed from the get-go to support it.
I guess it remains to be seen how many developers will embrace the new 1.1 spec, but personally, I'm not interested in implementing something that was superseded 3 years ago in any new apps
I'm still a bit on the fence regarding supporting MPE generally, especially as this new spec adds several layers of complexity to something that's probably best described as a bit of a bodge... And of course MIDI 2.0 kinda blows the whole expression thing out of the water anyway...
Hope that makes sense and you see where I'm at re MPE.
EDIT for accuracy I was wrong. The original spec 1.0 was published in 2018 and updated in 2022. Doesn't look like many developers have adopted the additional configuration message.
Thats just not true. Please note the following from the description of 1.1 on the official website:
"M1-100-UM MIDI Polyphonic Expression is a version 1.1 update which replaces the previous rp53 version 1.0. Version 1.1 has significant editorial improvements for clarity but has no technical design changes."
No technical design changes since official 1.0 release. They just fiddled with the wording in certain sections.