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.
Virtual MIDI vs CoreMIDI + Midibridge, getting apps to talk + listen
Lifted from this thread, thought it might be helpful:
http://forum.audiob.us/discussion/comment/106923#Comment_106923
Re: Sampletank MIDI issues... Some apps don't play nice with Virtual MIDI, but they will with CoreMIDI. Sampletank + Beatmaker is one example. (Thesys + midiSequencer is another ...) The solution to this can be found using Midibridge. Normally, CoreMIDI is used to talk over WiFi, but we can use it within iOS too, here's how:
1-Open Midibridge
2-Go to the Preferences pane, to the CoreMIDI Net tab
3-There's a CoreMIDI Net Host/IP Address field
4-Below that, there is an IP address listed. It's probably 10.0.1.2
5-put that IP address into the above mentioned field
6-Port = 5004, connect automatically = yes, connection dialogs = yes
7-Toggle the Disconnect/Connect button
8-Go to the Interfaces pane
9-There should now be two CoreMIDI Net modules, with icons colored Orange, one for input and one for output.
10-you may now quit Midibridge
From now on, every time you open Midibridge, this will happen automatically: the internal CoreMIDI Net will be activated and stay active until you restart the iOS or press the disconnect button in Midibridge.
Then, when using Beatmaker with Sampletank, point BM's MIDI output to Network Session 1, and Sampletank will respond. This will probably work for a bunch of other problem pairings as well. Have fun.
Comments
Shortcut version of above
In MidiBridge prefs, enter the word 'localhost' (without quotes) in the CoreMIDI Network Destination field and press the Connect button. You can also choose 'Connect Automatically' to re-start the connection when MidiBridge launches.
MidiFlow now also has a solution that might work - it now can create additional Virtual MIDI In and Out ports. Usually VM issues are because one or the other App in a connection has its own VM port broken. But also usually the Apps can connect to another App's working VM port, so they should be able to connect to MF ports. FreEWI is used in the past for this trick too, but it only handles one instance, while MF can set up multiple I/O pairs.