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.
MemoToMIDI — sing or play an idea, get MIDI. Testers wanted.
Hi all — I’ve been lurking a bit — first post, first app. I’m looking for a handful of testers for MemoToMIDI (iPhone/iPad). It turns a quickly captured musical idea into a MIDI file you can drop into your DAW.
More:
Record a voice-memo-style take (instrument or hummed/sung line), and it transcribes to MIDI on-device.
The transcription can be pretty great on clean performances in quiet rooms, but there’s always a little something to tweak, so a big part of the app is a piano-roll style editor where you can compare your audio to your MIDI and clean up a take fast: nudge/resize/split notes, adjust detection sensitivity and mode per take (poly/mono/voice), quantize (globally or per note), transpose.
Export a standard .mid via the share sheet into Logic, Cubasis, GarageBand, Loopy Pro, wherever.
Everything runs on-device and offline — no account, no upload, nothing whatsoever leaves your phone.
fighting these screenshots a little..
What it is not (yet): it won't magically nail every note of dense polyphonic material, and vocal takes are a little rougher than plucked/keyed instruments. It doesn’t do bends or anything like that. You figure out what it does pretty quick and you play into it. If most of the notes land and fixing the rest is faster than entering them by hand, you’re using it right.
If you've tried audio-to-MIDI tools before and find yourself skeptical about another one, I get it — I've tried them too, and I was a little disappointed. I'm not going to claim perfection, here; I'll just say the way I have engineered this thing works better than the others I have tried, and I would genuinely rather have skeptics in this beta than family and friends. Bring the take that broke the last tool you tried? I genuinely want to know if it breaks mine, too.
Beta vs. launch… so nothing surprises you: the built-in preview sounds are plain soundfonts right now, with a few very basic synth patches mixed in — I think they're getting replaced with something as useful but more economical and hopefully a little nicer sounding. That’s the biggest gap between this build and the finished app, I think. Judge the notes, not the tone. Also, everything is unlocked in this beta; at launch, recording and editing stay free and it's the MIDI export that becomes a one-time purchase (no subscription).
For the technically curious, a few things under the hood I haven't seen elsewhere: the whole pipeline is native Swift running on-device, with the pitch model converted to Core ML (I haven't found another Swift-native implementation of this model — it's why the no-network claim is possible at all). Basic Pitch is awesome but it has mushy timing, so a separate transient/onset analysis pass maps each MIDI note back onto the actual attack/onset in the audio — the note starts where your finger or pick did, not where the model's frame grid landed. The timing sounds a lot more faithful than other tools I have tried. Quantize doesn't need a fixed tempo either: you tap/map the beat of your take (or record against the built-in click if you like…no headphones needed, the click doesnt bleed into the midi) and the app uses the beat map to warp midi onto a straight grid, making further quantization possible. Happy to go deeper on anything if anyone cares.
What I'm looking for: not install numbers — a handful of people who'll run the honest loop and report back. Three steps: capture a real musical idea, clean it up in the editor, export it and open it in your DAW. Then tell me where it fell down: notes it got wrong that were painful to fix, edits that fought you (there’s a tiny thing with moving a transposed note which is pretty annoying right now. I just saw it), exports that didn't behave in your host. That's the whole ask. There's a beta only report button in the export tab which sends me a whole blob including your recording so I can diagnose anything you think I should look at.
Beyond just the loop: this app got a long way without much outside feedback, because for most of its life I was just building it for myself after waiting years for someone else to do it — it only recently turned into something I thought I could share. That means this is pretty much the only chance anyone's had to tell me what it should really be, or what makes it useless, etc. So beyond the test loop above, I'd love to hear ideas that are nothing like what I've built — different takes on the capture-to-MIDI problem entirely. What would be clever? Whatever, I’m all ears. This thing really works for my purposes but I'd love for it to do more.
One thing I'd rather say up front than try to hide, because I know people care: I built this solo, and I’m a pretty slow coder...I only finished it this decade, because I used AI heavily over the last year— for code, for the manual, for a lot of work. I can’t lie…I’m so impressed by this evil technology and I kind of hope it can save us from ourselves, but I digress…For now, I couldn’t outsource myself… My judgement was still really important through hundreds (thousands?) of commits, endless tweaking, dead ends, etc. I guess I’m just saying it was still a ton of work. Also, the cleverest ideas were mine, I swear it. I’ll take any questions about this AI stuff. Convince me to cut it out…whatever.
There's a full manual at memotomidi.com/manual if you want some details.
TestFlight link: https://testflight.apple.com/join/yS2CYME1
Thanks for reading the essay. Get in touch!
James
Comments
love the concept, gonna try it out!
Is it an AUV3? Can I run it in Loopy Pro? Forgive me if you stated somewhere and I missed it.
Welcome @JRJRJR
This sounds very interesting, can’t wait to test it out. Cheers and congrats on the creation.
Nothing in the description to say it is but that's what it needs I think to make it a genuinely groundbreaking app - @JRJRJR ?
Is it vibe coded? Apologies for asking if it's not!
I've started work on this, and it works. I don't know how long it will take me to get it into your hands, though. I really want to get iPhone/iPad polished, first.
Yes, in the sense that I absolutely used claude code and codex while I built this thing, but no in the sense that I wasnt writing specs and then having AI build it overnight. This was a pretty painstaking engineering task that involved really intense iteration and QA. When there were shortcuts that didn't affect quality, I took them, but a lot of the time there was no shortcut. ~1400 commits, and I kind of suck at saving. I'm not offended by the question at all. I'm interested if the AI use offends people.
This is just the kind of thing I've been looking for. Sadly the beta on test flight is full. Any chance of squeezing in another?
As for vibe coding questions that pop up on the forum a lot nowadays, I feel they are often a little un-nuanced (not aimed at you @mistercharlie ). For a forum full of people who use software to aid in the production and composition of music I'm not sure what the specific issues are with assisted coding for apps. I am sure there are some but better to focus on those I would suggest. Apologies for the sidetrack!
Oh wow that filled up quick. Killer! I just increased to 50.
It’s partly about the quality of the code, and that many (or most?) vibe-coded projects get abandoned quickly.
But it’s mostly the ethical and environmental problems. Huge water and power use, when the climate is already hurting. And it’s all trained on stolen work, without permission. And it’s also clearly a bid for both control of information to the masses (us), and breaking labour (also us).
That’s why I will keep asking whether folks are willing to ignore all of that to make their coding projects a bit easier.
Thanks so much. Keen to have a play with this!
I hear you in part but I think the whole thing is far more complex than that. Also there are some double standards at play in using the technology many of us do (to produce music) and ignoring its own environmental impacts. And are you saying that AI assisted coding is using stolen code? Please note, I'm not trying to be atagonistic or oppositional here, just interested in there debates around this stuff. Also not hung-ho on AI and not interested in pure gen AI as such, but I do feel that aspects of the tech are useful. And @JRJRJR my apologies for derailing your thread. Will shut up now and save this for another place
Cool app and concept. I just downloaded and did a few tests inside the app, have not exported anything yet.
Housekeeping type thing, if you are zoomed in on the piano roll, would it be possible to navigate or adjust the playhead position with the top wave area?
Maybe a long press on the waveform to zoom for adjusting? zero crossing detection and transient snapping?
Also with the groove beat timing area, it would be nice to be able to adjust the beat markers. maybe have a transient detection in that area to?Also it does not refect the wave area if you have adjusted it in.
Last thing, have you thought about this for drum grooves? maybe being able to tap out a drum groove in your app, then export or adjust the midi for GM drums?
Great start.
It’s that all LLMs are trained on stolen data/art/etc. All of them.
FWIW I don’t use any LLM based tools, and I really think that everybody else should do the same.
If you do use them, then you are agreeing that it’s ok to build out huge data centers, waste water and power, and that it’s ok to train those models on people’s stolen work.
IMO you cannot use them and also claim care about the environment. It’s like being a vegetarian and still eating battery eggs.
You are literally typing this out on a device whose manufacture and parts have caused air pollution, water pollution, depleted rare earth minerals and greenhouse emissions. As am I
Agreed on the wave navigation. I immediately went to use it as a possible lateral navigation element.
I'm assuming the bottom menu is supposed to disappear when in landscape mode? I went to landscape mode when on the export screen as I couldn't read the middle button.
Only had a very quick play on the phone but I think this could be a super useful and functional tool.
I guess the main thing for me is that it doesn't make my coding projects a bit easier--it makes them possible. This is a transformative technology for me, and I'm not sitting it out. I literally haven't driven a car since I got a license 31 years ago, for exactly the kinds of reasons you list. All that public transit. The walking. I rarely left the city. Now, the forest fire smoke is blocking out the sun over Toronto, here in 2026, so I'm not sure what I accomplished, but it still feels like I did the right thing. You should, too, if it's the right thing. It's a weird thing for me to be on the other side of things, from your perspective. For my part, I believe something pretty dramatic is going to have to happen on planet Earth to prevent total ecological collapse in the next century or so. AI is the only thing I can seriously think of that might do it without apocalyptic things happening. Maybe with AI we at least get to live in a zoo? I'm not making jokes. It might be just like that. Bleak.
Anyways, I don't think MemoToMIDI is going to change the world, but it has proved something kind of cool about what AI makes possible for a person like me. I can't remember ever having momentum like this, and I swear to god I have a repo called save-the-planet. If AI can facilitate that for me then imagine what it can do for a climate scientist or god forbid some policy maker. I gotta watch it on this topic, though...I get worked up and pontificate.
Just know I respect your take. I should address the stolen work thing, too. I think the main thing there is I think if they stole all that work they should be prosecuted, not me? it's kind of deflecting, I guess. I'll think about it.
Thanks for that idea, guys. Definite yes!
Yup, on iPhone the bottom panel disappears in landscape for more piano roll. For a long time that was the only way to edit.
This just gave me a simple idea which might be useful...Im gonna make one of the scale lock settings just be one pitch so you could drop it into a drum track. Neat! But also, meet a very early stage "TapToMIDI". You tap a surface near your phone and get a groove with velocity already baked in:
Love this idea!
I would like the record button to be red, and maybe be labeled "Start Rec" or something similar. I wasn't sure if it was recording initially since there was movement on the graph so it seemed like it might be recording, but it wasn't.
After a quick test, it seems pretty responsive, had to move and delete a few notes, but the audio to midi seemed pretty good. Ill have to continue testing it, but so far, so good.
Build 1.0 (9) is up — should be in TestFlight now. Mostly built from this thread:
Waveform playhead navigation — you can now tap or scrub the top wave area to move the playhead, zoomed in or not, landscape included. @TheAudioDabbler asked for this and @Cambler seconded it — thanks, guys
Recording screen reworked — clearer about when you're armed vs. actually recording, better guidance in Free mode. @bigcatrik, your record-button feedback drove this. The recording and beat-tapping flows are still getting iteration — better than before, not finished.
Proper iPhone landscape layout for the recording screen — no more clipped controls, and it mirrors to your handedness setting.
Beat Timing: waveform taps count — taps on the wave area now register as beat taps during capture instead of being swallowed. (@TheAudioDabbler — fuller beat-marker editing is still on the list.)
iOS 27 beta crash fixed — opening a clip could crash on the 27 betas. Thanks to the two of you whose crash reports made it reproducible.
Stability — moved notes under transposition now land where you drop them, interrupted recordings save the take instead of corrupting it, and memory fixes for big imports.
Not in this build: AUv3 (@Vmusic, @charalew — in active development), transient snapping and drum-groove tapping (@TheAudioDabbler — on the backlog). And one honest note for @Cambler: the landscape thing isn't really fixed yet — if your results open in landscape you just see the piano roll, and nothing tells you the Detect/Groove/Export tabs are waiting in portrait. A proper hint, at least, is coming next build
If you've got ten minutes: try the waveform navigation zoomed in, and do a full record → edit → export pass in landscape, ideally a Free-mode take with beat tapping. The report button in the export tab still sends me everything I need if something misbehaves.
Thanks all! — @Poppadocrock, and anyone I missed, anyone who PMd, everyone testing, you rock
James
Great stuff @JRJRJR - will pick it up when it's released once it gets AUv3