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
@Samu sorry, I didn't even mean to post that. The forum is really extremely slow and unstable on a mobile device, hard to do anything correctly (for example my iPhone SE freezes completely when I merely try to select anything in the input box, and wildly scrolls around on its own...). But now that you saw it so fast
No, you can just choose which stuff Xequence's MIDI In listens to... but we're derailing the topic (that's why I didn't even mean to post that in the first place 
)
On another note, it's interesting to see just how insensitive most people, even musicians, seem to be to accurate timing. I mean, that file @SlowwFloww posted above is so broken, I wonder how anyone can get away with that for years? Is there not a SINGLE EDM producer using Cubasis or one of the many other apps with these problems?
I mean OK, for me, a 30 fps video is a slideshow and I have my phone cameras set to 60 fps, but come on...
True...
I'm just 'annoyed' by CoreMidi in general and miss something similar to the 'Audio & Midi' app on macOS where you can route sources to destinations and block certain inputs completely.
@SevenSystems @Samu
Ah just remember.. that broken file I posted is from an audio recording of the iPad's audio output....
If I would finish that track and render the project via mixdown it will play in sync....
But it's just annoying working on a track when the whole time the timing is off...
I wanna thank all you guys for helping me out. I learned a lot from the stuff you posted here!
Cubasis is exit for me.. kinda sad because I really liked the GUI and workflow..
@SlowwFloww thank you for bringing this up and the detailed analysis, maybe it helps raise awareness.
Also might be a good idea to post your results directly on the Steinberg Cubasis forum, where it might get more due attention.
I do hope @LFS and his team will do 'something' about the Cubasis timing stability.
On the desktop I'm a Logic Pro X user and it's been like a rock, nothing can shake it.
I still use Cubasis for rendering samples & loops and 'Freezing'(now that it's working more reliably) is really handy.
Apart from multiple AUv3's(Synths & Effects) and other 'MusicApps' my iOS trinity consists of BM3, Cubasis & Gadget and it will likely stay so for the time being.
That's eMagic's legacy
hardware MIDI interfaces had the same timing problems BEFORE eMagic introduced its Unitor 8 (8x8 port interface), which was the first interface ever to introduce -- you guessed it -- MIDI timestamps 
of course, that only worked together with Logic, and indeed gave rock solid MIDI timing even with hardware (the connected MIDI devices themselves didn't get the timestamps, but that was no problem because they were tight enough anyway. The bottleneck back then was the actual operating system on the studio computer, and the connection between the computer and the multiport MIDI interface. That's what the Unitor 8 fixed).
Immediately bought the Unitor 8 when it became available and ditched my old MOTU 6x4 interface, which I had used with Cubase up to that point and was sick of the timing as well.
(for the very young hipsters here: eMagic is the original maker of Logic, which then got bought by Apple and rebranded Logic Pro X)
Thanks for posting this!
Taking the first and last transient as a basis for a jitter measurement grid, the beat attacks vary from -5ms to +7ms.
This is not good, but to say it is "extreme jitter" is a bit of an exaggeration in my opinion.
During my beta testing of other DAWs, I have seen worse, yet people have rarely complained about timing issues.
Anyway, I'm happy to see that more and more musicians take care about precise and tight timing
@LFS has a new challenge now
One more step back, they were originally C-Lab and they even bought the rights to the Atari Falcon from Atari and made rackmount versions.
Great thread by the way, this needs to be a priority for developers.
And I thought I was old!
I remember seeing this ad in magazines in the 90's.
Back when ads actually contained useful technical information and weren't just canned BS from marketing departments
I've done a test with the project file @SlowwFloww posted on an iPad Air 1, iOS 8.4 and Cubasis v2.2:
Again, taking the first and the last transient as a reference, about one third of the hits was very tight (below 0.2ms deviation), one third was 2ms early and another third of the beats was 4ms early. So that's a maximum of 4ms compared to 12ms on a more recent iPad with a more recent iOS version.
Interesting.
Prior to that, I was running Steinberg’s Pro 12 on my Atari ST...
Jitters varying from -5ms to +7ms is not workable for me personally thanks for the info.
As a proof of concept, maybe, and if you still have jitter then your DAW must have serious issues
@rs2000 as a last resort, you could then still join all the individual files into a single one. If it STILL has jitter then, you're probably better off using a tape recorder
They do sound and look more sexy, no doubt
@SevenSystems
I wish I had your eyes and ears!
Don't! As you can see, it only ends in frustration
Ha, yeah I guess.
In your testing, which are the apps other than Gadget and AUM you have found to get timing right?
I can confirm it only for Gadget... I pretty much settled on it when I found it to work
but I'm sure there's others... (SunVox also does it "right" but has a different timing problem... the incoming notes get inserted into a virtual pattern which incidentally runs at the project BPM, so to get accurate timing, you have to crank the project BPM all the way up to 800 (the maximum). And no, using the same BPM as your MIDI data doesn't really work because of phase offset... think about it.)
Iam in full agreement I had these Cubasis issues with audio and shockingly in Auria Pro sometimes - Beatmaker3 = no issues
I've written up a post about timestamping for AUv3 and IAA here, that might be interesting for devs and other nerds
http://lijon.github.io/ios_midi_timestamps.html
PS. The current AUM beta has sample perfect timing for AUv3->AUv3/IAA midi, after rewriting the whole internal MIDI system. Still working on finding solutions for AUv3->CoreMIDI timing...
@j_liljedahl thank you so much for that! I was considering to write something up, but it's much better to see from someone who knows BOTH the MIDI and Audio side!
Exciting news!