Question about MS encode/decode order in Stereo Widener example

[Yinxi]

Hi everyone,

I’ve been going through the Stereo Widener example in the HISE documentation, and I noticed something that seems strange for me: the routing.ms_decode node appears before the routing.ms_encode node in the signal chain.

However, according to the documentation for routing.ms_encode, it should be placed at the beginning of the chain to encode a stereo signal into Mid-Side, which can then be processed and later decoded with routing.ms_decode.

From Doc about ms_encode : "To use the routing.ms_encode node, you would typically place it in a processing chain with the stereo input you want to encode, and then use a container.multi node to split the signal into its mid and side components. You can then process the components separately and recombine them using a routing.ms_decode node placed later in the chain."

This seems like a contradiction

Image from Hise Documentation :

[d.healey]

@Yinxi I think the docs might be wrong.

The decode splits the signal into mid and side so that they can be processed separately. The encode reassembles the two parts before they go back to the output.

[dannytaurus]

@d-healey In my experience, traditionally the term 'encode' means to convert from L/R to M/S and the term 'decode' means to convert from M/S to L/R.

So maybe it's the names of the modules that are wrong? Although I doubt that will get updated for legacy reasons.

Still confusing though!