Bug with RadioDJ

Midi plugin Bug reports
1

Hello,

I am using the MIDI plugin with a Stream Deck XL, the loopMIDI emulator, and the RadioDJ broadcasting software.

I’ve had this setup for several months now, and everything has been working perfectly.

However, for the past two days, I’ve been having issues when trying to trigger audio jingles via RadioDJ using the MIDI plugin. The jingles start playing for a fraction of a second and then cut off immediately.

Please note that I didn’t have any issues before with this exact same setup. Currently, my other MIDI commands are working fine in the software: I can control track volumes using the dials, and I can start and stop my main playlist as well as my auxiliary players.

My issue is strictly isolated to the Instant Players used for the jingles.

Here are the logs:

2026-06-25 14:45:51.2254 44822,84ms INFO 99 Midi Logger [Logfile cleared]
2026-06-25 14:45:52.7428 1517,39ms DEBUG 99 NoteOn ReceivedSettings [b4bd2acead128048eeeec41d6281c9d1 lgn - ]
2026-06-25 14:45:52.7428 0,01ms INFO 98 Midi Logger [logging level 1 started (4.3.0.1) (create)]
2026-06-25 14:45:52.7428 0,02ms DEBUG 99 NoteOn ReceivedSettings [b4bd2acead128048eeeec41d6281c9d1 rb - ]
2026-06-25 14:45:52.7428 0,01ms DEBUG 99 NoteOn ReceivedSettings [b4bd2acead128048eeeec41d6281c9d1 Unknown property: rb - ]
2026-06-25 14:45:52.7428 0,00ms DEBUG 99 NoteOn ReceivedSettings [b4bd2acead128048eeeec41d6281c9d1 selectedCycleType - ]
2026-06-25 14:45:52.7429 0,00ms DEBUG 99 NoteOn ReceivedSettings [b4bd2acead128048eeeec41d6281c9d1 selg - Default group]
2026-06-25 14:45:52.7429 0,00ms DEBUG 99 NoteOn ReceivedSettings [b4bd2acead128048eeeec41d6281c9d1 smc - 0]
2026-06-25 14:45:52.7429 0,00ms DEBUG 99 NoteOn ReceivedSettings [b4bd2acead128048eeeec41d6281c9d1 smip - No MIDI Input]
2026-06-25 14:45:52.7429 0,00ms DEBUG 99 NoteOn ReceivedSettings [b4bd2acead128048eeeec41d6281c9d1 smop - loopMIDI Port]
2026-06-25 14:45:52.7429 0,01ms DEBUG 99 NoteOn ReceivedSettings [b4bd2acead128048eeeec41d6281c9d1 sno - same]
2026-06-25 14:45:52.7429 0,01ms DEBUG 99 NoteOn ReceivedSettings [b4bd2acead128048eeeec41d6281c9d1 snt - C3]
2026-06-25 14:45:52.7429 0,00ms DEBUG 99 NoteOn ReceivedSettings [b4bd2acead128048eeeec41d6281c9d1 tf - ]
2026-06-25 14:45:52.7431 0,18ms INFO 98 Midi Logger [logging level 1 ended (change)]
2026-06-25 14:45:52.7431 0,01ms INFO 98 Midi Logger [logging level 2 started (4.3.0.1) (change)]
2026-06-25 14:45:54.7458 2002,77ms DEBUG 95 NoteOn KeyPressed [b4bd2acead128048eeeec41d6281c9d1 Port(loopMIDI Port) Channel(0) - Key(1) - Velocity(127)]
2026-06-25 14:45:54.7459 0,11ms DEBUG 95 Connection Send_NoteOn [b4bd2acead128048eeeec41d6281c9d1 Sending Channel(0), Key(1), Velocity(127)]
2026-06-25 14:45:54.7467 0,74ms DEBUG 95 MidiController Send_NoteOn [b4bd2acead128048eeeec41d6281c9d1 message successfully sent: NoteOnMessage, InPort:No MIDI Input, OutPort:loopMIDI Port, Channel:0, Key:1, Value:127]
2026-06-25 14:45:54.7468 0,09ms DEBUG 95 StateThrottler SetState [b4bd2acead128048eeeec41d6281c9d1 same state as last, ignoring: State(False)]
2026-06-25 14:45:54.7470 0,20ms DEBUG 103 MidiController NoteOn_Received [MidiController message received: NoteOnMessage, InPort:loopMIDI Port, OutPort:, Channel:0, Key:1, Value:127]
2026-06-25 14:45:54.9457 198,72ms DEBUG 92 NoteOn KeyReleased [b4bd2acead128048eeeec41d6281c9d1 Port(loopMIDI Port) Channel(0) - Key(1) - Velocity(127)]
2026-06-25 14:45:54.9458 0,07ms DEBUG 92 StateThrottler SetState [b4bd2acead128048eeeec41d6281c9d1 same state as last, ignoring: State(False)]
2026-06-25 14:45:59.5545 4608,69ms DEBUG 99 NoteOn OnSendToPlugin [b4bd2acead128048eeeec41d6281c9d1 ViewLog : Yes]

