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 - MIDI Compensation Placing Events *Early*
Hey. Pro Musician here. In Auria, I can play parts dead on the beat when recording, and when I finish, the recorded MIDI data is anywhere from 1500-1600 samples earlier on the grid than what I played and is completely out of sync and unusable on playback. I’m used to adjusting slightly for low latencies but this is something else. (Yes, recording on a different device with 0 latency monitoring spits out exactly what I played.)
As far as I can tell, adjusting recording compensation does nothing for how it adjusts and places the incoming MIDI notes on the grid. It only affects miced/direct audio.
Has anyone solved this?
Comments
(Note this is for projects that are “off grid” and quantizing isn’t an option for both reasons of groove and the drums not precisely aligning to begin with.)
What buffer setting are you using?
Are you using a separate buffer size when recording?
and have you looked at latency compensation in settings?
How are you determining the latency?
Are you user that you aren't seeing the audio data being later than you expect rather than the MIDI data being earlier?
I think it sends midi with a timestamp in the future. Korg instruments react correctly to this kind of midi.
The midi events (and the triggered sound on playback) are placed earlier than I played them in real time, and thus are ahead of the pulse, etc.
I measured the difference in samples using the Samples mode on the timeline and used the maximum zoom to determine the distance between the downbeats and the beginning of midi events. That’s where I got the 1500-1600 from.
Latency Compensation does not help because Auria does not implement negative compensation. Adding compensation just makes the gap wider.
I used a variety of buffers from 512 all the way down to 64.
I am still unclear how are you determining when the MIDI events were actually played (i.e. to eliminate the possibility that you are playing slighty ahead of the beat to compensate for the audio latency)? Measuring the difference between the audio events and the MIDI does not necessarily tell you when the MIDI was played. If the audio was generated in response to the MIDI, the gap may tell you the relative time difference of the audio data making it to disk.
Can you give a more complete description of the set-up?
Without knowing more it is hard to know exactly what the situation is. Is this audio coming from a mic, from a hardware synth triggered by the incoming MIDI, or ......
I ask because if there is any latency in the system between when the MIDI note was initially played and when the audio is generated, a good player is likely going to compensate without knowing it. So, if they are aiming to be precisely on the beat, the MIDI will be ahead of the beat to compensate for the latency.
If my math is right, 1500 samples is about 34 milliseconds at 44.1kHz. Does the amount of offset change at all when you change the buffer size? Set it to something big just to see.
On the first point, you’ll just have to trust me that I know my playing well enough from other recordings to say that it does not come in 34 ms early under normal conditions , but also that what I’m hearing in real time when I am recording does not match what is getting played back afterwards. If there’s no option to turn off compensatIon for that in the MIDI output, that’s a problem. (Example: Reaper has an option to turn off the MIDI compensation altogether if you’re adjusting for latency in real time.)
The chain is either playing the touch screen keyboard or using an external midi controller to play live on the keys, using both internal Auria instruments and 3rd party AUs. Straight out of the iPad speakers/headphone jack.
The lowest buffer I can get without buzzing is 64. The offset is still 1500-1600 samples. The results are the same at 512
@Ziggysane interesting problem. So it sounds like during tracking you’re playing dead on but on playback it sounds early, but the data is also visually placed early. Even if this is a major glitch, can you not just move the data over to line up exactly, as an interim solution, annoying as it may be?
If I was playing some thing that was on a regular grid it would be an option and it’s what I’ve done in the past, but playing to unquantized drums and songs with tempo changes makes it hard to line anything up without knowing if it’s going to be out of sync/groove overall. There’s probably a way to do it by ear through trial and error and nudging, but that’s valuable time for recording music :-)
It might be worth trying in another DAW on the same device if you have one - just to isolate whether it's something particular to Auria Pro or not.
I tried in two of the free ones (since I already spent $50 on Auria Pro I’m not eager to throw more money at the problem).
Soundtrap - better than Auria, but the offset is still pretty bad overall, with no option to adjust.
N-Track - much better!!!! Very close out of the box on default settings. If nothing else, it proves that it’s a problem with how midi compensation and audio are handled in Auria and not that it’s something inherent to iOS/the iPad that can’t be fixed.
Have you been in touch with Auria's developer?
@Ziggysane
What hardware are you using?
External audio interface?
Midi interface?
Usb hub?
Not your complete rig obviously.