ReaComp Output mix meter

[matt_t]

Small buglet -

In short: the peak value at the top of the Output mix meter doesn't always react when a new peak is reached.

In long(!): it seems to always be OK immediately after adding ReaComp, setting the paramaters and pressing play. However, if you do any tweaking and *then* press play, that's when the meter reading can "stick" (not sure if it does 100% of the time, but a lot of the time).

If it's relevant, my habit is to zero the Output and GR meters after I've tweaked. (Might be nice if it did it automatically on stop/restart, incidentally.)

v5.981 btw

Thanks

Edit: literally seconds after posting, I've opened up Reaper and it's done it after the first "play", without any tweaking. Sod's law!

[matt_t]

Bumping this annoying intermittent fault. Surely not too much to ask that an output meter always shows the correct value, especially in a highly-regarded plugin like ReaComp? Please

[matt_t]

Not so much another bump as a cri de coeur

Why can't the ReaComp output meter always show the correct peak value?

All the JS plugs I regularly use always do, e.g.:

Audio Statistics (I should hope so too...)
Tilt Equalizer
Volume Adjustment
Convolution Amp/Cab Modeler
Dirt Squeeze Compressor
Distortion

I don't use ReaXcomp much, but have never seen that be wrong, and don't use ReaGate at all so have no info.

But with ReaComp it can either

1) work correctly
2) sometimes if there's a peak in one channel followed quickly by one in the other, it'll react to the first but then miss the second. Or possibly if they're both in the same channel
3) be out by 0.1dB (always too low), which I guess is some kind of rounding issue
4) display some apparently random value (again, always too low)
5) just not react at all

This is most easily noticed in solo mode, with no FX after ReaComp, no routing issues, no folder FX etc, no reverb etc, no FX on the master track. ReaComp's meter should show the same peak as the Master, but doesn't always.

A small bug, no doubt, but it is a bug, and I have seen equally small ones reported and fixed. And this one has been "bugging" me for a long time!

FWIW I'm still on REAPER 5.99 32-bit (though I tried a portable 64-bit install and that didn't make any difference), Windows 8.1. Just for the hell of it I'll attach my REAPER.ini as well

[matt_t]

Anniversary (plus a few days) of the last bump. (Edit: Or is it? Thought it was 12 April but might have been 4 December. Oops.)

One other thing I can add is that audio device settings make a difference, e.g. with ASIO4ALL setting the buffer size to 2048 from my usual 512 lessens the problem somewhat. Can't imagine why that would be, but it does...

[matt_t]

Is it really that long since I bumped this?!

[bobobo]

to chime in


the output mix meter will reset if the graphics are redrawn, switch to another fx in the same fxchain and than back to the reacomp while playing.

i don' t asume it as a real bug, more something on purpose, the question is, which

[matt_t]

Thanks for the calming attempt to talk me down from the ledge , but *is* a real bug. No other plugin does this.

I've just managed to LICEcap it, which was a pain since - in true "intermittent bug" fashion - it went away as soon as it was being ovserved, a bit like the interference pattern in the quantum double-slit experiment. But only a bit, since it did come back and was recorded.

Note:
A) Bass track meter (track is exclusive soloed)
B) Master track meter
C) ReaComp output mix meter



First time I hit play the track meter and master meter both correctly say -13.8 but the ReaComp meter says -15.7. It keeps repeating this wrong value whenever it does get it wrong, for some reason. Then I reset the meter, hit play again and it gets it right this time.

Nothing to do with graphics redraws as far as I can see. There are no more of them when it gets it right than when it gets it wrong.

If the ReaComp meter is there for anything it's to show the volume of the loudest sample that leaves the plugin, but it doesn't always. That's a bug, admittedly a small one, but it ... bugs me.

[Justin]

ah yes, meter decay. fixing!