Thanks for the feedback!
I think I will be implementing the the functions below to the 3 unused pads.
-Trigger Type One-Shoot/Loop
-Play/Pause
-Sync
As far as adding the second page that may be something I look at adding in the future, but this mapping will only focus on Remix Deck C & D control.
I haven't really noticed this, but I have found a different bug and pretty sure its not with my mapping. The bug happens when multiple pads in the same slot are pressed at the same time or in a quickly right after one another. One pad will go solid and play and the other pad that is considered to be "waiting" only it never plays and will continue to flash only to stop if you press this pad. Anyone else seeing this or have the LED's mapped differently?
The outputs I am using for a single pad LED are:
Beat Phase - Modifier Condition: Slot "1" Cell "1" State. Remix Deck "C" = Waiting
Slot 1 Cell 1 State - Modifier Condition: Slot "1" Cell "1" State. Remix Deck "C" Loaded
Slot 1 Cell 1 State - Modifier Condition: Slot "1" Cell "1" State. Remix Deck "C" Empty
Slot 1 Cell 1 State - Modifier Condition: Slot "1" Cell "1" State. Remix Deck "C" Playing
There is quite a bit of LED feedback with is very useful and pretty much necessary to understand what is happening. The issue tends to be with the USB port drawing too much power away from your computer. Try using a powered USB hub this was known to help with my other mappings and windows computers. Here is one that I currently use in my modular setup not a single hiccup
Bookmarks