[7.15] MCP Meter readout LUFS-S (current) displays 'max' value instead

[Vorticist]

Demonstration: https://www.youtube.com/watch?v=bF-qvPwEvAU

- Duplicate a track
- Set one to meter LUFS-S (readout current) and the other LUFS-S (readout max)

Unless I'm missing something, it seems tracks set to meter LUFS-S (readout max) and LUFS-S (readout current) are displaying the same - the readout seems to display the recent max value in both cases instead of a 'current' readout. Very small and specific but would be great to have a fix for my workflow.

Macbook Pro M2 Max
Ventura 13.6.1
Reaper 7.15

[schwa]

Originally Posted by Vorticist

Demonstration: https://www.youtube.com/watch?v=bF-qvPwEvAU

- Duplicate a track
- Set one to meter LUFS-S (readout current) and the other LUFS-S (readout max)

Unless I'm missing something, it seems tracks set to meter LUFS-S (readout max) and LUFS-S (readout current) are displaying the same - the readout seems to display the recent max value in both cases instead of a 'current' readout. Very small and specific but would be great to have a fix for my workflow.

This seems to be working as expected. "Readout" means the number that is displayed above the meter, which is typically a max-hold value, but in the case of "LUFS-S (readout=current)", the number displays the current value. In this screencap you can see the left-hand track holds the max value for the readout and the right-hand track does not.

[Vorticist]

Originally Posted by schwa

This seems to be working as expected. "Readout" means the number that is displayed above the meter, which is typically a max-hold value, but in the case of "LUFS-S (readout=current)", the number displays the current value. In this screencap you can see the left-hand track holds the max value for the readout and the right-hand track does not.

Thanks, I didn't try changing themes - switching to default and then back to my current theme seems to have fixed it!

[elcalen]

I did a quick test on my end, two tracks with the same audio item, and it sure was looking like the number was staying the same on both tracks, and never going back down in quieter parts, even with the "current" meter. (7.15/Linux)

EDIT: For what it's worth, I have the master track loudness meter also set to LUFS-S/current, and that works as expected. Unlike the track meter readout, the master track readout goes up *and* down.

[CAlexanderParra]

Originally Posted by elcalen

I did a quick test on my end, two tracks with the same audio item, and it sure was looking like the number was staying the same on both tracks, and never going back down in quieter parts, even with the "current" meter. (7.15/Linux)

EDIT: For what it's worth, I have the master track loudness meter also set to LUFS-S/current, and that works as expected. Unlike the track meter readout, the master track readout goes up *and* down.

This is exactly how it behaves for me too. Master track is working fine but tracks aren't. Switching to the default theme and back to my theme doesn't seem to fix it either. (7.15/Win10)

[schwa]

Note that if multiple tracks are selected, changing the meter configuration on one selected track will affect all selected tracks. So if you think this isn't working correctly, check to make sure the track metering is set the way you think it is.

[elcalen]

Originally Posted by schwa

Note that if multiple tracks are selected, changing the meter configuration on one selected track will affect all selected tracks. So if you think this isn't working correctly, check to make sure the track metering is set the way you think it is.

I definitely checked it multiple times.