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.
Tasty Pixel Midi Clock Sync
Well, most of it is in the title. Maybe just maybe, after the pretty shitty run with IOS 8 upgrade things may be looking bright on the horizon. I've been super frustrated with the way samplr syncs with loopy hd. It does but in a rather sloppy/drunk way. I've contacted Michael about this and the answer was a maybe.
Now about 2 weeks after that email exchange I've watched this video and I'm definitely feeling good about this. I know its not in the bag yet but I'm feeling confident. I really hope this works, it would make such a difference to the way many of us work on IOS and beyond.
Gotta love this guy! 
Comments
Nice! http://thespectacularsyncengine.com
The universe finally is coming into alignment @supadom!
This is such good news.
Shoe-in for the FAD keynote speech 2016.
EDIT: Of course the 'error' function in the app he mentions/shows here will soon be known among certain other developers as 'The Clock of Shame'.
So be it.
Great!! Just great! Great explanation of midi clock.
Great news for iOS MIDI. It will be interesting to see just how bad the MIDI Clock jitter is on my main desktop DAW and external gear.
If my Electribe scores badly on the clock of shame it might have to go.
Awesome!
I understood maybe 25% of that, but loved every bit of it...
Would be great to have midi sorted out and easily implemented on iOS.
Amazing news, this will really help solidify iOS as a serious music production platform. Midi sync baked into Audiobus sounds like perfect combo
I think it's actually pretty bad news unless he is saying that midibus doesn't provide a stable clock
It would have been better to unite round one standard.
Yes michael, love you for that....
Go michael go.....
It'll be nice if Audio Bus gave out the midi standard to clock all Audio Bus apps, I hope DM1 developers are watching this video.
I think it's up to us to 'pressure' the developers to adopt it as standard. I wrote to Marcos of samplr last night but maybe the more the better?
Nice. Great to see Michael taking on the MIDI problem. The app looks good. It would be nice MIDI if sync could find its way into Audiobus. I know, AB is all about connecting audio streams. But, if the MIDI implementation Michael develops formed part of the AB SDK and AB provided a solid clock implementation then apps could be designed to take their clock from AB.
@xen said:
Let's put these guys against the wall! :P
Fantastic!
@BiancaNeve said:
It does seem as though @michael has completely ignored MidiBus, in one sense and then copied its approach to the problem in another sense. The MidiBus package has a rock solid library, that is freely available and has been implemented by many app Devs.
MidiBus powered apps
Anytune
apeFilter
Beat-Machine
birdStepper
Caustic
Deregulator
Different Drummer
Earhoof
Electrify NXT
Fifth Degree
GliderVerb
Guide Track
Gumdrops
iDensity
iPulsaret
iVCS3
Jam Synth
Key In
Limiter
MidiBus
MidiFire
midiSequencer
Motion Synth
Oscilab
Quincy
Reverb
ScaleGen
SECTOR
Sliver
SOLO [Nr.19]
Sparkle
Stria
Triggler
vidibox
WholeWorldBand
There is also an app in the AppStore, although the app isn't free.
Maybe It's not as bad as it looks, choice can be a good thing.
MidiBus is here now and it works great, so I'm sticking with it.
I don't know, correct me if I'm wrong but is midi bus a separate app? If yes then I'd rather have something that is implemented directly into the apps or linking app such as audiobus. I'm a little sick of starting million apps before I can start making music.
Having said that I'm up for any protocol that works and make my workflow streamlined. Since @Michael has coded audiobus which pretty much became a golden standard for interconnecting audio on IOS amongst many I have a great confidence in him working the same magic for midi.
The midibus library is the code behind the midibus app, and essentially gives any developer access to the midibus clock
http://www.audeonic.com/midibus/
Does not require the app.
Whichever catches on by the developers of the apps I use, I'm happy with it. It's interesting that none of the apps I regularly use are is on the list @Multitouch. Probably that's why I am not aware of it
Turnado
Effectrix
Wow
Egoist
Sunrizer
Magellan
Xynthesizr
Loopy hd
Beatmaker 2
Isem
Samplr
Gadget
There's often two standards in our polarized world. Maybe one needs two of them to keep things in balance with the universe?
@supadom said:
Looking at your list, I see what you mean.
Midi especially on IOS reminds me of the spoken language English as an example.
For apps to sync correctly with other apps, they must completely understand each other .
If we stick four guys in a room and they all speak English that doesn't necessarily mean they will all completely understand each other especially if each one is from a different part of the world.
@Micheal as much as I admire him (which is a lot) has seriously dragged his heels with this
and is still failing with its implementation.
What I mean is Thespectacularsyncengine should be part of the Audibus SDK this would make things a lot simpler for Devs and users. The midi transport controls would be located in the Audibus tab along with the regular controls.
Also hundreds of apps could benefit by simply updating their AudioBus version.
This has been mentioned many moons ago.
http://forum.audiob.us/discussion/comment/11666#Comment_11666
On 7:55 @Micheal mentions that some features maybe come to AB .great news on solving the clunky sync on iOS .Hope the sdk will be adopted like AB.
About midiBus,
On another thread ,@sonosaurus mentions that it's very good for sending clock but it's unclear for receiving. But it would be great for both devs to join forces...
I may have to watch Michaels video again, but as I understand it, he's creating an open source project that helps app developers implement the MIDI standard, not creating a new standard that devs will have to implement, and definitely not creating an app that will be required to run everything. The app he mentioned will be a free diagnostic tool, right?
I just don't understand how this could be seen as a bad thing...
I'm pretty sure that's the same thing that Midibus already is. The Midibus app is not required for developers to use the Midibus library.
I think it would be good if Michael and the Audeonic developer's efforts were collaborative so that at the very least they could work with each other. I wouldn't want a situation like we currently have with AudioCopy and AudioShare where depending upon the app you have to go through extra steps (e.g. Gadget and AudioShare).
I still don't get the problem. If the point is trying to get more apps to do proper MIDI, who cares what Code they use to get there?
I definitely don't know what I'm talking about with MIDI, so I'll be glad to be corrected. I'm just hopeful there is progress coming.
Watching the video and comparing this thing to MIDIBus, I don't see any difference. Everything is already there with MIDIBus. However, the latter was not promoted enough. So, the real news here is that Mike seems to make some efforts to make many apps fix their MIDI implementation using his SDK. He is in a good position to do that I think.
I wish there was a project providing a complete MIDI implementation, not only for clock. Mike mentions the problem that many apps have either too few MIDI options or too many in an heavy-to-understand interface. Furthermore, they all have different defaults. It would be great if all MIDI apps had the same MIDI config screen and the same defaults. This would be really useful not only for syncing apps but also for controlling them with external hardware or from other apps (e.g. Midiflow).
@Hmxt,
If there is no standard ,a dev can be confused on implementation and can lead to incompatibilities between app communication.
When OSC first came out ,I was excited and though it will replace midi soon. But still apps and especially hardware will stick to this " ancient " protocol for many years...
I'd almost forgotten about OSC. I wonder how well that works on iOS. Sorry to go OT.
edit - I started another thread, so as to not derail this one.
What Michael is doing is providing code for developers to use so that they can implement solid MIDI standards compliant sync (useful for both virtual midi and hardware midi compatibility) within their audio engine. Yes, part of that is providing solid midi clock output (which the midibus library also does), but the more critical part is providing solid midi clock reception and syncing, which is much more difficult to get right and to correctly integrate within an audio engine. So far as I've seen there is no good existing library that provides the latter, and I for one am glad there will finally be one.
And it is purely sync only, in fact the only overlap with the midibus library is the clock send functionality. So there really isnt any competition there.
There may be a similarity between the sample app from Michael and the midibus app, but again that is inconsequential as the main point is the SDKs for developer's use that provide solid functionality for things that are easily screwed up.