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
I also think it should support sync without buying an additional app.
I also appreciate the irony of saying that here, on the errmm, AudioBus site....
Thanks for the update and info
I've not got midibus so hadn't tried that - it was @Calcutta - who hopefully can try again and maybe report back which apps or DAWs work with midibus?
Great news about the plan to see how others have managed the sync issue with a view to updating. The app is sounding great and so it's the tantalising prospect of wanting to use it more that's frustrating me
I'd love to support midibus, but I need another app window to switch to for start/stop or midi setup like I need a hole in my head. Small things like constantly changing windows are crushing my creativity on the platform - sad but true. I appreciate an open source standard can only be a good thing, but the apathetic musician in me will gravitate towards app workflows which are easier to setup and maintain.
Thanks for the vid - looking forward to anyone with midibus and Cubasis or Auria to report back
@EvilBird said:
ah, this explains all my horrors! thx 4 this
do i need to kick everybodys ass so u guys can agree on a simple clock?
get it going!
thx 4 the work around, to bad it doesn't support state saving, so i can't save the tempo with it
and ab2 could fix it - all they have to do is say u need to support "this" clock or u r not on the bus
It would be great if developers could unite and present a solution to Apple or at least lobby/push Apple to get a standard implemented.
I can't imagine that it's not already on the company's list of things to do, I just don't think it's a priority.
edit: and of course maybe users could do some similar lobbying. music apps are probably not the highest selling apps, but we're total nerds and we probably buy a lot of them!
@Skoptic - COMPLETELY agree with you about the pain of having to switch to another window. I've been chatting with some other devs about the issue, seems I'm not the only one who's had trouble getting DM1 to play nice. The conversation is giving me a few leads to pursue so hopefully we can obviate the need for MidiBus. Btw, were you able to get the workaround to sync bS and DM1? Curious since you weren't able to get it working before.
@lala and @papertiger - I'm with you, though I'm skeptical that Apple will be of much help. I think this is going to be a matter of users demanding better, and devs coming together to build an open source midi standard. I'm planning to open source my midi sync code once I get this issue figured out, which I hope will encourage more indie devs to adopt an open MIDI protocol. More open source code, and the input of users like yourselves, are probably our best hope for improving things for the immediate future.
@papertiger said:
Apple has already rolled out their standard for syncing apps... IAA timeline integration. They wisely ditched midi clock sync even though IAA supports midi data. Timeline integration is similar to MTC (midi time code) in that it provides the node with the exact position in time that the sequencers transport is located in addition to the exact bpm (which is much better than a bunch of ticks that the programmer has to measure and average the bpm from using various inexact methods). Clock sync has never been accurate even at its best and was replaced by MTC a long time ago.
I have, and have previously owned, pretty many synths, and none of them ever synced to MTC, only to MIDI clock. Many of the apps I use on my iPad sync perfectly well to MIDI clock as well.
http://en.wikipedia.org/wiki/MIDI_beat_clock
A google search turns up plenty of examples of how badly clock sync suffers from clock drift. If the tempo never changes I've found that it can stay synced long enough for a whole song, but only if the receiver is good at averaging the bpm. If a song has tempo changes then you can forget about 2 instruments ever playing in time together. For simple tempo based effects like delay and arpeggiators, clock sync is perfectly fine. Synths that don't have a built in sequencer wouldn't implement MTC anyway. Getting 2 different instruments to play sequences together at the same time is never going to work right on iOS with clock sync, which is why Apple has implemented MTC. Clock sync will remain adequate for time based FX.
Guess I'm lucky that I don't want to play back sequences, just have my delays, arps, and step sequencers stay in sync.
Which most of the time, works out fine.
Agree with @dreamless that clock drift is the entropy of midi sync. On a song-length recording, sync goes to dung by the end. I'm going to check out using Apple's MTC protocol for bS, but I'm wondering--@dreamless, did you use this protocol for Jam Synth? (I haven't checked it out yet :-/) Was the protocol robustly supported by other apps or is it still catching on?
I just finished implementing it in both Jam Synth and Beat-Machine, but the updates aren't approved yet. With Jam Synth it didn't really matter because it only syncs the delay and lfo and clock sync works fine, but I added it anyway because IAA also bypasses virtual midi (another potential hazard). Beat-Machine has benefited greatly from it because its sequencer can be directly linked to the IAA host sequencer for perfect sync. It seems only the major DAW apps have implemented it though.
Cheers @dreamless for illuminating us on this. Clearly if you're working in dev environment you learn pretty quickly the nuts and bolts. I've noticed that iaa tempo sync is solid which totally confirms what you've just said.
Yes midi has it flaws, but thats no excuse
Lets stay in the real world: how many instruments do you know that support mtc/smtpe?
none?
And how many do you know that support midi?
i guess the numbers are talking 4 themselfs ...
Tempochanges arent everybodys cup of tea either ...
Its only 24 ticks a beat - so get that shit motherfucking together &_&
I dont need songposition stuff, im playing how the mood takes me
mtc is boring taperecorder shit
That is not the point of audiobus @all!
if i wanted that i could just use boring cubasis or something and call it a day ...
I like tea. I like it a lot.
One sugar for me please!
Can't beat a good Assam
Thanks lala, glad I'm not the only one who feels that way.
Unless that was sarcasm....then, never mind....
@dreamless did you have any difficulty getting IAA/MTC to play nice with AB? I worked on implementing IAA with Singaling, still in beta tho because of buggy interactions between AB and IAA
If I could use the IAA clock in birdStepper without disrupting the flow of audio to AB, that might be an optimal solution
@zymos
No no
I mean what I say, I was beginning to feel like im talking to myself, thats why I was getting angry.
Did you buy the app lala?
I like peppermint tea.
Good, drink some, it'll give you something to do.
I like against the grain, as long as it's not just to fvck up the wood.
So, everyone who has birdstepper, how do you like it so far (aside from techincal issues)? Does it fill a need for you in your music?
@EvilBird said:
No, IAA seems to steal the audio away from AB when an app is connected to both. IAA sync isn't optimal yet because it's only implemented by host sequencers but bS could make use of it pretty easily.
dreamless said:
Thats the point im trying to make.
Scroll around the forum and look what ppl say, i remember reading sebastian saying something along the lines like 1/2 of the patches they see have nothing in the output slot. So it seams a lot of ppl use audiobus live in some way and not to record stuff.
thats part of why i am posting all those patches so other devs see how audiobus is used and not how they think it is used...
@lala said:
Hey Lala.. no offense, but I'm not sure what you're message is. I think you want all developers for iOS to come up with a standard? That world be nice, but I suppose its not that simple to make everyone adopt the same thing in the real world.
@gkillmaster said:
I'm not sure who else has the app here? There's a lot of chat, but not many case reports.
The sound is good - it can completely mangle things and has been great on both beats and synth loops. I must admit the lack of sync means I've used it faaaaar less than I would usually with a new app.
Handling the lines is a bit haphazard and there's no undo.. so it's a bit more about feel and fun, rather than the precision of dialling in a well crafted Effectrix session (or maybe that's just me).
The delay or wobble don't have bpm sync ability (or I haven't found these yet) so you get a free roaming sync .. which can be both good and bad
There isn't any quantise to the horizontal sequence of each FX control (er finding it difficult to explain that and I'm in a rush
) so again it is a bit unstructured which can be both good and bad too 
There might be these function which I haven't found yet - but I suppose I'm getting at it being organically haphazard rather than clinical effectrix grid action
To me its very simple:

If we dont start here and now it just wont happen
Its just like when ios4.2 introduced midi and it took our coding monkeys a year to maybe use it ...
And now its x years later and we r still having issues with the god dammed midi clock sync, wtf?
I remember talking 2 sebastian when he started that ios midi dev group and I asked him: well, what took you so long? And he said we didnt know ppl wanted this ...
It's nice to know you were being constructively polite and appreciative back then too
Nothing like the agitator who thinks they are responsible for accomplishments...
Im pushy, so what?
Thanking god for the not working sync is not the way I pray.
If u cant deal with that just ignore me