[REAPER] track grouping bug

[Chris-S]

Hi,
is track grouping not used so much? Seems to be a bit buggy.

Example (2 tracks):

Put both tracks volume fader to -20 db or so. Set up a group (shift-G):

track 1: vol master
track 2: vol slave, vol reversed

turn that group on.

now: move track 1 volume fader. Track 2 volume slider moves in the inverse direction -> okay.

but: once track 1 volume is set to -inf, it stops working. Moving slider 1 now leads to a "jumping" of slider 2.

[Chris-S]

Second question what does "Do not master when slaving" mean?

[Chris-S]

Assuming it's the "-inf" thing which makes the trouble an easy fix would be to limit the minimum db for grouped faders to -100 or so.

[EvilDragon]

Why not post on Reaper forums

[Chris-S]

Because I have no account and want to limit on one forum.

[yellowmix]

Then how do you expect them to address this?

[Chris-S]

Have just contacted them via mail.

[lfm]

Second question what does "Do not master when slaving" mean?

When grouping - a master controls a slave - but what happends when you move a slave???
And that could go nested on many levels.

That option tells you should not have Masters touched as you do things to slave - as I recall.
It's in the manual and ran 5.4 trial this summer only.

But something regarding that.

EDIT: From manual
"Use the Flag: No Slave-Master settings to ensure, for
example, that a track which is a master in group 1 and a
slave in group 2 will not act as a master in group 1 when
being slaved in group 2."

[Chris-S]

Answer from Cockos support:

This behaviour is expected due to the non-linear working of the faders and the limited
mouse resolution.

As a workaround use automation instead of grouping.