Scaler 3 and Polybrute Connect MIDI

Scaler 3 Support Bug Reports
,
1

Hello,

I am using Scaler 3 in combination with Polybrute Connect, it’s a VST that connects my DAW to my Polybrute hardware synth. It requires that the Polybrute VST midi device stays untouched.

This normally works fine, but when I place Scaler 3 on Track 1 this completely hangs my Ableton because the Polybrute VST midi device has been ‘stolen’. Causing it to hang.

I found Scaler 3 to be the reason for this by creating a new project and placing Scaler 3 on Track 2 and Polybrute Connect on Track 1, which works fine when I reload the project. But when I place Scaler 3 on Track 1 and the Polybrute Connect on Track 2 and reload the project it completely hangs.

This is the reason I believe Scaler 3 is probably the culprit. Another reason I believe this is that Scaler 3 also uses a stand-alone software which requires access to midi devices.
However, I don’t see why Scaler 3 would need to access midi devices when used as a VST? I am assuming it is accessing midi devices because there I see other reason my Polybrute VST midi device would get ‘stolen’. Should it not just receive the audio and midi buffers from the DAW and leave midi devices themselves untouched?

Please look into this bug. Thank you.

2

HI @Joe50 and welcome to the forum. Scaler is has multiple MIDI out in all instances so accessing the MIDI network is part of its functionality. You shouldn’t have an issue with Polybrute Connect. Can I firstly check you are using Scaler 3.2.2? We made some adjustments to how it accesses MIDI devices.

3

Hi @Joe50 are you using Windows or macOS? If you are on Windows it is possible Scaler 3’s MIDI interface is interfering with your hardware controller plugin. The MIDI interface was added to allow for MIDI routings when running standalone, and to circumvent Ableton Live’s MIDI routing limitations.

We do plan to add the ability to disable this functionality via a coming update which should prevent it from interfering with your Polybrute Connect plugin.

4

Hi @davide @Tristan. This was on Windows. I just updated from version 3.2.1 to 3.2.2 and it seems to have resolved the issue, thanks!