Scaler 2.7.2 changes synth parameters when opened with a Logic External Instrument

Scaler 2 Support
1

Hello,

When I select and load Scaler as a Midi FX plugin to run into the Logic External Instrument plugin, my OB6 hardware synth patch settings all change and the patch becomes completely messed up.

I have used a midi monitor and I can see that when I open Scaler it is sending all of the below to the OB6. It also does this with my other hardware Korg synth so I don’t believe its something specific to the OB6.

If I load Scaler as a midi FX into a virtual instrument all the data below is not sent.

It does it every time both in Rosetta and M1. Logic 10.7.6

Has anyone else experienced this?

Thanks.

20:16:49.081 To OB-6 Control 2 Registered Parameter LSB 4
20:16:49.081 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.081 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.081 To OB-6 Control 2 Registered Parameter LSB 3
20:16:49.081 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.081 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.081 To OB-6 Control 2 Registered Parameter LSB 4
20:16:49.081 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.081 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.081 To OB-6 Control 2 Registered Parameter LSB 3
20:16:49.081 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.081 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.081 To OB-6 Control 2 Registered Parameter LSB 4
20:16:49.081 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.081 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.081 To OB-6 Control 2 Registered Parameter LSB 3
20:16:49.081 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.081 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.081 To OB-6 Control 2 Registered Parameter LSB 4
20:16:49.081 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.081 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.081 To OB-6 Control 2 Registered Parameter LSB 3
20:16:49.081 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.081 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.081 To OB-6 Control 2 Registered Parameter LSB 4
20:16:49.081 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.081 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.081 To OB-6 Control 2 Registered Parameter LSB 3
20:16:49.081 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.081 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.081 To OB-6 Control 2 Registered Parameter LSB 4
20:16:49.081 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.081 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.081 To OB-6 Control 2 Registered Parameter LSB 3
20:16:49.081 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.081 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.081 To OB-6 Control 2 Registered Parameter LSB 4
20:16:49.081 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.081 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.081 To OB-6 Control 2 Registered Parameter LSB 3
20:16:49.081 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.081 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.081 To OB-6 Control 2 Registered Parameter LSB 4
20:16:49.081 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.081 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.081 To OB-6 Control 2 Registered Parameter LSB 3
20:16:49.081 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.081 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.081 To OB-6 Control 2 Registered Parameter LSB 4
20:16:49.081 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.081 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.081 To OB-6 Invalid 30 bytes
20:16:49.081 To OB-6 Note Off 7 C♯-2 0
20:16:49.081 To OB-6 Invalid 467 bytes
20:16:49.082 To OB-6 Control 2 Registered Parameter LSB 3
20:16:49.082 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.082 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.082 To OB-6 Control 2 Registered Parameter LSB 4
20:16:49.082 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.082 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.082 To OB-6 Control 2 Registered Parameter LSB 3
20:16:49.082 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.082 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.082 To OB-6 Control 2 Registered Parameter LSB 4
20:16:49.082 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.082 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.082 To OB-6 Control 2 Registered Parameter LSB 3
20:16:49.082 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.082 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.082 To OB-6 Control 2 Registered Parameter LSB 4
20:16:49.082 To OB-6 Control 2 Registered Parameter MSB 0
20:16:49.082 To OB-6 Control 2 Data Entry (coarse) 0
20:16:49.082 To OB-6 Control 2 Bank Select 0
20:16:49.082 To OB-6 Invalid 7 bytes
20:16:49.082 To OB-6 Invalid 14 bytes
20:16:49.082 To OB-6 Note Off 7 C♯-2 0
20:16:49.082 To OB-6 Invalid 2 bytes
20:16:49.082 To OB-6 Control 2 Data Entry (coarse) 0

2

Scaler 2.7.2 is supposed to fix this. Is that the version you are running?

3

Out of interest, if you are on M1 you should see the following (FILTER SYSEX MESSAGES), can you try turning it off and see if it stops the data send? I’m not at my studio to try and emulate but if it’s a scaler issue maybe @Ed1 can help?

Screenshot 2022-12-28 at 3.43.59 pm

4

Thanks for the replies.

When Scaler is loaded with (FILTER SYSEX MESSAGES) off by default it still sends the data.

Scaler version is 2.7.2

5

Can anyone explain why Scaler is sending this data?

Thanks.

6

Hi @Optimo

if those messages are sent when Logic is running with Rosetta, I would think this is not related to the M1 issue with the sysEx messages. The other M1 issue is completely fixed under Rosetta which might indicate this is a different issue.

Apart from the sent messages is everything working as expected?

Have you tried with the “FILTER SYSEX MESSAGES” setting ON in Scaler? Is there any difference?

Thanks,
Ed

7

Hi Ed,

Thanks for getting back to me.

It does this when filter sysex is on or off.

Once scaler has opened it works as expected.

When I load scaler it sends all those messages. Something in that data send is changing the patch parameters on my hardware synth.

Sometimes I have to power cycle the synth because all the settings are all over the place.

8

Hi @Optimo

Logic sends some initialization MIDI messages when adding a plugin. Scaler in this case is just passing them to your synth. Those messages should not mess up with your config though.

Do you have Logic configured to use MIDI 2.0? There’s a checkbox under “Settings > MIDI” in Logic Pro. Check your current configuration, maybe enable MIDI 2.0 and give it a try.

9

Hi Ed, thanks for getting back to me. I’ll check this Thursday when I’m back at the studio and confirm.

10

Hi Ed,

I tried with Midi 2.0 enabled and no controller messages pass through scaler to the ob6. This means I cannot control any of the synths parameters (cutoff, resonance etc.) unless I remove Scaler from the midi insert.

With midi 2.0 disabled. It loads and sends all the data from my original post which changes things like filter cutoff. Once scaler is loaded if I then recreate the patch everything works.

The OB6 uses NRPN could this have something to do it?

Thanks.

11

Hi @Optimo

The messages sent by Logic seem to be NRPN message but this shouldn’t be an issue.

Did you try with disabling the “FILTER SYSEX MESSAGES” setting in Scaler? Does it make any difference?

Thanks,
Ed

12

Hi Ed,

It doesn’t make any difference unfortunately.

I have also loaded the Logic midi plugins and monitored the midi output and none send out all the data that Scaler does in my first post.

13

:thinking:

On my machine, I get the NRPN messages when loading any third party plugin in the MIDI FX area.

Do you use NRPN to communicate with your synth? If not, as a workaround maybe you can disable NRPN in the OB6 so it does not mess with your presets.

We are still investigating if there is anything we can do in Scaler to prevent this from happening.

14

Hi Ed,

I do use NRPN for the high resolution filter parameter changes etc.

For now I am making sure that everything is saved before loading an instance of Scaler.

Appreciate you looking into this.