Looptimus is compatible with any midi-mappable music software such as Ableton Live, MainStage, Logic and more! Looptimus also works seamlessly with the Loop Community Prime app on iPhone, iPad, or Mac. This software can be used to create virtual loopback MIDI-ports to interconnect applications on Windows that want to open hardware-MIDI-ports for communication. The ports created are unique for each user and only exist while the loopMIDI-application is running. So if you log-off, the created ports cease to exist. In the Audio MIDI Setup app on your Mac, choose Window Show MIDI Studio. In the MIDI Studio window, click the Configure Bluetooth button in the toolbar. Your computer name is the default advertising name for the Bluetooth service. To change the name, enter a. 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.

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

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.

Midi Loop Machine

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

Loop Midi For Mac