Does the Monitor Control Room knob on the Artist Control do anything?

[Ben Wood]

Might be old news but the Monitor Control Room knob works on the Artist Mix
Im running Eucon 4.8.3.29.
Make a master fader, right click, click Eucon Monitor (at the bottom).
Cheers

[Ru_C]

Just picked up a used Artist Control & Omni, to upgrade my home/office setup.

First thing I assumed would work of course, was the 'Monitor Control Room' knob on the Artist Control, controlling the 'Monitor Control Room' function/knob on the Omni.

Does this really not work? Or am I using it wrong & need to rtfm more?

cheers

[BScout]

Originally Posted by Ru_C

Just picked up a used Artist Control & Omni, to upgrade my home/office setup.

First thing I assumed would work of course, was the 'Monitor Control Room' knob on the Artist Control, controlling the 'Monitor Control Room' function/knob on the Omni.

Does this really not work? Or am I using it wrong & need to rtfm more?

cheers

No. And never will. The Omni does not support Eucon so can't be controlled.

[Ru_C]

Originally Posted by Ben Wood

Might be old news but the Monitor Control Room knob works on the Artist Mix
Im running Eucon 4.8.3.29.
Make a master fader, right click, click Eucon Monitor (at the bottom).
Cheers

Any kind of hack to stop the master fader going *above* 0db, when it keep turning it to the right?

It would essentially work as intended (In Pro Tools anyway), if I can achieve that.

[Ru_C]

Originally Posted by Ru_C

Any kind of hack to stop the master fader going *above* 0db, when it keep turning it to the right?

It would essentially work as intended (In Pro Tools anyway), if I can achieve that.

Ok, I'm talking to myself now on this point (it comes to us all with old age), but is this a solution?

As I can't stop the Master fader from going to +12 when I turn the Artist Control Monitor knob fully clockwise, I've just put a trim plugin on the Master fader, & set it to -12db (-12.5 to be safe).

This basically seems to work, & I now have a functioning volume knob, that essentially hard-stops at '0 db'

Have I just found a workaround? or is there something horrible happening with floating-point vs fixed-point maths on outputs, that I don't understand?