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
That would be incredible! Please share. Do you have something like that for AUM by any chance? I haven't made an account to post the transport super fast speed bug, btw, @a_m, it asked to use my personal Google account and I was in a rush when I last thought of it (daughter just get let out of school and had an hours drive back home in traffic!)... I'll get on it ASAP. I noticed the bug also happens occasionally if I deactivate the app in AUM and then reactivate it.
@a_m You must have done loads of settings during development and yet there are not one preset. I for on would really appreciate some starters to bypass starting from scratch. Hopeful you'll add some in a near future
I don’t think anything like that would be possible in AUM. Loopy Pro has a very deep system for creating custom UI that makes it possible.
The transport super fast speed bug should be fixed now as of version 1.0.1.
Thanks Doug! That's what I needed. "Cool Beans"
Thank you for the quick work! Have any thoughts on future apps?
Can someone tell me how to set up the CC modifier in Drambo? I can get it working in Audio Evolution Mobile Studio and AUM but not in Drambo.
I press the MIDI Learn button in Drambo, assign a CC number to a parameter in Drambo, then use that CC number with the CC modifier in Neon but nothing happens. What am i doing wrong?
No one able to help?
Can you provide more details on how you have it set up in Drambo? I could guess, and ask do you have a MIDI Output module loaded in the rack, but if I'm wrong, then we'll be going back and forth a lot checking other things.
Sure, no problem.
This is how i have it set up but when i assign a CC number to, for example, the oscillator fine tune and use that number for the CC modulator in Neon nothing happens.
Have i got it set up wrong?
Thanks again. Doug!
The video that @thesoundtestroom posted got me on board. This sequencer is a great companion to ID700. Thanks for a great app @a_m!
Anyone had a problem with it losing states and modifiers when reloading a project in AUM? I had something really nice going this afternoon, saved it all and when I loaded the session again this evening only the active states are intact. All the other states are empty, in both instances.
Is it any more reliable if you save the presets? I’m so used to sessions reloading as they were saved I didn’t save the presets.
the parameter tree (what is loaded by the host when you reload a session) only contains the active state. but if you save the preset, it will load it with the state when you reload the session. so yea, the intended workflow is to save presets when you are using multiple states. sorry that wasn’t clear…
Thanks for the quick reply.
This might become a problem more generally, then, as people expect sessions to reload as they were, fully intact. Having to save the state of the plugin separately to the host project is what we used to have to do with older IAA apps. My understanding is that AUv3s are expected to save their complete state in the host project, and that’s certainly the case with other plugins. Having to remember to do something extra at the end of each session means I’ll probably stop using it as this non-standard behaviour pretty much guarantees I’ll lose work again at some point.
yea i totally get that… i think i could probably make it work that way in the future, but i think the parameter address layout would need to change and i’d have to give some thought on how to do that without screwing up users’ existing work
My experience with auv3s is that the entire state of the auv3 is saved in a project, which is one of the biggest benefits of auv3.
yeah… now lamenting my choice to do it the way i did it… don’t remember exactly what my thinking was at the time. agree that this would be a big quality of life improvement tho…
We're rooting for ya. This is such a powerful sequencer. I'd love to see as many people adopt it as possible, and I think state saving will really be a big part of that since your sequencer offers so much in the stages and metasequencer!
A few factory presets would be nice..
I second that. It’s amazing. It’s just the ease with which you can lose a couple of hours’ work if you don’t remember to save it separately to your project that’s making me wary. In the case of my experience today, I had two instances going, so I’d have had to save three things to be able to retrieve the whole thing.
So how do you import NeonPreset files from one device to another? 4Pockets NeonAudioEditor shows up..
Thanks..
I think tbh, as this is so new, ppl would rather have their old projects not load properly than have to deal with this problem going forward in perpetuity, as it genuinely is a workflow killer and will generate a lot of complaints. If you did a poll here, I reckon the vast majority would say 'definitely fix that, at any cost'.
New setup is a bit confusing. Old option which saved all states was better. Getting a bunch of crashes now and lost sequences in states in existing projects in AUM because I didn't save to presets.
Also, tried using AUM presets as a way to save all states and getting crashes.
This is an awesome sequencer, please look in to this.
This is +1 for both state saving when a host saves.
and a +1 for changing the value of a parameter on release of a selection instead of arrival of a selection as an option. For me, it’s confusing to have say, a stage’s behavior change on me, when I’m just scrolling the list of possible options. I can see how that’s a deal-breaker for any sort of live use.
Also, here’s my pitch for some kind of two finger scroll procedure for choosing a value from a loooog list of options like the scale list. Or some kind of tap to summon the list of of options, the dialog box stays open, then scroll the list, then make a selection, then dismiss the dialog box, or some other re-working of how long lists are navigated.
To navigate a list like that requires three to four complete rounds of summon & swipe to get values at the extremes of a range.
It’s early minutes in getting oriented to neon, so I don’t have any projects to get lost in a state saving refactor.
This sequencer looks super fun to dive into, well done!
Seconded, thirded or whatever. Worth it for the security of being sure that when you save a project it’s saved completely.
Awesome sequencer! But please fix the state saving as a top priority. Second, what @drconfusion said about the way you choose values etc. is spot on how I feel about it. If that could be changed as well it would be very appriciated.
That said, Neon is super fun and inspiring in every other way.
man i sure hope this gets set up to work
to Iphone
I know it would be a lot of work, but wouldn’t it be cool if the app’s icon color changed to correspond to each instance’s color?
AUM does facilitate for this though in a way…
Hello. @Robin2
I tried to test CC modulation setting you mentioned.
Maybe it worked so I explain it below.
But if you try it, please be careful to turn down your hardware and software volumes, or use a limiter app/module/etc., before testing. (The reason is described below.)
Note: If the method I wrote helped @Robin2, it is because @EdZAB ‘s advice was helpful.
*
Warning:
I don’t know how to properly set up ‘MIDI feedback’ of MIDI output module of Drambo.
So I’m very concerned that volume of output sound may be too loud or make noise, by reasons that I would never think of.
So, please be careful to turn down your hardware and software volumes, or use a limiter app/module/etc., before testing.
*
Terrible note:
I have Drambo, but I don't have Neon. (Exactly. I’m a blood sucking flea who gets joyful energy from reading comments of people who enjoy a new app. My apologies.)
So I tested with Octachron sequencer app instead. As a result, my method worked in my environment.
But I’m not sure if it can be applied to your situation. Besides, I don’t know if my method is the best solution or not. And I’m very amateur about music software and hardware and etc. So I have no idea what my Drambo settings mean.
*
Test method:
The difference between your method and mine is ‘probably’ the presence of a MIDI output module.
(The settings of Drambo app itself or Neon app’s settings might possibly have something to do with it, but I’m not sure.)
Please see the attached image file 1 to check the position of modules.
I set Tune knob on OSCILLATOR module to CC 30.
I set Fine knob on OSCILLATOR module to CC 31.
I set PW knob on OSCILLATOR module to CC 32.
And I set CC parameter values of 30, 31, and 32 on Octachron.
(Please see the attached image file 2, 3, 4, 5.)
(6th track in the screenshot is in red state is merely my operational error.)
I tapped Drambo’s ▶️ switch.
All three knobs moved(?).
(Please see the attached gif file.)
Hi @cramdog. Thank you so much for taking the time to give such complete advice, really kind of you and massively appreciated.
So, i tried your setup (with volume very low in case as advised) and it worked for modulating the assigned cc with Neon, but other functions from Neon - the basic sequencing functions - didn’t seem to work.
Fortunately, this setup
seems to work perfectly!
Don’t know If that setup is the ‘correct’ way but it seems to work.
Many thanks again for your help @cramdog, i couldn’t have got it working without you. Cheers.