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.
Vote here for Audiobus to take on/fix iOS Midi sync
Am posting this to try and see how much demand there is out there from users for a developer (I vote Audiobus) to fix the current mess that is iOS midi sync by baking a solid midi sync send and receive in to apps that use audiobus SDK. Personally i would be happy to have an i app purchase in Audiobus for simplified midi routing and sync that actually works more than 10% of the time.
Comments
+1
+1
Please do.
Yes, midi solidity.
Yes please!
Yes!
I'm sure the AB team feels honoured just to be nominated, but it has already been discussed.
http://forum.audiob.us/discussion/5206/serious-question-why-is-midi-so-wanky-for-so-many-apps-in-ios/p1
Is there any way you could attach a poll? It will give a more legible result.
I vote for this!
+1 for midi sync and +1 for poll
The only issue I'd worry about is adding bloat to a pretty slim program, thus possibly adding extra latency. But I'm all for it otherwise, of course. I think it's obvious that the community would like to see someone fix this. Why not audiobus?
+1
@telecharge said:
Great thread, seems like there are a lot if complex issues at play. Sounds like iOS music making needs to scale up like laptop music making did before likely to be enough incentive for developers. For me is mainly the midi sync element that is broken the rest I can deal with
+1++
+1
Went from loving Gadget and it's slick workflow and new update back to Cubasis due to all the potential great app combos.................ended up with an out of sync mess with glitchy audio once stroke machine was introduced, midi clock made stroke machine into a beat machine gun...what a headache.......
Was so close to deleting the lot........oh well back to Gadget
Unapologetically Terrible.....fix it please Seb & Michael.
I want better sync... and I would like a dev to fix.... But I understand what Seb says about it being logistically difficult and not generating enough revenue.
So I'm happy for anyone who is asking for it to fund the development themselves, but I'm not going to presume to poll Audiobus dev's into the task. It's been asked and answered.
I'm not sure that a single midi sync app is the answer. From what I can tell, there are many apps that have not been designed well around the iOS mdi spec, and part of that might lie with how well Apple has documented it. I think it would be best if we point the offending devs to apps that got it right.
I recently saw this app, and wondered if anyone has tried it....
https://itunes.apple.com/us/app/syncmix/id796836875?mt=8
Looks like the target apps need to support WIST, and that would imply multiple iOS devices, but it might be interesting to hear more about it.
I also saw this......
http://www.finger-pro.com/docs/avoiding-the-pitfalls-of-coremidi-programming-for-developers.html
I wish too
If need more money for development id purchase via inapp purchase some kickstarter extention or something
Wont the AB2 IOS 8 update resolve this with the IAA element anyhow?
@telecharge said:
Has it been three months already? ;-) Anyway, my feelings haven't changed since the last time this conversation came up. :-)
@Audiojunkie said:
I was not a member of forum 3 months ago. Shall expect another similar thread around December then. My hope is that there is enough demand out there for someone to have the financial or personal incentive to get Sync sorted at some point. iOS midi itself is not horrendous (or no more tricky than midi with real wires and physical ports) but the Sync is important for the types of music a lot of iOS musicians are making, even my 4 track cassette studio 18 years ago had a midi timecode sync (taking up one of the 4 audio channels). Guess is a question of watch this space for a year or two.
No worries @RedSkyLullaby! :-) I'm glad you're here and I'm glad that you have strong feelings about this subject! :-) We're on the same team on this one! :-)
@funjunkie27 said:
Agree. Core midi would work if all apps were written correctly to the standard. What really needs to happen is for Apple to develop a module for Core midi that music app developers can easily plug in to their apps. An example is the way that Apple game devs can plug in the standard Game Center code... it's easy for them and each app developer doesn't have to reinvent the wheel themselves.
(cough) MidiBus SDK (cough). It exists and has for a while. And is already in use by several of those Apps that do work right. This keeps coming up, but few remember. (why?)
@dwarman said:
I'm totally agreed with this! I have always thought that MidiBus was the solution. Unless the Audiobus team do something to solve the problem, MidiBus is the way to go. I wish there was a way to get developers to get on board!
@dwarman, this thread is primarily about sync. While the Midibus SDK (and app) is good for general port management, and provides a good master clock send functionality in the app (the SDK is missing some details to control precisely when the clock starts relative to an app's own internal transport), it does not address the real problem of clock reception and sync in the "slave" apps.
A library that does that heavy lifting of midi clock sync reception while exposing an interface that an app's audio engine needs to sync their own transport reliably is what would really help. Perhaps this is something that the Midibus SDK could try to address someday?
IAA transport/tempo sync is a nice solution, but it requires the master app to be the host of all the IAA plugins that need to sync to it, and it requires that everyone implements following that sync API correctly.
Audiobus has positioned itself quite well to be the hub of this sync API because it is already wrapping IAA (being a flexible master app with built-in popup control panel capabilities in all the other apps). It currently does not do anything MIDI related, but it seems like it could produce master midi clock streams for any apps that don't indicate they support IAA sync. But I can't speak for Michael or what he may be already planning (I know he has thought about this stuff).
+1
if only to be rid of all the MIDI-sync related threads here... ;-p
There are some developers that have a handle on MIDI sync, Sonosaurus, Kymatica and Sugarbytes are 3 that quickly come to mind. I can open their apps as IAA nodes using BeatMaker2 as the host with minimal effort, all tightly locked in sync. That is as it should be, with no need for a third party app.
@sonosaurus said:
Wondering what it would take to fund that. $5k? $10k? $15k? More? $15k is less than 4 weeks of work at $100/hr (which is less than the caliber of dev I'd want spearheading this effort could make at a day job). I would absolutely be a part of paying up front for it if it were the right developer, published on GitHub and included good documentation.
Seems like this might be the answer though. If IAA has sample accurate sync and the new AB SDK essentially makes all apps IAA compatible and AB is always running... Plus, as evidenced already, @michael and @sebastian know how to write docs and examples for developers. I'd gladly pay up front for something like this (and pay again for an IAP) if there's a way to make it worth it for them.