Loop Midi For Mac

LiveLoop is a live midi sequencer that enables you to record loop while playing piano on a keyboard. To record loop while playing. Or delete midi tracks directly., or a midiYoke port to use. To autostart your virtual MIDI ports you need to goto the traybar, right click the loopMIDI icon and activate autostart. Restart your host application. You should now be able to select your virtual MIDI ports within your host and within the MP3244 or SQ4.

Free Midi For Mac
Loopmidi For Mac Free Download
Midi Loop Machine

Last modified: Jan 19, 2021 @ 9:36 am

In the Audio MIDI Setup app on your Mac, choose Window Show MIDI Studio. In the MIDI Studio window, click the Choose MIDI Configuration pop-up menu (it may show Default), then choose New Configuration. Enter a name for the new configuration, then click OK. To add a new external MIDI device, click the Add button in the MIDI Studio toolbar. An Apple Loops is a type of audio file that uses the.aiff file extension. What makes them so special is the little amount of meta data stored within the file that tells Garageband and Logic some vital information about the file. The information stored within the file can include things like genre, instrument, key, tempo, time signature.

Update 13-Sept-2019: the information in this post (originally from Sept 2016) is still relevant for OSX 10.14. Reference to a new, easy-to-use software MIDI keyboard (MidiKeys) has been added.

Note: this page describes setup for OS X 10.11-10.14. Some older versions like 10.10 and 10.9 are essentially the same where MIDI is concerned, but your millage may vary if you have a vastly older OS versions (namely those older than 10.6).

Although a basic MIDI setup on Mac OS X is typically easier than on Windows (to go beyond the default Windows synth anyway), it still requires some work. Here I will try to give a comprehensive overview of what you need to work with MIDI on Mac, particularly for interactive MIDI applications. I am also focusing on free setup, so the instructions on this page do not involve spending money to get things working.

In brief, to work with MIDI you need two things at a minimum:

Virtual MIDI ports (many devices create these automatically, but some programs do not)
A synthesizer

You may also want a way to get MIDI input without extra hardware. All of these topics are covered here.

First though, let’s talk about exactly what MIDI is. Some of this general information on MIDI is the same as on my Working with MIDI on Windows page. If you know about MIDI already, feel free to skip right to the section on Virtual MIDI ports.

MIDI stands for Musical Instrument Digital Interface. It is a protocol for communicating information between various devices and it has been around for over 30 years. For various reasons, many people new to MIDI struggle with what exactly it is and, therefore, often misunderstand what it and programs using it can and cannot do. Here are some quick facts that are often stumbling points for people that are new to working with MIDI and audio, each of which will be addressed in more detail later:

MIDI is a way of communicating between devices with certain message formats. For example, a MIDI controller can communicate to another device, perhaps a synthesizer, when a pitch should start and when it should end—much like the information communicated by a note on a paper score. In fact, a MIDI file is actually pretty close to a paper score in terms of the types of information it captures.
MIDI is not sound! You cannot “hear” MIDI any more than you can “hear” a paper score
by itself. MIDI controllers do not create sound by themselves. Things that make sound from MIDI must interpret what they are told via the MIDI protocol. These devices are synthesizers, and they interact with audio devices to create sound.
Generally, your on-board sound chip and many external soundcards know nothing special
about MIDI and they are not MIDI synthesizers. If you buy a brand new laptop, its sound chip will not deal with MIDI messages and is not a MIDI synthesizer.

Note that a “MIDI device” does not have to be a piece of hardware. There are plenty of software “MIDI devices” that can be called as such simply because they show up in device lists just like hardware devices.

1.1 MIDI Messages

MIDI information is broken into messages, which are sent over some communication medium. Messages can refer to “programs” or patches (think of it as an instrument name), channels, pitches, and so on. Channels can be thought of like staffs on a digital music score. Some examples of MIDI messages include:

Note on: start playing a particular pitch on a particular channel at a particular volume.
Note off: stop playing a particular pitch on a particular channel.
Program change: assign a new instrument to a channel.

Once again, these messages must be interpreted by a synthesizer in order to create sound. Sometimes MIDI messages are also called MIDI events.

MIDI-related programs that do not show up in the device manager when running are not MIDI
devices.

1.2 Controllers vs. Synthesizers

The difference between a MIDI controller and synthesizer is quite simple:

A MIDI Controller is a device that allows a human to push some buttons or keys and generate MIDI messages or events. In: human ineraction. Out: MIDI messages. There is no sound involved.

