> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.morningstar.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Issue using MIDI Controller in Windows OS

# Overview
When using a Morningstar MIDI controller on **Windows**, users may encounter issues where the controller cannot be connected to more than one application at the same time. This is a **Windows operating system limitation**, not a limitation of the Morningstar hardware.

This article explains why this happens and how to work around it, especially when using the **Morningstar Web Editor** alongside DAWs like **Ableton Live**.


# The Core Issue: Windows MIDI Port Exclusivity
On Windows, **MIDI devices use an exclusive-access model**.
This means:
* A single MIDI device can only be connected to **one application at a time**
* If one application opens the MIDI port, **all other applications are blocked** from accessing it
For example:
* If your Morningstar controller is connected to the **Morningstar Web Editor**
* Ableton Live (or any other DAW) **will not be able to see or connect to the controller** at the same time
This behavior is enforced by Windows and applies to **all class-compliant MIDI devices**, not just Morningstar products.


# Common Scenario That Causes Confusion
1. User connects their Morningstar controller to the computer
2. User opens the **Morningstar Web Editor**
3. The controller connects successfully
4. User opens Ableton Live
5. The controller does **not appear** in Ableton’s MIDI settings
This happens because the Web Editor already has exclusive control of the MIDI device.


# Solution 1: Disconnect from the Web Editor
Before using your Morningstar controller with a DAW:
1. **Close the Morningstar Web Editor tab**
2. OR click **Disconnect** in the Web Editor (if available)
3. Wait a few seconds
4. Open your DAW (e.g. Ableton Live)
5. Select the Morningstar controller as a MIDI input/output
Once the Web Editor releases the MIDI port, other software will be able to access it.


# Solution 2: Connect to the Editor via Serial Port
In the Editor, there is a Serial port connection option which will use the Serial protocol instead of MIDI. This allows you to use MIDI for your other MIDI software, and then Serial for connecting to the Editor.


# Solution 3: Use a Virtual MIDI Port (Advanced Users)
Advanced Windows users may use **virtual MIDI routing software** to work around this limitation.
Common options include:
* loopMIDI
* rtpMIDI
* Bome MIDI Translator (paid)
In this setup:
* The Morningstar controller connects to **one application**
* MIDI data is then forwarded to multiple applications via virtual MIDI ports
⚠️ This method is more complex and is **not officially supported**, but it can be useful in advanced workflows.


# Important Notes
* This is a **Windows-only limitation**
* macOS allows multiple applications to access the same MIDI device simultaneously
* Morningstar MIDI controllers are functioning correctly when this occurs


# Summary
If your Morningstar MIDI controller:
* Works in the Web Editor **but not in Ableton**
* Or works in Ableton **but not in the Web Editor**
The cause is almost always Windows MIDI exclusivity.

**Only one application can use the controller at a time on Windows.**