I think the issue started after the 4.3 update.

Thx

T-O

2

I would greatly appreciate it if you used the “Upload log” button instead of attaching sections of the log to a post. Formatting is ruined when the log is attached to a post, and the upload button uploads more information.

The only odd thing I see in the log file is that you use the same loopMIDI port for both input and output, which, from my perspective, is a no-no. However, in this case, it probably has no impact on the behavior.

I can see the plugin sending key 1 with velocity 127 on channel 1 via “loopMIDI Port” and receiving the same command on “loopMIDI Port” as input. This input seems to be ignored, and since the only activity on the MIDI port is that single command, it’s a mystery why you’re seeing different behavior now.

Version 4.3 behaves the same way as the previous version when sending and receiving MIDI messages, unless you made changes to the MIDI System page. Unfortunately, because you cleared the log file, I can’t see how the plugin connected to the MIDI ports.

You mention that other commands work fine - do these other commands also use the Note On/Off action, or are they other kinds of commands? And do these other commands use the same port, or other ports? I’m just trying to understand if the issue is restricted to the Note action or something else.

3

Thx for you help.

I set the MIDI Input to disabled by leaving that section blank, but the problem is still there.

For the other commands, they are also Note On/Off and they work fine.

I swapped the controls to trigger the jingles using the rotary knobs on a different MIDI note, but the issue persists.

4

Since the plugin only sends a single Note On command, I find it hard to see how this could behave differently from the previous version, which also sent a single Note On command. I need more information. Please do this:

  1. Enable extended logging
  2. Quit Stream Deck (notification area icon - quit)
  3. Restart Stream Deck
  4. Press the button that does not work
  5. Press a button that works
  6. Upload the log, using the upload log button
  7. Post the log ID from the upload.
5

ca380484-8007-45d8-ad41-c0e9d7f2a992

6

Thanks.

Which note command is failing? In your first post, the log snippet showed key 1. If that’s the command that fails and you pressed that button in the latest log, I would say you have a faulty Stream Deck device.

I can see the button for the key 1 command being loaded and unloaded numerous times, but it never logs a key press.

7

Yes the problem is with the key 1, but i didn’t change the setup since month and RadioDj hasn’t been updated in months.

i’ve try with an other Streamdeck, i have the same issue.

8

Well, if you pressed that key during logging, the Stream Deck software didn’t tell the plugin about it. If you have the same problem on another key or device, I really don’t know what’s causing it. The plugin isn’t notified that you press the button, so it can’t do anything.

I suggest you create the same configuration from scratch (not copy/paste) on a different key or device to see if the behavior is different.

If there are still problems, I suggest the following.

  • Ensure extended logging is enabled.
  • Clear the log file.
  • Press a functioning button once.
  • Press the faulty button once.
  • Press the functioning button once more.
  • Upload the log file.

Please don’t switch profiles and pages or perform other actions, since that clutters the log file and makes it harder to locate the interesting parts.

9

14c8dcc1-2db0-403e-8555-4b974f1e10ad

I pressed the Key 2, the sound started and then stopped instantly. Then same manipulation with the Key 3

10

If you made the three key presses I asked for, one of them is missing from the log file.

I cannot see any key press for key 1, which I assumed was the one with an issue. I can see key presses sending key 2 and key 3; both of them are successful.

If, during that logging, only keys 2 and 3 were supposed to be sent, everything works as expected from the plugins’ perspective. The commands are sent as configured, and no side effects are observed. If the result is not as expected, the issue lies elsewhere.

11

Any of my keys are bugged when they are used on my instant players.

Can i, please, have an access to an older version of the plugin to test with it ?

12

The plugin is not the problem, but I’ll PM a link to the previous version.