A MIDI synthesizer is a device that receives MIDI messages and produces sound. In: MIDI messages. Out: sound via an audio device or audio jack.

In a hardware-only setup, a MIDI controller (like a keyboard) would be physically connected to a MIDI synthesizer, to which speakers or headphones would then be connected. Perhaps some of the sound vs. MIDI confusion that the music community experiences is due to the fact that may keyboards actually include both of these elements: they are all-in-one MIDI controllers and synthesizers. However, any such device that features both “MIDI in” and “MIDI out” ports can usually be used as one or the other independently.

There is also a third category of devices that simply re-rout and/or re-interpret MIDI messages. As hardware, these devices are usually peripherals used to do specialized tasks like duplicating a stream of MIDI messages, merging MIDI message streams, or allowing a foot pedal to send messages down a regular MIDI cable (foot pedals meant for use with MIDI equipment typically have 1/4-inch TS or TRS plugs and send control voltage that has to be interpreted by something as a series of MIDI messages). Software also exists to re-rout, merge, and split MIDI messages.

Note: many common cases of using MIDI on Mac do NOT require setting up new virtual MIDI ports. Many devices (software and hardware) create their own ports. However, if you need to relay messages between two or more programs that do NOT create their own ports, you will need to follow the steps in this section.

A virtual MIDI port is a piece of software that runs in the background to send/receive MIDI messages from other programs or hardware devices. Virtual MIDI ports allow communication between MIDI-related programs that are not perceived by the operating system as MIDI devices. In other words, these programs might be able to send and receive MIDI messages, but they can’t “see” each other directly—but they will both be able to see a virtual MIDI port and can, therefore, use it to communicate. Hardware ports can be used similarly, although it often requires using a MIDI cable to create an ungainly self-loop (connecting a device’s output to its own input).

OS X comes with the ability to set up new virtual MIDI ports. Typically there are none by default and you have to add them manually. Here’s how to get to the screen where you can configure your ports:

Open up Finder and click on “Applications.”
Search for “Audio MIDI Setup” – you should see a little keyboard icon show up. Double click on it.
If you are lucky, you will get 2-3 windows that open up and one of them will be called “MIDI Studio.” If you don’t see that window, go up to the top left of the screen and go to
Audio MIDI Setup > Preferences and make sure the box called “MIDI Window” is ticked.
Once you have MIDI Studio open, double-click on “IAC Driver.”
There should be a list called “Ports.” If this is empty, you don’t have any ports set up. To add a new port, click the “+” button. This port will now always be there (potentially unless you upgrade your OS version – then you might need to go through these steps again).
You can manage the ports you have as you need new ones or if you want to remove some later. Typically it’s good to have at least 2 ports at any given time. You can give your ports meaningful names if you want by double-clicking the name of the port.

WARNING: you should never send to and receive from the same port within the same program. Doing so creates a feedback loop of never-ending messages. This is one of the reasons it’s good to have two different ports available when you are experimenting with hooking MIDI-based programs together. Some situations require even more ports to avoid feedback loops, but two is good enough for most cases.

As described above, a synthesizer is the thing that actually makes sound for you. Both hardware and software synthesizers exist. For Macs, typically the easiest solution is SimpleSynth. You can download and install this program and keep it running in the background at all times. This will give you a basic set of standard MIDI sounds. SimplySynth creates its own virtual MIDI port while it is running. If you have no other ports set up, it will be the default output device. You can also set SimpleSynth to take input from other ports or input devices.

If you want to use sound font (SF2) files, another great option is Sforzando. This program behaves much like SimpleSynth and is very easy to configure, but you need to already have some SF2 files to use with it. So, if you currently have some virtual instruments in SF2 format and want to use them, give Sforzando a try. Like SimpleSynth, Sforzando creates its own virtual MIDI port while it is running, but it can also take input from other ports/devices.

IMPORTANT: Make sure you start SimpleSynth/Sforzando first, before opening any other MIDI software! If you already had other programs open, close them and re-open them after starting the synthesizer.

To turn MIDI messages into sound, you need to get them from the source producing them to the synthesizer that will interpret them. The producing program may be a MIDI file player, a physical MIDI controller, or a software MIDI controller.

SimpleSynth happens to come with its own virtual MIDI port functionality. You can change which port SimpleSynth listens to for MIDI messages. Regardless of which port you use, you want the following configuration overall:

