Midi::sendMessage: Unknown message type. Ignoring it

I’m sending out a custom Sysex MIDI message via Lua everytime a knob changes a value like this:

local sysexData = { 
    SYSEX_MESSAGE_LENGTH_PARAM_ADJUST,
    SYSEX_COMMAND_PARAM_ADJUST,
    paramHigh,
    paramLow,
    valueHigh,
    valueLow
}

midi.sendSysex (0, sysexData)

Whenever that line is called, I’m seeing this in the debugger (TRACE level):

Midi::sendMessage: Unknown message type. Ignoring it.

I’m not sure what that means. The sysex message isn’t ignored, I can receive it on the device connected to the E1.

Is there something wrong with the way I’m setting up the sysex message?

Does 0 map to PORT_1?

Without actually seeing the data bytes, that is the only thing I can think of.

The globals are PORT_1, PORT_2, PORT_CTRL

1 Like

I’ve changed the line to midi.sendSysex (PORT_1, sysexData) and logged the variables:

22:52:59.757 Midi::sendMessage: Unknown message type. Ignoring it.
22:52:59.772 lua: Sending MIDI Sysex Length=5 Opcode=0 Parameter(high)=0 Parameter(low)=0 Value(high)=0 Value(low)=1
22:52:59.817 Midi::sendMessage: Unknown message type. Ignoring it.
22:52:59.820 lua: Sending MIDI Sysex Length=5 Opcode=0 Parameter(high)=0 Parameter(low)=0 Value(high)=0 Value(low)=65
22:52:59.907 Midi::sendMessage: Unknown message type. Ignoring it.
22:52:59.910 lua: Sending MIDI Sysex Length=5 Opcode=0 Parameter(high)=0 Parameter(low)=0 Value(high)=0 Value(low)=73
22:52:59.968 Midi::sendMessage: Unknown message type. Ignoring it.
22:52:59.971 lua: Sending MIDI Sysex Length=5 Opcode=0 Parameter(high)=0 Parameter(low)=0 Value(high)=1 Value(low)=9
22:53:00.073 Midi::sendMessage: Unknown message type. Ignoring it.
22:53:00.075 lua: Sending MIDI Sysex Length=5 Opcode=0 Parameter(high)=0 Parameter(low)=0 Value(high)=1 Value(low)=10
22:53:00.148 Midi::sendMessage: Unknown message type. Ignoring it.
22:53:00.150 lua: Sending MIDI Sysex Length=5 Opcode=0 Parameter(high)=0 Parameter(low)=0 Value(high)=1 Value(low)=42
22:53:00.223 Midi::sendMessage: Unknown message type. Ignoring it.
22:53:00.225 lua: Sending MIDI Sysex Length=5 Opcode=0 Parameter(high)=0 Parameter(low)=0 Value(high)=1 Value(low)=74
22:53:00.314 Midi::sendMessage: Unknown message type. Ignoring it.
22:53:00.316 lua: Sending MIDI Sysex Length=5 Opcode=0 Parameter(high)=0 Parameter(low)=0 Value(high)=1 Value(low)=82
22:53:00.420 Midi::sendMessage: Unknown message type. Ignoring it.
22:53:00.423 lua: Sending MIDI Sysex Length=5 Opcode=0 Parameter(high)=0 Parameter(low)=0 Value(high)=1 Value(low)=83
22:53:00.496 Midi::sendMessage: Unknown message type. Ignoring it.
22:53:00.499 lua: Sending MIDI Sysex Length=5 Opcode=0 Parameter(high)=0 Parameter(low)=0 Value(high)=1 Value(low)=115
22:53:00.632 Midi::sendMessage: Unknown message type. Ignoring it.
22:53:00.635 lua: Sending MIDI Sysex Length=5 Opcode=0 Parameter(high)=0 Parameter(low)=0 Value(high)=1 Value(low)=116
22:53:00.768 Midi::sendMessage: Unknown message type. Ignoring it.
22:53:00.771 lua: Sending MIDI Sysex Length=5 Opcode=0 Parameter(high)=0 Parameter(low)=0 Value(high)=1 Value(low)=117
22:53:00.933 Midi::sendMessage: Unknown message type. Ignoring it.
22:53:00.936 lua: Sending MIDI Sysex Length=5 Opcode=0 Parameter(high)=0 Parameter(low)=0 Value(high)=1 Value(low)=118
22:53:01.069 Midi::sendMessage: Unknown message type. Ignoring it.
22:53:01.072 lua: Sending MIDI Sysex Length=5 Opcode=0 Parameter(high)=0 Parameter(low)=0 Value(high)=1 Value(low)=119
22:53:01.160 Midi::sendMessage: Unknown message type. Ignoring it.
22:53:01.163 lua: Sending MIDI Sysex Length=5 Opcode=0 Parameter(high)=0 Parameter(low)=0 Value(high)=1 Value(low)=127
22:53:01.311 Midi::sendMessage: Unknown message type. Ignoring it.
22:53:01.314 lua: Sending MIDI Sysex Length=5 Opcode=0 Parameter(high)=0 Parameter(low)=0 Value(high)=2 Value(low)=0
22:53:01.491 Midi::sendMessage: Unknown message type. Ignoring it.
22:53:01.493 lua: Sending MIDI Sysex Length=5 Opcode=0 Parameter(high)=0 Parameter(low)=0 Value(high)=2 Value(low)=1

For some reason it seems your first parameter value is 0 and that might be illegal coming right after the F0

Remember - MIDI messages have the F0, manufacturer ID, machine type, command, then data. The E1 handles the F0 … F7 bracketing, but you still need to supply the correct bytes in between them

What machine/thing is the intended target of this sysex message?

The messages are intended to be received by a custom Reaper control surface plugin I’m writing in C++. I’m receiving the messages just fine in the plugin. Do you think that this approach has drawbacks? Do you think it’s related to the unspecific log from the E1?

Do you call your Lua from a function assigned to a virtual parameter?

It is safe to ignore it. I will get rid of the message in the upcoming release.

1 Like

The Lua function is assigned to a knob. Does that make it a virtual parameter?

I mean the type of message assigned to the knob, like this:

If it is a virtual type, it is safe to ignore it. If not, I will need to know what type of message you have there. I would take a closer look at it then.

Ah yes, that one is set to virtual. So the message is meaningless in my case. Thanks!

1 Like

I will remove it from the trace in the next release.

1 Like