FL Studio Troubleshooting

Last updated on
Print this article

If FL Studio becomes unresponsive, crashes, or keeps failing after setting up the Auriteq controller, the issue is usually caused by a MIDI feedback loop. This can happen on Windows when FL Studio automatically changes the MIDI port configuration after a restart.

FL Studio on Windows: FL Studio becomes unresponsive, crashes, or keeps failing after setup

Problem

After setting up the Auriteq controller in FL Studio on Windows, FL Studio may become unstable or stop responding.

You may experience one or more of the following symptoms:

  • FL Studio becomes unresponsive after setup
  • FL Studio freezes or crashes when the controller is active
  • The controller works at first, but the issue returns after restarting FL Studio
  • FL Studio keeps failing even after you disable the problematic MIDI port
  • The MIDI settings look correct at first, but change again after a restart

Cause

This issue is caused by a MIDI feedback loop.

On Windows, FL Studio may automatically assign the Auriteq input port as an output port as well. If the input and output ports are assigned to the same channel, FL Studio can send MIDI data back into itself, creating an infinite feedback loop.

When this happens, your MIDI settings may look similar to this:

The important thing to check is whether the input port has also been assigned as an output port on the same channel.

If you simply turn the problematic input port off, FL Studio may assign it back to Channel 1 the next time you restart the program. This is why the problem can keep returning even after you think you have fixed it.

Solution

Step 1: Open FL Studio MIDI Settings

Open FL Studio and go to Options → MIDI Settings.

Step 2: Find the problematic port

Look for the Auriteq input port that is being assigned as an output port.

In the example shown above, this port is called ATIN.

Step 3: Do not simply turn the port off

Turning the port off may only fix the problem temporarily.

After restarting FL Studio, the program may automatically assign the port back to Channel 1, which can create the MIDI feedback loop again.

Step 4: Assign the port to an unused channel

Instead of turning the port off, assign the problematic port to a channel that you are not using anywhere else.

For example, set it to Channel 23.

Tip: You can use any unused channel. The important part is that the problematic port is not assigned to the same channel as the active Auriteq input/output configuration.

FL Studio should now keep this assignment instead of resetting the port to Channel 1.

✅ After this: The MIDI feedback loop should no longer occur, and FL Studio should stop freezing, crashing, or becoming unresponsive.

Why this works

FL Studio may automatically reactivate disabled MIDI ports after a restart and assign them to Channel 1.

By assigning the problematic port to an unused channel instead of turning it off, FL Studio is going to to preserve the setting. This prevents the port from being reset to Channel 1 and avoids recreating the feedback loop.


Still not working?

Please make sure you are using the latest version of the Auriteq app and the latest version of FL Studio.

If the issue continues, contact support and include:

  • Your Windows version
  • Your FL Studio version
  • Your Auriteq app version
  • A screenshot of your FL Studio MIDI Settings window
Did this answer your question?

Still need help?

If you’re still experiencing issues, please contact us at support@auriteq.com and tell us your problem. Please include in your email:

  • What DAW and version you’re using
  • What OS you have (Mac or Windows) and which version
  • If you’re on a Mac, whether you have an Intel or Apple Silicon processor