Program making MIDI messages –> a particular port –> SimpleSynth

Your message-producing program should send to the same port that SimpleSynth is set to receive from. If you have multiple programs creating MIDI messages, you can set all of them to send to the same port that SimpleSynth is listening to.

If you have a situation where you are taking MIDI input from one device, processing it with some other program, and then outputing new messages to a synthesizer, you MUST have two different ports involved:

MIDI message generator –> Port1 –> SomeOtherProgram –> Port2 –> SimpleSynth

If you try to use just a single port, you’ll get a feedback loop.

Most USB hardware MIDI controllers make their own port show up on the system when plugged in. In these cases, you can have a somewhat simpler setup:

HardwareNamePort –> SomeOtherProgram –> SomeVirtualPort -> SimpleSynth

Sometimes it’s nice to be able to get MIDI input without having a physical MIDI controller to plug into your computer. For these situations, I recommend MidiKeys (simplest option) or Virtual Midi Piano Keyboard (VMPK). To send MIDI messages from these programs to others, you need a virtual MIDI port set up as described in previous sections.

Using MidiKeys
The nice thing about MidiKeys is that you just need to fire it up before the program that will be accepting MIDI messages from it. The downside is that you must do Ctrl+Click > Open the first time you run it (later versions of OS X aren’t friendly to 3rd party apps opening with double-click the first time) and the the keyboard mapping is a little funky. Still, it is by far the simplest solution for getting a keyboard-based MIDI controller on OS X. It can send to either its own port or any other port registered with the operating system at the time.

Using VMPK
Make sure you have virtual MIDI ports set up as needed BEFORE starting up VMPK. VMPK also acts as its own synthesizer, so if you want it to act purely as a controller then you need to configure it as follows:

Go to Edit > MIDI Connections
Tick “Enable MIDI Thru on MIDI Output”
Tick “Show Advanced Connections”
Set the MIDI OUT Driver to be “CoreMIDI”
Set the Output MIDI Connection to be your desired virtual port. Note: if you don’t tick “show advanced connections,” you may not see the ports you’re looking for.

If you want to set VMPK to only play when clicking instead of making sound whenever the mouse passes over the keyboard, you can do the following:

Go to vmpk > Preferences
Untick “Enable Touch Screen Input”

I recommend two approaches for playing MIDI files if you don’t care where the MIDI messages are sent:

MuseScore – useful for making scores and playing simple MIDI files. Note: it is primarily intended for MIDI files that have very “clean” timing (in other words, not files recorded from live human input).

If you want to play a MIDI file and customize the output device, most programs available on Mac seem to cost money. At present I don’t have a good alternative to recommend. When I find one, I will update this page accordingly.

05/2021 ipMIDI macOS 2.0 released – Big Sur

ipMIDI 2.0 now runs native on macOS 11.3 Big Sur arm64 ('Silicon') and intel64 architecture.

Check out the trial version of IpMIDI. ipMIDI trial runs for 60 days with full functionality. After that it continues to work with one port.

Customers of ipMDI for Windows, please email for an additional free retail version of ipMIDI 2.0 macOS.

02/2021 ipMIDI, LoopBe30, LoopBe1, LoopBeAudio and Windows 10 Feature upgrade 20H2

All drivers run out of the box. No further action is required after an upgrade.
LoopBeAudio may lose its custom icon in the sound control panel. How to fix.

12/2020 ipMIDI, LoopBe30, LoopBe1, LoopBeAudio and Windows 10 Feature upgrade 2004

All drivers run out of the box. No further action is required after an upgrade.

01/2020 ipMIDI macOS is now 'notarized'

ipMIDI 1.7.1 macOS is now notarized. This will make installation easier in future osx releases. There is no need for a reinstall.

10/2019 ipMIDI on macOS Catalina

ipMIDI 1.7.1 macOS runs without problems. No further action is required after an upgrade or clean install.

05/2019 ipMIDI, LoopBe30, LoopBe1, LoopBeAudio and Windows 10 Feature upgrade 1903

All drivers run out of the box. No further action is required after an upgrade.

01/2019 ipMIDI on macOS Mojave

ipMIDI 1.7.1 macOS runs without problems. No further action is required after an upgrade.

05/2018 ipMIDI, LoopBe30, LoopBe1 and Windows 10 Feature upgrade 1803

All drivers run out of the box. No further action is required after an upgrade.

