|
|
|
|
|
|
Update: MidiBridge v1.1 Released – Adds Support for Virtual MIDI
Date Added: Oct 22, 2011
22 October 2011:
Audeonic Apps have released version 1.1 of MidiBridge. The update includes support for Virtual MIDI to interconnect other apps on the same device that support Virtual MIDI.
What’s new:
- Now supports Virtual MIDI to interconnect OMAC compatible apps (Open Music App Collaboration)
- Backgroundable
- Jitter/sync mode
- Fixes bug where events going to wrong output
- Minor bug fixes and improvements
MidiBridge is a utility that interconnects all MIDI interfaces (external and network) on an iOS device at a fraction of the cost of equivalent hardware.
Supported external interfaces include Line 6 Midi Mobilizer I and Line 6 Midi Mobilizer II, IK Multimedia iRig MIDI and all other CoreMIDI devices that are compatible with iOS via the USB camera kit on iPad. For CoreMIDI support, iOS 4.2 or greater is required.
For more information about MidiBridge click here.
|
 |
You Might Also Like...
MidAir (Universal)
miniyo-T (iPhone)
4x4 Virtual Mobile for Traktor (iPhone)
Beatsurfing (iPad)
Muza (Universal)
News: Choose Category
Twitter
RSS
COOL! I have just read that you can connect apps that support Core Midi but not virtual midi to virtual midi ports using this brigde. Someone wrote that he were able to control Animoog with Genome this way. Definitly have to check it out. Will return with info on how it works.
Cheers
Ooooh Yeah! This works. By connecting midibridge to it self, just write “localhost” in the midicore ip adress under preferences and connect, you can control your midi core apps with genome by bridging it to the virtual “network session”. So far it works with animoog, alchemy, iSyn Poly, Addictive, iMS20 and grainbender on my iPad2. Guess it works for all midi core apps then.
This is very cool indeed!
Eh! …Seems like Genome can do the trick without the need of MidiBridge. Just go to midi config -> Network midi -> [name of the owner]‘s iPad and connect..Duh!
Sorry if I made anyone buy midi bridge in vain for this purpose. However MidiBrigde can still connect a good deal of different controllers to virtual ports or MidiCore.
Cheers
Just a little clarification on this. IncarnateX is correct in that if the source
MIDI App (in this case Genome) can connect to itself and operate on the CoreMIDI network port, then all apps that can receive on the network port can be controlled.
All apps implement CoreMIDI in their own way and they don’t always interconnect. Sampletank, for example listens to all apps’ virtual MIDI outs, but not all apps define their own MIDI outs and prefer to write to other apps’ MIDI ins. Here is where MidiBridge can solve inter app connectivity issues:
- connect a ‘write to MIDI in’ controlling app to a ‘read from MIDI out’ receiving app (as described above).
- connect an app that can send to CoreMIDI virtual to an app that supports only CoreMIDI network (ie. no virtual supportl)
- connect one controlling app to multiple receiving apps and (optionally) split the receiving apps across MIDI channels.
- connect Midi Mobilizer I (and soon synthstation 25) to newer CoreMIDI apps that don’t natively support these devices.
Plus all combinations of the above.
Nic,