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.
MIDI workflow in ios
First, a mini rant.
I'm really struggling with MIDI in ios. I take as a given having to set up new connections for every session. It's a huge inspiration and workflow killer, but I'm resigned to the fact that it's just part of the ios MIDI ecosystem. But beyond that, I find making connections between apps and syncing apps via MIDI clock sync to highly unreliable. The process differs substantially from one app to the next, and getting apps to do what they're designed to do can just be an endless process of trial and error. Case in point, figuring out reliable ways of: 1) recording on a midi track in Cubasis that triggers Sunrizer, and 2) triggering Sunrizer with steppolyarp required a tremendous amount of troubleshooting. I was unable to get Cubasis and Sunrizer to sync properly via MIDI clock sync. When clock sync was turned on in Cubasis, the tempo varied wildly when playing a patch using the arp in Sunrizer. These are two of the most mature ios apps. This stuff should just work IMO. My solution was to manually "sync" by setting both apps to the same tempo. But even when I did that, the two apps did not play in sync. With the Cubasis metronome turned on, triggering an arp patch in Sunrizer I could hear tempo drift. Adjusting the tempo in Cubasis help bring the two apps closer together but I felt like I was transported into the 1980s. :-) Having steppolyarp drive Sunrizer and record the MIDI output in Cubasis is also proving to be very fiddly. I know what's going through your mind right now. :-) No this is not simply a Sunrizer issue. I had similar issues with Thor and Cubasis.
Now that I've gotten that off my chest, I'd really appreciate hearing any workflow suggestions folks have. Does midibridge solve any of these issues and make working with MIDI in ios more predictable and reliable?
I really want ios to be more than just a cool loop maker, but after an ios music making session it's very common for me to feel like my time would be better spent at a computer DAW where stuff that's a PITA on ios simply works.
Comments
My suggestion is to find something that works then go with that, rather than trying to make something work that doesn't really work.
I started doing this myself just a few months ago and am now able to squeeze little bits of sweet juice from iOS music apps.
My approach has been to find a set up: a sound source, something to drive that sounds source, and something to capture that drive of the sound source. Then just capture as much as I can until I get sick of it.
This approach doesn't always work, but when it doesn't I just move on: find another sound source, etc.
Makes a lot of sense and that's what I've done so far. I've easily generated some very inspirational stuff from Gadget, then brought it into a computer DAW where I've edited and mangled audio from Gadget and added additional parts. In that sense ios has been a nice addition to my workflow. It's probably not a coincidence that the tool I've found most useful (Gadget) is self contained. :-) But I totally get your bigger point which makes sense - find a sound source that generates inspirational stuff, capture the audio, mine the audio for larger compositions.
And it's not that there aren't amazing tools on ios. There are. They just don't play well together (midi wise).
Some apps actually have pretty solid midi implementation, it's just kind of a pain because there's not a lot of consistency. Some apps will do one thing while other apps might not have that same functionality (like clock send or clock receive for example), and so you have to try to remember what does what and it becomes one big tangled mess in your mind trying to keep track.
@ecamburn I agree with you 100% that MIDI is a pain in the ass on iOS. Like 1P18 you have to remember what works for each app. I'm using Notes on the iPad to keep track of everything.
Like you I also see great value in Gadget. Great sound without MIDI headaches. The only bad thing is its' lack of effects and mastering tools. You have to dump the individual tracks to another app or a computer.
MIDI Clock on iOS = http://www.reactiongifs.com/r/fmc.gif
I've had better luck with programs sync'ing via IAA than MIDI.
Using MIDI Bus as a mater clock doesn't fix things. Using MIDI Bridge doesn't solve timing problems but you can save some presets in there which is nice and it lets you route/filter specific events but you are correct that timing synchronization on iOS device is rarely effective.
Yes same frustration here. I like automation and it never works. I got all the MIDI apps and I didn't find a decent workflow with any of them. I also had problems syncing apps in Cubasis. I was disapointed in FluxFx because the automation sequencer doesn't sync. I hope this wil be fixed soon.
Oh man, I agree with all of you. I'm trying to manage the midi out on the Akai EIE that's going to some rack synths. I think I need a good midi management app. Not midi Bridge though. Something that is intuitive and solid. Any ideas would be appreciated.
I have done a ton of troubleshooting in this avenue and have made some progress using audiobus, loopy, akai mpc, ipad, iphone 5, pc and a usb midi keyboard controller together. using pc running podium free (yes, free) you can connect ios devices and apps usind camera connection kit with usb midi interface. with ios app going to akai mpc, then to pc, back to akai, back to ios, you have the ability to have quick and flawless control of clock, code, and track recordings. I can record track after track using mpc or pc as midi recorder. by simply hitting track up or down, I can change pre set midi tracks and channels while recording. I posted my first couple youtube videos on this called HOW TO SETUP SWEET MIDI WORKFLOW
Im still learning the youtube thing but this setup could be done in many different ways with different equipment. I would be glad to help if I can.
this video is part 1/2. part 2/2 goes into detail adout the ios bs-16i app and how to control it with this setup. this also works for all the apps I use on ios. when I hit record on mpc, it will sync with ios tempoand other functions
There are things happening with this kind of stuff. I cannot talk about it but there's hope (TM).
I use MidiBridge as my prime connection and mapping manager, but I am also somewhat geeky and techie and don't mind the UI. You might have a better experience with MidiFlow. Each has their differentiating features, but both also can not fix broken MIDI implementations in other Apps, although sometimes can they provide a useable work-around.
And either of them gives you a central viewpoint of your MIDI connectivity if you use them that way, far preferable to me than having to go into each App and loo at their MIDI connection configuration (usually several menus down) to set or check who sends to whom, and having to keep in mind that they must only send one way - one end needs a working Virtual MIDI In port and the other end needs to be able to see and send to it. OR (and definitely not AND), one needs a working Virtual MIDI Out port that the other can see and listen to. MidiBridge and MidiFlow work with Apps that have working Virtual MIDI ports and are not promiscuous listeners.
btw, I would classify MidiBridge as very solid, just maybe not so intuitive (though the patch bay paradigm for cabling between devices and Apps was immediately obvious to me). MidiBridge and MidiFlow both implement state saving (MB calls them Scenes, MF calls them Songs), a feature which can fix your topology issues. MB additionally can switch scenes in response to Program Change messages, either received from connected MIDI sources or synthesized internally using the StreamByter.
@Sebastian woot!
@dwarman While Sebastian is beavering away on his new universal MIDI whatsamajigit I'm going to check out MidiBridge and MidiFlow. I like possibility that you can make MIDI connections in a consistent way outside of the apps.
Good post dwarman.
Agreed. I've been using MF more than MB lately because of the UI but MB is very capable.
@icaveman Thanks for making and sharing those videos.
integrating all my hardware, all my software and all my apps at once is the name of my game. its great having new tech all the time to learn. Im always interested in workflow efficiency. keep my eyes open