05/2018 LoopBeAudio and Windows Windows 10 Feature upgrade 1803

Again, all audio drivers will loose their custom icons in the Sound Control Panel.
So does LoopBeAudio.
How to fix

03/2018 ipMIDI 1.7.1 macOS released

Free Midi For Mac

After a lot of trouble with the upgrade to (High) Sierra, version 1.7.1 should solve the problems. Sorry for the inconvenience.
Additionally, Release 1.7.1 works again with old 32bit drivers from third party vendors. Otherwise there is no reason to update a working setup.

Download ipmidi_1.7.1.dmg

11/2017 ipMIDI, LoopBe30, LoopBe1 and Windows 10 Fall Creator Feature upgrade

All drivers run out of the box. No further action is required after an upgrade.

11/2017 LoopBeAudio and Windows 10 Fall Creator Feature upgrade

Again, all audio drivers will loose their custom icons in the Sound Control Panel.
So does LoopBeAudio.

06/2017 ipMIDI 1.7 macOS - new digital signature

ipmidi.dmg has a new digital signature to make the install more easy on macOS Sierra.

04/2017 ipMIDI, LoopBe30, LoopBe1 and Windows 10 Creators update

All drivers run out of the box. No further action is required after an update.

04/2017 LoopBeAudio and Windows 10 Creators update

All audio drivers will loose their custom icons in the Sound Control Panel. So does LoopBeAudio.
You can assign the old icons via: Sound ⇒ Playback/Recording ⇒ <device> ⇒ Properties ⇒ Change Icon
Browse to:
Program Files (x86)nerds.deLoopBeAudioloopBeAudio.exe
to set the old LoopBeAudio icon again.

A reinstall of LoopBeAudio will also fix this issue.
No other problems were found.

10/2016 ipMIDI 1.7 macOS released - the Sierra update.

ipMIDI version 1.7 released. The new 64 bit driver is running on macOS 10.12 Sierra, OS X 10.11 El Capitan and OS X 10.10 Yosemite

ipMIDI OS X version 1.6 (32/64 bit driver) for OS X Lion to Mavericks (10.6 - 10.9) and
version 1.5 (Universal binary) for OS X Leopard (10.5) are still available.

Get your free copy now! read more...

09/2016 ipMIDI - MIDI over Ethernet, compatible hardware

Solid State Logic bundles the ipMIDI driver with their audio consoles.

ams Neve recommends ipMIDI for their audio mixing consoles, e.g. in the Genesys manual.

Rupert Neve Designs recommends ipMIDI in their SwiftMix™ Fader System manual.

more about hardware.

08/2016 Windows 10 Anniversary update with ipMIDI, LoopBe30, LoopBeAudio

After the update to Windows 10 '1607' all audio drivers will loose their custom icons in the Sound Control Panel. You can assign the old icons via: Sound ⇒ Playback/Recording ⇒ <device> ⇒ Properties ⇒ Change Icon
Browse to:
Program Files (x86)nerds.deLoopBeAudioloopBeAudio.exe
to set the old LoopBeAudio icon again.

A reinstall of LoopBeAudio will also fix this issue. No other problems were found.

ipMIDI and LoopBe30 run out of the box. No further action is required after an update.

11/2015 LoopBeAudio 1.2 released - the Windows 10 '1511' update

Users of LoopBeAudio need to install the new LoopBeAudio version 1.2 after an update to Windows 10 '1511 aka threshold 2' [Version 10.0.10586].
Please uninstall the old driver and run the version 1.2 installer.

Customers will receive an email for a free upgrade.
more about LoopBeAudio...

10/2015 ipMIDI and OS X 10.11 El Capitan.

ipMIDI OS X runs fine in El Capitan, both after an update and after a new installation..

For a fresh install make sure your security settings are on their defaults:
System Preferences ⇒ Security & Privacy ⇒ Allow apps downloaded from: ⇒ Mac App Store and identified developers (or Anywhere)

08/2015 LoopBeAudio 1.1 released - the Virtual Audio Cable

Version 1.1 is Windows 10 compatible. Please uninstall the old version and install version 1.1.
Adds support for ASIO4ALL. Have a look at the help file for an example setup.

Customers will receive an email for a free upgrade.
more about LoopBeAudio...

08/2015 Windows 10 update with ipMIDI, LoopBe30, LoopBeAudio

ipMIDI, LoopBe and LoopBeAudio are fully Windows 10 compatible.

