Scaler 3.2 blocks all LoopBe30 MIDI Out ports in FL Studio 2025.2

Scaler 3 Support
1

Scaler 3.2 seems to cause a conflict with LoopBe30 in FL Studio 2025.2.
With Scaler 3 loaded, FL Studio says every LoopBe30 MIDI Out port is already in use. Removing Scaler 3 instantly fixes the issue.

2

Hi,It’s me again.

I just installed the previous official version of Scaler 3 (v3.1.3) and the issue has completely disappeared.

This confirms that the bug was introduced in version 3.2.0 on your end.

I’m looking forward to a fix in an upcoming update.
Thank you in advance for your feedback and for addressing this problem.

Best regards.

3

Hi @Haze And welcome to the forum. Thanks for investigating. Not sure what LoopBe30 is but makes sense that Scaler 3 is using Virtual MIDI Out Ports. Do you ned LoopBe30 if you have Scaler 3?

4

Hi Davide,

I mainly use LoopBe30 to capture in MIDI the chords or melodies generated by VST instruments/plugins that harmonize or enrich an incoming MIDI stream (e.g., UJAM Virtual Pianist etc.).

This is a different approach from that of Scaler 3. However, these two approaches can complement each other and one should not interfere with the other.

5

Hi @Haze Understood. Scaler 3 won’t be stealing the Virtual MIDI Outputs I wouldn’t imagine. I use other hosts in Logic on a Mac alongside Scaler 3 no problem, not sure what’s going on with LoopBe30 but maybe some other users could contribute?

6

In any case, this is a change you made between version 3.1.3, which works for me, and version 3.2.0, which does not.

7

Just be clear to try and help you. Scaler 3.2 introduced External MIDI Out - natively. LoopBe30 must be doing some kind of strange MIDI routing, loop, feedback, In/Out/Thru. We are doing nothing unusual that is not native so you should try and tinker with LoopBe30 settings or contact them directly. I do note that it has some unusual MIDI behaviour set by default"

The most likely reasons LoopBe30 conflicts with other MIDI plugins are that

its ports are unintentionally muted in the LoopBe30 application, or they are being incorrectly selected by the plugin itself. To resolve this, check the LoopBe30 application to ensure the correct ports are not muted, then verify that your other plugins are configured to use the correct MIDI ports and that you are using compatible plugin and host versions (e.g., both 64-bit).

Common solutions

  • Check LoopBe30 settings: Open the LoopBe30 application and look at the list of ports. If a port is selected (checked), it is muted. Uncheck any ports you want to use for routing.
  • Ensure correct port selection: Open the settings for the plugin that is not working and verify that it is set to receive MIDI data from the correct LoopBe30 output port. You may have multiple ports available. If it’s trying to use a port that’s “muted” (selected) in the LoopBe30 application, it will not work.
  • Match plugin and host bit versions: If you are using a 64-bit version of your host (like FL Studio), you must also use a 64-bit version of your plugins. A 32-bit plugin running in a 64-bit host (or vice versa) will not work correctly, as seen in this Image-Line Forums thread.
  • Use MIDI IN/OUT, not THRU: Some older devices use an “IN” and a “THRU” port. When using a keyboard with a MIDI output, ensure your connection uses the “IN” and “OUT” ports. If you are using the “THRU” port, you must disable its THRU function to avoid potential issues, as described in this article from Onj.Me.
  • Consider alternative drivers: If the issue persists, consider using a more modern, actively maintained virtual MIDI driver like loopMIDI or rtMIDI, which may be more compatible with current software.
8

I haven’t used LoopBe30 in years but try disabling the shortcut detection in the port setup dialog. I seem to recall it caused some problems for me in some situations.

But I would definitely recommend switching to use something more modern like the free and excellent loopMidi: loopMIDI | Tobias Erichsen

1 Like
9

Thanks for your advice!
I’ve finally found a solution.The trick is to assign any MIDI port number to one of LoopBe30’s outputs in FL Studio before launching Scaler 3. Once that’s done, all the issues disappear completely.
Afterward, I can freely change or even remove that port number — no port actually ends up being used.

Following this step, I’ve also noticed that the specific LoopBe30 output no longer appears in Scaler 3’s “MIDI Output Device” list (unlike before), which is actually perfect in this case.