small issues with JS routing matrix...

[liteon]

I've noticed a couple of things:

These are both for R3(alphas) and R2.55

I.

- insert a track
- add any js fx on it
- check the routing matrix (2ins 2outs btn) - looks ok
- go to the track routing panel and add more channels (from 2 to 8 for example)
- check the routing matrix for this plugin again:


- the matrix hasn't updated for the additional channels. clicking on the first two channels will do so.

II.

I think there is some sort of a performance leakage with the JS routing.

an example for 8ins 8out:


by disabling one of the channels 2x more cpu usage (from 2% to 5%)is required by this fx. there is an exponential dependence here, if 64channels are enabled for the track, disabling one of the routings will require 5x more (or so) CPU i.e from 20% cpu to 100% cpu. result is a freeze and restart is required.

---
The above are present only for JS fx not for any VSTs.
I've tried ReaStream(8ins 8outs) and disabling any routing from the matrix reduces CPU usage.