To use LoopBe30 after Windows 10 update, you must reinstall it using the original installation file. Please uninstall with the Control Panel, reboot and run the installer again.

ipMIDI runs out of the box. No further action is required after an update.
Users of LoopBeAudio need to install the new LoopBeAudio version 1.1
Please uninstall the old driver and run the version 1.1 installer.

03/2015 LoopBeAudio released - A Virtual Audio Cable

LoopBeAudio is a virtual audio device to transfer audio between computer programs, digitally, without any quality loss.

Configure up to 24 audio channels, a sample rate from 8000 Hz to 384000 Hz with a bit depth from 8 bit to 32 bit. Build a virtual 7.1 surround device, even though you don't have the built-in hardware.
more about LoopBeAudio...

02/2015 ipMIDI and OS X 10.10 Yosemite.

ipMIDI OS X runs fine in Yosemite, both after an update and after a new installation..

10/2013 Windows 8.1 update with LoopBe30 and ipMIDI.

To use LoopBe30 after Windows 8.1 update, you must reinstall it using the original installation file. Please uninstall, reboot and run the installer again.

ipMIDI runs out of the box. No further action is required after an update.

03/2013 ipMIDI 1.9.1 released, the Windows 8 update - MIDI over Ethernet Driver.

Version 1.9.1 is a small bug fix for windows 8 only.
It was not possible to disable local loopback. (MIDI between application within the same computer).
This is fixed.

Registered customers will receive an email from share-it for a free update.
more about ipMIDI...

09/2012 Silent Mountain Lion update for ipMIDI OS X.

The installer of ipMIDI is digitally signed now, so Mountain Lion's 'Gate Keeper' does not complain anymore.

Get your free copy now! read more...

08/2011 ipMIDI 1.6 OS X released - the Lion update.

ipMIDI OS X version 1.6 is a 32/64 bit driver for OS X Lion and Snow Leopard (10.6 - 10.7).
Version 1.5 (Universal binary) is still available for OS X Leopard (10.5)

07/2011 ipMIDI - MIDI over Ethernet compatible hardware:

The Cintex GmbH offers with their DMX512 product series new ipMIDI compatible hardware.
Solid State Logic bundles the ipMIDI driver with their Matrix console.

more about hardware.

05/2011 ipMIDI, LoopBe30, LoopBe1 spring update:

ipMIDI version 1.9:
Removed leading spaces from the port names 1-9. Some older Application could not handle this correctly. e.g ' 1. Ethernet MIDI' is renamed to '01. Ethernet MIDI'.
An input port received old messages after reopening in certain circumstances. This is fixed.

LoopBe30 version 1.6:
Removed leading spaces from the port names 1-9. e.g ' 1. Internal MIDI' is renamed to '01. Internal MIDI'.
An input port received old messages after reopening in certain circumstances. This is fixed.

LoopBe1 version 1.6:
The input port received old messages after reopening in certain circumstances. This is fixed.

Registered customers will receive an email from share-it for a free update.

04/2010 ipMIDI 1.8 for Windows released - MIDI over Ethernet Driver

ipMIDI installer did not open the windows firewall for Starter and Home Editions of Windows 7 / Vista. Professional and Ultimate Editions are working properly. This is fixed in release 1.8.
So if you were disappointed by ipMIDI trial on those version, maybe you give it a second chance.

Registered customers will receive an email from share-it for a free update.
more about ipMIDI...

10/2009 ipMIDI 1.7 released, the Windows 7 update - MIDI over Ethernet Driver

Version 1.7 adds Windows 7 compatibility.
Only the installer has changed. There is no need to update your existing XP or Vista installations.
There is even no need to reinstall ipMIDI during a Vista to Win7 update, but if you install ipMIDI on a fresh Windows 7 you need ipMIDI 1.7.

Registered customers, please check your email for a free update.
more about ipMIDI...

10/2009 LoopBe30, LoopBe1 and Windows 7 - virtual MIDI Loopback driver

...are working together without any problems. Both after an update and a fresh install.

LoopBe1, LoopBe30

09/2009 ipMIDI 1.5 OSX and Apple Snow Leopard...

...are working together without any problems. Both after an update and a fresh install.

Get your free copy now! read more...

03/2009 ipMIDI 1.5 for Apple Mac OS X released - a free MIDI over Ethernet Driver

Version 1.5 is a bugfix release to achieve better compatibility with third party applications.

