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.
MidiBridge vs MidiFlow vs ????
Quick or maybe not so quick question. LoopTree appears to need a midi app to route the few midi commands to it. I am trying to control it with my FCB1010. I have it set to send note data but I get nothing from LoopTree. I was hoping to do a video of LoopTree soon. I have been meaning to buy one of these midi routing apps but never really needed to until now. I am just wondering which one you guys recommend. I know that MidiBridge does not see many updates and with iOS 9 lurking around the corner I want to take that into consideration too.
Thanks in advance.
Comments
MidiFlow has become pretty useful for me over the last few months. Fairly user friendly UI for setting up routing and filtering. Filtering has become pretty powerful over the last several revisions. Defintely the easiest to get up and running with.
I do like MidiBridge, as well. I moved from a PC based Ableton setup, and I relied heavily on Bomes Midi Translator, which could do all sorts of non standard conversions. Was very surprised at how much similar functionality I was able to get out of MidiBridge, right down to scripting support.
I would recommend both, but think MidiFlow will handle most standard routing and filtering needs with a much lower learning curve. MidiBridge takes a bit longer to take in, but has some extra layers of control if you need it.
Do you just need basic routing?
@rad3d Thanks. I just need basic routing for now but I am always open for more options and advanced features.
I'm with rad3d on this one. Pitch perfect.
@gmslayton
Here is the documentation of Midiflow: http://midiflow.com/documentation/
I think it gives you a good idea of what you can do with the app, and how. While the scripting feature of MidiBridge can be useful, Midiflow has quite some other unique features: Custom virtual ports, Routing retention, MIDI clock, Monitoring, support for RPN/NRPN, and so on.
The biggest MF feature for me is custom Virtual ports. MF is I believe unique for this. OTOH, MB has the StreamByter for arbitrary remapping of messages. MB does also have pretty reasonable routing retention, PC selectable routing scenes, and only shows you active ports, vs MF wich shows all your Apps in the selectors. I have a few hundred. MB also shows multiple connections (1 to many and many to one) in a slightly more compact and immediate format.
Both are handy, even both at the same time. I only have to mess with App's own selectors to make sure they only have their Virtual ports enabled and no other connections. I wish they would remember that. Most do not.
I don't like the UI of Midi bridge.For some reason i rarely could get it to work.I'm too dumb for it it seems
Although i never spend a huge amount of time with it,most often i found a solution without having another app in the background.Unfortunately i need to try it again now.I realised that iM1 has no input selector and this damn thing ALWAYS receives notes on the master channel when i play it with an external keyboard thru cubasis (using the iM1s Multimode...).
For me Midibridge is simpler to set up. I like the way you can see the ins and outs flash as they receive data so it's easy to see if the connections have been made.
Do these apps use much CPU ? I've never bothered just because I've always assumed the benefit is outweighed by the hassle/ CPU drain.
Both have seemed to operate very efficiently for me. Never noticed a hit from using them.
Have midibridge but it only gives me more headaches. Terrible interface and half of the setups i try wont work. Must say i only understand the basics of midi and midibridge is more made for advanced midi users. I wish i bought midiflow because it looks a lot more user friendly.