at present, TAPE can be routed to softcut input, but not to supercollider input.
this is the current routing chart.
(there have also been requests for a softcut->supercollider route, which would alllow lots of feedback.)
it’s not hard to add routes, though it is a little tedious/finicky to add all the relevant glue. @Dewb contributed the latest additions in this PR.
adding routes does have a small impact on CPU usage of mixer client. viz., at present there is no mechanism for conditionally disabling the processing of a route when its level is zeroed.
given that eventually, every route will be requested, it might make sense to simply implement (yet another) fully modular framework within the crone mixer client. but i’m not in a hurry to do this.