ipMIDI 1.5 OS X Changelog:

Cubase forgot ipMIDI ports after every restart. They had to be reassigned in Cubases MIDI Device Manager. This is fixed.
During ProTools start up there was sometimes a problem with fragmented MIDI messages. This was a problem for hardware devices listening to ipMIDI. This is fixed.

Get your free copy now! read more...

09/2008 ipMIDI 1.6 for Windows released - MIDI over Ethernet Driver

New feature of version 1.6: 'enable/disable loop back'

With the 'Loop back' checkbox you can define how your MIDI messages are routed.
If you disable loop back only application hosted on another computer will receive MIDI. This is the prefered way when you start a simple setup.
With loop back enabled, applications hosted within the same computer and your sending application, will additional receive your MIDI data.

Registered customers, please check your email for a free update.
more about ipMIDI...

07/2008 ipMIDI 1.4 for Apple Mac OS X released - a free MIDI over Ethernet Driver

Version 1.4 OS X Changelog:

Reduced network traffic algorithm like the ipMIDI WinPC version.
Fixed a problem with not working 'phantom ports' reported with some configuations.
Fixed a problem when reinitializing ports within Logic.
Adjustable Loopback: Disable Loopback to receive only MIDI originated from another computer. Enable Loopback to send MIDI between applications within the same computer.

Get your free copy now! read more...

06/2008 ipMIDI 1.5.3 for Windows released - a MIDI over Ethernet Driver

Version 1.5.3 is a bugfix release recommended for all users of Windows:

Reduced network traffic. This version will even work with weaker network cards or hub/switches. If you had problems with dropped MIDI messages give this version a try.
Loopback is fixed again on Windows Vista. (Send MIDI from one application to another within the same computer).

Registered customers, please check your email for a free update.
more about ipMIDI...

03/2008 ipMIDI 1.1 for Apple Mac OS X 10.5.x leopard update - (universal binary)

ipMIDI runs now on 10.4.x tiger and 10.5.x leopard.
ipMIDI offers now up to 20 multicast MIDI over LAN ports to connect your Apple Macintoshs with Windows PC's in your local network.
Get your free copy now! read more...

01/2008 LoopBe30 1.5 released - 64 bit Virtual MIDI Driver with up to 30 Ports

LoopBe30 version 1.5 additionally contains a native 64 bit driver. It installs and uninstalls cleanly under Windows Vista 64/32 bit, Windows Xp 64/32 bit and Windows 2000.
A better integration with Vista User Account Control (UAC).
The driver, systray application and installer have been signed.
(No functionality has been added for Windows Xp 32 bit and Windows 2000)

Registered customers, please check your email for a free update.

LoopBe30 is an internal MIDI device for transferring MIDI data between computer programs.
more about LoopBe30...

01/2008 ipMIDI 1.5.1 for Windows released - a MIDI over Ethernet Driver (Vista / XP / 2k - 32 and 64 bit)

Version 1.5.1 is a regression bug fix release: 1.5.0 did crash in rare cases on Windows XP. We apologize for the inconvenience caused.
Known limitations to all versions : On Windows Vista MIDI loopback is broken. (You can not send MIDI from one application to another within the same computer). This does not apply to Windows XP. A fix is scheduled. Please use Loopbe30/1 if you need this functionality.

Registered customers, please check your email for a free update.
more about ipMIDI...

01/2008 LoopBe1 ver 1.5.1 released - A Free Virtual MIDI Driver (Vista / XP / 2k - 32 and 64 bit)

Version 1.5.1 is a regression bug fix release: 1.5.0 did crash in rare cases on Windows XP. We apologize for the inconvenience caused.

LoopBe1 is an internal MIDI device for transferring MIDI data between computer programs. more...

12/2007 LoopBe1 64bit released - A Free Virtual MIDI Driver

Version 1.5 additionally contains a native 64 bit driver. It installs and uninstalls cleanly under Windows Vista 64/32 bit, Windows Xp 64/32 bit and Windows 2000.
The driver, systray application and installer have been signed.
(No functionality has been added for Windows Xp 32 bit and Windows 2000)

LoopBe1 is an internal MIDI device for transferring MIDI data between computer programs. more...

11/2007 ipMIDI 1.5 for Windows released - 64 bit MIDI over Ethernet Driver

