Understanding cross talk with dual mono input

[Alx_d]

I configured one input on the ED10 as a Dual Mono Input (DMI) and used a single TS cable. When I look at the unused trigger for the second dual mono input I see that when I strike the pad for the first dual input the Scan/Hold/Decay match what I see on the used input (Auto select off).
I then used a TRS cable with splitter, same setup as above, and I see the same results.
I then short the input of the unused input using the splitter again, and I still see the Scan, hold/Decay trigger match the first input.
Why am I seeing this? To me this is telling me there is crosstalk between the dual mono inputs.
I do not see this on the the other 9 inputs (a mix of stereo and dual mono inputs), so it appears to be only per input and not across all inputs.
I assume this is normal but I would like to understand how this effects the dual mono inputs when I use both of the inputs with a TRS cable a splitter?
The gain is set to 1 and the threshold is set as low as it can go so that when sitting idle the unused input is not trigger even when striking the first dual mono input.

Version 1.5.0_18
Firmware 1.5.0_16

Below is the screen shot of the unused input.

ED10 Input Dual Mono.PNG (86.86 KiB) Viewed 443 times

[Rob]

I configured one input on the ED10 as a Dual Mono Input (DMI) and used a single TS cable. When I look at the unused trigger for the second dual mono input I see that when I strike the pad for the first dual input the Scan/Hold/Decay match what I see on the used input (Auto select off).
I then used a TRS cable with splitter, same setup as above, and I see the same results.
I then short the input of the unused input using the splitter again, and I still see the Scan, hold/Decay trigger match the first input.
Why am I seeing this?

It's probably a bug. When in dual mono mode, the two inputs should act as if they are separate inputs. I'll see if I can reproduce the behavior you are talking about.

[Rob]

Confirmed bug. The issue is merely a display issue. With auto-select off, and the second half of a spilt input selected, the transient from the first half is being displayed when it shouldn't. Fixed for the next version and thanks for reporting the issue.