PDC

[George D]

When PDC is enabled the latency is compensated according to the manual.

As you can see in the picture is the PDC enabled or disabled? 

 

[reginaldStjohn]

I believe that the PDC button is in its normal, non-highlighted, state when it is not disabling latency compensation for live input channels. If it is highlighted it is disabling latency compensation.

[David Baay]

Yes, as the documentation shows, the button is to "Override" PDC on "live" (input-monitored) tracks. Note also that you can only override PDC on an input-monitored track if the PDC-inducing plugin is not on that track or in its path to the output.

Edited January 30 by David Baay

[George D]

4 hours ago, reginaldStjohn said:

I believe that the PDC button is in its normal, non-highlighted, state when it is not disabling latency compensation for live input channels. If it is highlighted it is disabling latency compensation.

But the FX are also off when the light of the button is on....

[David Baay]

Yes, the FX button also operates as a bypass/override. There has been a lot of virtual ink spilled over the arguably unintuitive and inconsistent labeling/lighting/functionality of these and other buttons in the Mix module. If we're lucky, the new Sonar will revise the iconography at least.

Edited January 30 by David Baay

[George D]

16 hours ago, David Baay said:

Yes, the FX button also operates as a bypass/override. There has been a lot of virtual ink spilled over the arguably unintuitive and inconsistent labeling/lighting/functionality of these and other buttons in the Mix module. If we're lucky, the new Sonar will revise the iconography at least.

But you said that the PDC isn't working the same way. When the light is off then pdc is on and working. Did I understant it right?

[David Baay]

51 minutes ago, George D said:

When the light is off then pdc is on and working. Did I understant it right?

Yes. In both cases, when the buttons are not lit/engaged, the underlying functions (PDC and FX processing) are working. When the buttons are lit/engaged, the normally working-by-default processes are bypassed/overridden.

[jackson white]

? for the theme editor, one of the 1st changes made here, although the tool tips are accurate when considering the default state.

[Starship Krupa]

I am solidly in the grey=off, lit up=on camp. After all, in the FX rack, lit up button means "effect active." Why invert it in other areas?

The argument against it says that the buttons should be lit up to alert the operator that something is not "as usual." This is how we think of the Mute button, after all. And yes, I finally just set it right using Theme Editor. Unfortunately, this won't be possible with the new Sonar coming out, not on its initial release and possibly never.

This is my mnemonic:

"In the racks FX are off when the button is grey

In Mix Module when its orange the FX have gone away"

It's a tribute to the famous segment of The Court Jester: