Hi Algoriddim Team,
I’ve encountered what seems to be a bug related to pad LED feedback when triggering loops via the controller.
Issue:
- When I activate a loop on the right deck, the corresponding pad blinks as expected, indicating that the loop is active.
- However, when I activate a loop on the left deck, the corresponding pad does not blink at all.
- I’ve compared the MIDI settings, and everything is exactly the same for both decks.
This inconsistent feedback makes it harder to track active loops visually during a performance, especially when relying on pad LEDs.
Could you please look into this?
(See this video for more details)
Is it a bug in the Reloop, or something else?
Hi @DJ_Big_Blender, thanks for the detailed info and video. We tested this on 2 different Mixon 8 units and were not able to replicate this while using the (built-in) MIDI mapping. From your video, you MIDI settings look correct. Please make sure you are using the latest Mixon 8 firmware from Reloop then retest with the (built-in) MIDI mapping to see if you have the same issue with that mapping.
Yes, thanks — that’s a good idea. I’ll do that.
1 Like
You’re welcome @DJ_Big_Blender. Did that solve it for you?
Hi @Slak_Jaw, thanks for asking.
The suggested solution didn’t resolve the issue for me, but it did provide some helpful insights:
When I revert to the built-in mapping, both the left and right pads blink as expected when a loop is activated. In two out of my three custom mappings, this blinking behavior also works correctly.
However, in the one custom mapping where it doesn’t work, I’ve significantly simplified the settings by removing the dual functionality of the pads. For both Hot Cues and Loop Roll, I copied the exact same function from the primary (or secondary) layer to the other — mainly to reduce complexity and minimize the risk of errors.
With the Saved Loop function, copying it to the secondary layer didn’t work as expected, so I left the secondary function empty. The fourth pad bank (Sampler and Neural Mix Solo/Active) remains unchanged.
In this particular mapping, the issue is that the left deck pad does not blink when a loop is activated — even though all settings are identical between the left and right decks.
I’ve have that mapping here for your review.
Thanks for your help!
Hi @DJ_Big_Blender, thanks for the additional info. Since the built-in MIDI mapping is working as expected, then this is likely related to something that you’re doing with your custom mapping. Since the MIDI Learn tool does not support control for flashing LEDs this has to be done in code. Likely you are inadvertently breaking this LED functionality when you modify the mapping. If you have some experience editing XML files, you could probably find a way to fix this behaviour in your custom mapping. I myself, am not super comfortable editing the XML files, so I tend to stay away from this. There are, however, some users in this community that have more experience with this so you could do some searches and reach out to them for guidance. Hopefully that’s helpful. Thanks!
Hi again @DJ_Big_Blender, can you confirm you used the proper MIDI commands for your custom mapping? When mapped to “Saved Loop Activate” the pads blink when active, when mapped to “Saved Loop Reloop” they don’t.
Yes.
Checked and double checked. Both mapped to Saved Loop Activated.
You can check the midi file also. Pads on both left and right decks do have the exact same mapping in my opinion.
Thanks for confirming. Did you move the Saved Loops to a different performance pad section vs the built-in mapping?
No, I didn’t. They are just on “Saved Loops” section like before.
I did run a small test, however, by swapping the midi ‘Saved Loop Activated’ function from Deck 1 to Deck 2 and vice versa. This now caused a blinking LED on the corresponding performance pad of Deck 1 when a loop was activated in the software on Deck 2. However, it did not cause a blinking pad on Deck 2 when a pad was activated on Deck 1.
S somehow, a loop from Deck 1 stubbornly refuses to blink, even though it’s assigned to Deck 2.
I need to wrap my head around what this means.
@DJ_Big_Blender, I found the problems with your MIDI Mapping. You had a bunch of duplicate MIDI commands in your mapping. You had an extra seven “Deck 1: Saved Loop Reloop” commands and an extra “Deck 1: Saved Loop Activate 8” command. I deleted these and everything works as expected now. I have included a fixed copy of your MIDI mapping below.
Reloop Mixon 8(Big Blender-2).djayMidiMapping (288.0 KB)
Hi @Slak_Jaw,
Yes! This completely solved my problem, so many thanks for diving into it so thoroughly. I really can’t thank you enough. 
I had actually looked into this myself to check for any overlap, but obviously didn’t catch it. That’s probably due to the overwhelming list of MIDI commands for a controller stacked on top of each other.
This did inspire me to submit this feature request last week, which would make the MIDI commands much easier to navigate. (Hopefully, that becomes a reality at some point.)
Also, I have no idea how those extra lines got in there, but it would be great if djay had some sort of check to automatically prevent duplicate or unnecessary entries.
Anyway: so happy to report that the left loop pads are blinking now, so I’m all good. 
You’re welcome @DJ_Big_Blender.
