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.
Auria Pro -- Am I missing something here?
Can anybody explain the following:
- Why can't I record MIDI in loop mode? I set loop to on and it loops in playback, but just keeps recording past the loop markers in record mode. I've set MIDI overdub to ON and every MIDI sequencer I've ever used (and I started in the 80s!) could do this. I'd go as far as saying it's an essential feature for a MIDI sequencer.
Am I missing a setting somewhere?
- When I connect a MIDI controller keyboard, every single track plays back (even the internal keyboard works like this). As default. Errr... WTF?
The only way I can get this to work 'properly' is to turn off MIDI input for every track I don't want responding to my MIDI keyboard and then turn it back on again when I do? Rather than just select a track and play, like in (copy and past from above: every MIDI sequencer I've ever used). This is maddening. I just want it to play/record the selected track ONLY. Why would I want every track to play back as default?
These basic things seem so backwards to me that I think I must be doing something wrong. I've hunted through all the settings and I've RTFM but I can't find any answers.
Please show me where I'm going wrong here...
Comments
@klownshed
You're not going wrong.
Auria Pro doesn't do loop record.
When you create midi tracks they are automatically
set to ,'All', on input and ,'All', on output.
The best thing to do is create a template with
a basic amount of midi tracks and set them all to ,'off', on input
and configure the channel outs to the synths or midi outs that you regularly use.
The developer thought that it was the best thing to do in an update earlier this year.
Loop recording has been requested for years, going back to the original Auria in 2012, but apparently it would require a rewrite of the audio engine so it can't be implemented.
(I'm not au fair with the technical details, but I do know that Auria streams from disk, which is one reason why it could support 48 tracks on an iPad 2 back in the day, and also why it can support huge sample libraries. It's possible that the disk streaming could be a factor here, but I'm speculating).
The MIDI input definitely needs to be revisited, hopefully it can be addressed in the near future. In Cubasis you have to select and record-enable a track to record MIDI to it. But in Auria there has never been the necessity to actually select a track to play or record to it, so in the past in order to enable MIDI input you had to record-enable a track - the problem is many users found that really confusing, so the behaviour was changed. However I don't think the change is a good one in its current implementation - either Auria needs an AUM-style MIDI matrix, or a better UI for selecting MIDI input.
On the built-in keyboard though you can just directly select the track number you want to play to, that at least works for me. But with exernal keyboards the current system is cumbersome.
If you want to play an instrument on one track and not hear instruments on other tracks, you have to turn off the midi inputs of the tracks you don’t want to hear. It didn’t use to be the case but Wave Machine Labs changed it a few updates ago , why they chose to go that route I have no idea and it’s why I don’t use it for midi production at all. You should be able to select a track and just hear that track when you play, not all tracks. Constantly having to turn midi on and off instruments is a major inspiration killer for me to the point that it’s hard for me to justify keeping it on my iPad, It’s only on my iPad because I’ve invested so much money into it. 🤷🏽♂️
The change was because one of the most frequent complaints/confusions among new users has been the need to arm a track for recording to hear the connected instrument.
Knowing how it works, I don't find it it so terrible to enable midi in on a track when I want it controlled by my keyboard and then turn it off when I'm done.
The thing that makes it a hassle is that you have to popup the input panel, but I think he is thinking about how to make it more convenient. You should contact the devs on their site if you would like to see a change.
I don’t understand the thought process behind these decisions.
It’s a solved problem in every other midi sequencer I’ve ever used.
There are too many baffling (to me) design decisions in Autia Pro that make it a pain to use and quite frankly there’s no point in contacting the developer as my brain is clearly not wired like the developer’s.
If you try on a pair of Nikes and they don’t fit there’s no point in complaining when Adidas fit perfectly.
Auria Pro doesn’t fit me. Shame. I will just put it down to experience and move on.
😊
Maybe you’re right and it doesn’t fit you, but if I could offer a suggestion...don’t think of Auria as a midi sequencer. There are plenty of those out there already and they do their job just fine. Auria is, in my mind, a near studio quality daw that’s geared to naturally recorded audio with midi bolted on to it. I think Rim’s concept for his midi implementation was that there was no need to reinvent the wheel when he had bigger fish to fry, so to speak. Auria is my main recording device, but I’m an analogue guy. Auria is definitely not a “midi first” app. It’s an after thought, if we’re honest. That being said, the hooks Rim built in there should allow you to get where you want to be midi-wise. Auria does things no other app can do. It also definitely falls short of some functionality that midi-first apps can do. But for a traditional daw used to record and manipulate sounds...for me, there’s none better. All I’m suggesting is maybe a change of perspective.
FWIW, the change was in response to user feedback not some strange thinking on the developer’s part. Apparently, a lot of people find the record-enabling to monitor a track counter-intuitive.
While I might like the MIDI editing more in some apps, the time resolution is essential to me. No other iOS app that I know of has both sample accurate audio and MIDI which I need when working with audio that didn't start out quantized. (Not to mention its buses).
If none of those things matter then there are other alternatives...and they all have warts. I guess it is always a matter of what one gets on with.