ACE routing

[Ploki]

I'm studying ACE.
default routing:
- Hardwired audio
- hardwired mod
- default audio
- default mod
I'll just fold it down to HW/Def because mod/audio doesn't really matter in ACE right, it's all the same signal?

As far as i can tell:
- Hardwired audio is means that there is NO INPUT on the destination you can over-ride. You can however split (i.e. VCO > MIX hardwire, but you can drag a signal from VCO anyway)
- Default audio means that there's an input on the destination which breaks the connection on the DESTINATION. But dragging it from the SOURCE behaves like with hardwired - a split, and doesn't break the connection, the default connection remains connected, right?

I think this is the part that confused me.
Also the fact that i can perform splits on the input jacks.
These two connections are identical, right? They just look different?

Screenshot 2022-09-29 at 18.45.20.png

Screenshot 2022-09-29 at 18.45.27.png

Also, there appears to be a bug, if i perform an "inlet" split, and decide to change the modulator on the inlet, the cable connection doesn't change but the source changes anyway.
(Screenshot1: the split on the m-wheel) - if i drag another source to PW, the cable will still display as if it's coming from m-wheel/VCO1 split.

For some reason, Bazille makes more sense to me than ACE. :/

[Howard]

1) Upper image: the lower connection is between two inputs - look up "daisy" chain in the user guide.
2) Lower image: the phrase "inlet split" makes no sense. The VCO1 output is being patched to two inputs: LFO level modulation (normalled to mod wheel) as well as VCO1's own pulse width.There is no "split on the m-wheel" here.
3) Tip: Click on the u-he badge top right and select "User Guide" As I wrote it, I think it's quite readable!

[pdxindy]

As I wrote it, I think it's quite readable!

[Ploki]

1) Upper image: the lower connection is between two inputs - look up "daisy" chain in the user guide.
2) Lower image: the phrase "inlet split" makes no sense. The VCO1 output is being patched to two inputs: LFO level modulation (normalled to mod wheel) as well as VCO1's own pulse width.There is no "split on the m-wheel" here.
3) Tip: Click on the u-he badge top right and select "User Guide" As I wrote it, I think it's quite readable!

i somehow skipped the page with daisy-chaining. Thanks, makes perfect sense now.

Yes, the manual is great! I think what confused me is that i spent more time with bazille than ACE and hardwired/defaults threw me off

except this i still think is a bug:
if i drag a new cable from a NEW output to an already daisychained connection, the cable will change color but it won't show a new cable coming from that output.
So it won't "Break" the chain, but it will still use the new output as the source which can be visually confusing.
i.e. here:
Blue is VCO1, Yellow is SUB1, Grey is VCO2. I think. (It's not)

Screenshot 2022-09-30 at 08.46.56.png

Changing skins "fixes" the cables and rearranges them as they're supposed to be: (same confing as upper screenshot)

Screenshot 2022-09-30 at 08.48.21.png

[tasmaniandevil]

Yes, that's a glitch in the matrix.

[Ploki]

follow up:
circuit bending:
- Crosstalk just spills everything into everything and makes a mess? Literally any knob i turn when i enable crossover does something.
- SLOP - detunes all VCOs including LFOs - but does it also detune Key Follows? It's hard to tell.
- OSC cap : destroys VCOs output, BUT NOT LFOs? Right?

(I’m trying to rearrange ACE so it makes sense in my head in a single page. As much as i like monolith i keep switching bAck to stock, but stock is also a field of knobs). Every “simple” u-he synth i try to skins turns out not so simple

[Howard]

Defining colours for cables in ACE or Bazille was always hit-and-miss, but I've learned to live with it. I'll ask for it to be improved anyway