Version 1.5 additionally contains a native 64 bit driver. It installs and uninstalls cleanly under Windows Vista 64/32 bit, Windows Xp 64/32 bit and Windows 2000.
A better integration with Vista User Account Control (UAC).
The driver, systray application and installer have been signed.

Registered customers, please check your email for a free update. (No functionality has been added for Windows Xp 32 bit and Windows 2000)
more about ipMIDI...

07/2007 ipMIDI 1.0 final for Apple Mac OS X 10.4.x tiger - released (universal binary)

ipMIDI offers now up to 20 multicast MIDI over LAN ports to connect your Apple Macintoshs with Windows PC's in your local network.
Get your free copy now! read more...

03/2007 inst2midi has been discontinued

Due to the focus on driver development the distribution of inst2midi has been dicontinued.
Thanks a lot to all customers since 1998.

02/2007 ipMIDI 1.2 released - A MIDI over Ethernet Driver

Version 1.2 installs and uninstalls cleanly under Windows Vista 32bit. No functionality is added, so there is no need to update your Windows XP installations.
Registered customers, please check your email for a free update.
more about ipMIDI...

01/2007 LoopBe30 1.2 released - A Virtual MIDI Driver with up to 30 Ports

Version 1.2 installs and uninstalls cleanly under Windows Vista 32bit. No functionality is added, so there is no need to update your Windows XP installations.
more about LoopBe30...

1/2007 LoopBe1 ver. 1.2 released - A Free Virtual MIDI Driver

LoopBe1 is an internal MIDI device for transferring MIDI data between computer programs. more...

Version 1.2 installs and uninstalls cleanly under Windows Vista 32bit. No functionality is added, so there is no need to update your Windows XP installations.

11/2006 ipMIDI 1.0 beta 3 for Apple Mac OS X 10.4.x tiger - released (universal binary)

ipMIDI offers now up to 20 multicast MIDI over LAN ports to connect your Apple Macintoshs with Windows PC's in your local network. read more...

ipMIDI beta 2 was not running on intelmacs. Sorry for the inconvenience.

06/2006 ipMIDI 1.0 beta for Apple Mac OS X 10.4.x tiger - released (universal binary)

Loopmidi For Mac Free Download

read more.... ipMIDI - A virtual, multi platform, MIDI over LAN driver.

06/2006 LoopBe30 1.1 released - A Virtual MIDI Driver with up to 30 Ports

Shortcut detection settings are stored in the registry. LoopBe30 will now load all your previos settings after a reboot.
Registered customers, please check your email for a free update.
more about LoopBe30...

02/2006 LoopBe30 1.0 released - A Virtual MIDI Driver with up to 30 Ports

LoopBe30 is a virtual MIDI device for transferring MIDI data between computer programs.
It has adjustable number of ports and adjustable shortcut detection. more...

Midi Loop Machine

11/2005: ipMIDI 1.1 released - A MIDI over Ethernet Driver

This is a bug fix. In ipMIDI 1.0 Ethernet MIDI Port 7 was missing.
Registered customers, please check your email for a free update.

09/2005: ipMIDI for Linux is called Multimidicast made by llg

Get it now: multimidicast by Linux Lighting Group . ipMIDI starts to become a multi platform solution.

07/2005: ipMIDI - A MIDI over Ethernet Driver

A virtual driver to send MIDI over LAN.
No more MIDI interfaces needed to communicate between applications on different PC's.
ipMIDI is a native WDM driver, with even lower latency than a hardware legacy device and real MIDI cables.
ipMIDI sends MIDI Data over Multicast UDP, not TCP/ip, so you will not have any client server hassle.
Select 'Ethernet Midi Port' in your audio application. That's all, no configuration, no problems. more...

05/2005: ipMIDI beta 1 released - A MIDI over Ethernet Driver

Thank you very much to all beta-testers.

12/2004: LoopBe1 ver. 1.1 released - A Free Virtual MIDI Driver

Small changes:

New Icon Set. Artwork by RGP Netherlands

10/2004: LoopBe1 ver. 1.01 released

Small changes with the installer:

Uninstalling LoopBe1 does not need a reboot under Windows XP.
Auto starting Entry for LoopBe1 Monitor moved from registry to startup folder.

5/2004: LoopBe1 released

LoopBe1 is an internal MIDI device for transferring MIDI data between computer programs. more...

Inst2midi - Audio to MIDI real-time Conversion Software

Inst2Midi converts your monophonic audio source straight into MIDI Data. more...