FIXED: DAT execute triggering on non-selected channels

Bugs
1

DAT_execute_selected_channel.toe (7.6 KB)

I encountered some unexpected behaviour with the DAT execute that I did not experience in previous versions. I am using some buttons to drive a DAT execute, and a select to isolate the channel I want to look at with the DAT execute. Expected behaviour would be that the DAT execute triggers on the off/on and the on/off of the selected channel.

Instead the DAT execute triggers on the off/on of every channel before the selected channel index, and on both off/on and on/off of the selected channel. The issue seems to persist with the CHOP execute as well. Example project file attached

Thanks!

system info:
Lenovo Legion 5 15IRX10 Windows 11

Nvidia RTX 5060 Driver 610.88

16GB RAM

2

Hi @Sebby,

thanks for sending this in. Weird one. The DAT Execute runs on button 1 to 3 - curiously button 4 is fine.
I can’t replicate this bug for the CHOP Execute DAT, here everything runs fine for me.

We are having a look
cheers
Markus

3

Thanks for the report. The DAT execute issue will be fixed in the next official release. We can’t reproduce any issue with the CHOP though.

4

Thanks! I looked back at my example file and looks like I made a diagnostic error, no issues with the CHOP execute