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
The tempo changes should be part of the MIDI file itself and should be unrelated to a particular track, so I'm not quite understanding the click track part. I think it's best if you could send the MIDI file to [email protected] for further investigation.
Davy,
The “click track” is just my nomenclature for the MIDI file created in Studio One with the song tempo map built it. In this instance, I add a metronome sound on each beat that, when rendered to audio, will match the stems for our rehearsal track. I can see the tempo markers (matching the file tempo changes), but the beat pulses of the track don’t line up with the time line. I’ll email the file after my morning coffee. 😏
Thank you!
Doug
MIDI File sent. Thanks!
Audio Evolution Mobile Studio v5.2.8 for iOS released:
How would I get midi data made with Atom 2 Piano Roll, to the main piano roll/arrange window?
I don't know that app, so I guess it's best to look for a MIDI export option and then import the .mid file into AEMS.
So there’s no way for AEM to record the midi data into its timeline in real-time like Cubasis ‘rec to track’ ?
Please open the midi input dialog of an instrument track and see if there is a device related to that app. Or perhaps try the virtual midi entry.
What is the point of being able to load midi au on a midi track if you can’t route it to an instrument or audio track?
Is it meant to sequence outboard only?
Reason I’m asking is because midi au on an instrument track can be recorded to the timeline, we just don’t have enough midi au inserts, 1 is very limiting.
Also, now I see that you removed recording of midi au to the timeline, why?
This was a key aspect to me using aem.
Unfortunate decision to remove this feature without notice and without asking users, feels like a huge step backwards in features and makes me feel it was a mistake purchasing aem only a month ago.
You can put an AU midi on an instrument track and then it will process the midi on the track, just like other apps do. This way it works like audio effects on an audio track.
Not at all. That wasn't even possible before the last release, now it is.
That may come later, but hasn't changed in this release.
Because it was wrong before. It wasn't an effect like an audio effect on an audio track.
I'm sorry you feel that way, but this is how it was supposed to work in the first place. Being able to modify the AU midi parameters while keeping the originally played midi in tact has huge benefits.
What you want would be the same as audio effects getting embedded into the audio sample without being able to change any of the parameters afterwards. So if you would want to adjust a reverb mix, you would have to record the audio all over again.
I don't see the downside of having it the proper new way.
Ok so, the downside is simple, midi effects are not just effects per se, using a drum sequencer is not an effect.
If you want to build a song you have multiple sequences, before you could record each sequence to the time line and arrange it, now you can’t.
Same thing with midi au’s that send midi cc to automate a synth, you can’t arrange it.
The outcome of removing it is huge, means that you can’t arrange midi au to a full blown song.
Same with tools like scaler, it outputs a sequence of midi progressions, now I can’t record a sequence of verse 1, verse 2, chorus, breakdown and make full song out of it.
Removing a feature is a mistake, and it will definitely make people reach far less for aem instead of using a different host.
I know it made me look elsewhere as it seems decisions are not made for everyday usage by real users.
Let us users choose how we want it to work, best way is to have a changeable setting in the configuration panel
I can make a setting, no problem. It just makes me wonder why apps like Cubasis also work like AEMS does now and seemingly nobody has complained about it.
Cubasis enables you to record midi au straight to the timeline, Mts even has paste to timeline button so there’s no need to even press play, paste outputs the midi straight to the timeline from the au.
And thank you for listening and bringing it back, if it can come back with multiple midi auminserts instead of only one or/and a way to route midi au from a midi track to other midi tracks(and instruments) it will be much appreciated.
FWIW, those apps that don’t allow for the possibility of capturing midi fx midi on the piano roll, do get a lot of comments about the lack. While it makes sense to have midifx be just like the fx on an audio track , it often makes sense to have the possibility to capture the midi output.
Ok, so I added a 'Rec' button to the AU MIDI screen. I think it works now as you want:
Off: MIDI on the track is processed, MIDI from the input (real-time) is processed, the unprocessed MIDI is recorded
On: MIDI on the track is not processed, MIDI from the input (real-time) is processed, the processed MIDI is recorded
Correct?
Im not sure if i understand
What does "midi on the track is not processed" mean when talking about when record is on?
Is there a testflight version to test it?
Everybody take a minute to respect and appreciate the developer that is this responsive. Nobody else would make an immediate update response to try to help a forum post.
Well, MIDI that is already on the track in a clip. The thing you don't want is that your AU MIDI processed recorded events get processed again when playing back after that. I checked with Cubasis 'Rec to track' and AEMS should do the same now.
There is no Testflight version, but I will probably upload this version today.
Amazing, i appreciate the quick fix and response time.
Thanks.
Just let me know by the forum if it does or still does not do what you expect. I'm looking at implementing multiple AU MIDI effects now, but with some AU MIDI fx now possibly being on 'Rec to track' and others not, things have become even more complex.
10,000 points baby.
Am I crazy or is Audio Evolution Mobile Studio on sale right now? It says $7.99 right now... I thought it was far more than that. I thought it was something like $29.99?
https://apps.apple.com/us/app/audio-evolution-mobile-studio/id1094758623
@NeuM said:
It has never been above $12.99 I think. But I'm experimenting with prices. Unfortunately, I cannot set a price per country, like on Android. This prevents me from asking a lower price in poorer countries. When I changed the price 'tier' from $9.99 to $7.99 on the 9th of October, sales and total profit has gone up. So, it's the poor man's solution with equal or more features than higher priced products, just because it's not from a known company. Oh well, perhaps the upcoming unique feature will change that.
…..? 🤔
Just a quick question. I have the Flowtones IAP. Is it not possible to have pitch and mod wheels on screen to use, or have I missed something obvious?
The interface of Flowtones is as Toneboosters made it.
Ok, thanks.
I wonder if AEMS is becoming the next Nanostudio.
Eh? In what way? It doesn’t record the output of midi fx? Hasn’t the option for that been added into AEMS in the latest update?
Ok, so the update should be out now (or very soon). Please let me know if that solves the issue with AU MIDI.