Could it map different axes to different devices？

[Vpn33]

The ability to output to multiple devices simultaneously is great — I can now refactor the code in my fork that handles simultaneous output to the Opossum and make it much less redundant!

Also, I just had an idea: now that you've added multi‑axis and multi‑device support, could it map different axes to different devices? For example, have L0, L1, and L2 output to device coyote3‑1, and R0, R1, and R2 output to device coyote2‑2. As long as the electrodes are positioned properly, this should simulate the effect of a multi‑axis device even better.

[Amethyst-Sysadmin]

It's possible in theory, but is difficult to do with the current design, because the output layer just receives a stereo pulse from the input layer. Having a whole bunch of controls to set mappings between different things also usually doesn't fit very well into a mobile interface.

I think doing something only for users with multiple devices that only works when playing multi-axis funscripts might be too narrow a use case for the amount of work involved. But it's a nice idea, and is something I might consider if I change the design in future to support inputs optionally returning more information (3/4 phase device support might also need something like that).