v6.29+dev0613a - June 13 2021

[musicbynumbers]

v6.29+dev0613 - June 13 2021

• + Mixer: support displaying LRA (loudness range) in master meter
• # Mixer: support combined-channel RMS loudness display

v6.29+dev0613a - June 13 2021

• * Includes feature branch: render normalization
• * Includes feature branch: MIDI editor note reordering
• * Includes feature branch: media item lanes
• * Includes feature branch: EEL2 x86_64/SSE
• * Includes feature branch: VST3 bridging
• # Mixer: fix label display when showing loudness at bottom of master meter

This thread is for pre-release features discussion. Use the Feature Requests forum for other requests.




Changelog - Pre-Releases

Generated by X-Raym's REAPER ChangeLog to BBCode

[musicbynumbers]

Thanks for LRA!

[Coachz]

Originally Posted by musicbynumbers

Thanks for LRA!

Is it LUFS - I?

[Mercado_Negro]

The readout at the bottom of the Master Meter has always been really hard to read. Could you please shrink the meter itself a bit so the readout is alone like the one on top?

[musicbynumbers]

Originally Posted by Mercado_Negro

The readout at the bottom of the Master Meter has always been really hard to read. Could you please shrink the meter itself a bit so the readout is alone like the one on top?

Either that or give both top and bottom meters a solid background behind just the text?

[Phazma]

Originally Posted by musicbynumbers

# Mixer: fix label display when showing loudness at bottom of master meter

I hoped this would fix my inability to see the loudness value but nothing...

Peak Top Peak Bottom Loudness Top Loudness Bottom

[Phazma]

Originally Posted by Mercado_Negro

The readout at the bottom of the Master Meter has always been really hard to read. Could you please shrink the meter itself a bit so the readout is alone like the one on top?

I agree with adding a bit of space below the part of the meter that lights up, so that the value never conflicts with the color of the meters.

Or more ideally let us WALTER the Peak and Loudness values independently from the meter itself so that we can place them wherever it works best for a given theme.

[schwa]

Originally Posted by Phazma

I hoped this would fix my inability to see the loudness value

My guess would be you have a customized theme that sets the alpha value of master.mcp.meter.rmsreadout.color to zero.

[chmaha]

I'm finding that running dry render, say, 5 times in a row gives me 5 different readings. I assume this could be a problem for normalizing as you might think you are hitting -1 dBTP but in fact you are not (or LUFS-I etc).

EDIT: Probably not a REAPER issue. It's my reverb plugin doing something different each time! I would have expected the results to be the same...Weird.

[Phazma]

Originally Posted by schwa

My guess would be you have a customized theme that sets the alpha value of master.mcp.meter.rmsreadout.color to zero.

Your guess was right, thanks for helping me fix it!

However, now that I can try it, wasn't it supposed to

Originally Posted by Edgemeal

+ Master meters: display a single value for LUFS, because it's not a per-channel calculation

Mine shows 2 values (for all loudness settings) and the LUFS-I readout (which I would use) shows both values 3dB higher than the LUFS-I value from the Loudness Meter JS or third party metering plugins on the master.

[nofish]

Originally Posted by Phazma

the LUFS-I readout (which I would use) shows both values 3dB higher than the LUFS-I value from the Loudness Meter JS or third party metering plugins on the master.

Any chance you've set 'Display gain' to 3.0 in the Master VU settings dialog?

[Phazma]

Originally Posted by Mercado_Negro

The readout at the bottom of the Master Meter has always been really hard to read.

Or perhaps the simplest solution would be to either add a second pair of coordinates to master.mcp.meter.rmsreadout.color for when the meters are lit or otherwise add master.mcp.meter.rmsreadout.color.lit to WALTER, which would allow to set a contrasting color for both when the meters are lit and when they are unlit (for example white when unlit and black when lit).

[Phazma]

Originally Posted by nofish

Any chance you've set 'Display gain' to 3.0 in the Master VU settings dialog?

Yes, that was the cause. Now the values show correctly.

Still, I think seeing 2 values is redundant. Is that also an error on my side?

[schwa]

Can you post a screenshot of your master mixer meter settings and the display?

[pepe44]

Guys you need to set the display offset to zero so the integrated values shows correct values.

Here is a printscreen of some minor issues compared to the TB dpMeter5

Peak values -difference of -0.4 dBFS to -07dBFS
The integrated value is quite near, its the approxiamtion due to "capture" time. Its fine.

https://ibb.co/481xvCv

PS: THANKS devs for this metering forgot to mention at first

[Phazma]

Originally Posted by schwa

Can you post a screenshot of your master mixer meter settings and the display?

Here (happens in all themes so I posted with default):

[Phazma]

When putting it at the top it does show just a single value. Is this how it is intended to look?



Is the "L-I" part really necessary? Wouldn't it look simpler like this?

[Mercado_Negro]

Originally Posted by Phazma

When putting it at the top it does show just a single value. Is this how it is intended to look?



Is the "L-I" part really necessary? Wouldn't it look simpler like this?

I like the L-I because we might go switching between different measurements depending on the task and that label tells us what we're using without opening the settings.

[mawi]

Would be nice if I could specify a solid background color with transparency for the RMS value (master.mcp.meter.rmsreadout.color). Currently I can only specify the text color.

[alexgameaudio]

I'm finding that the LUFS-I value doesn't calculate on shorter sounds - the limit seems to be around 2 seconds.

[chmaha]

I know it's being picky but it's annoying that the JSFX loudness meter and the master bus don't agree exactly on integrated value:

[Phazma]

Originally Posted by BethHarmon

I know it's being picky but it's annoying that the JSFX loudness meter and the master bus don't agree exactly on integrated value:

Same is with peak calculation, seems to work slightly different in various parts of Reaper. But I have mentioned that often enough and I don't want to keep being picky about it and annoy the devs (or just schwa?) who are/is doing a great job on the loudness/normalizing/render stuff.

[xpander]

Originally Posted by alexgameaudio

I'm finding that the LUFS-I value doesn't calculate on shorter sounds - the limit seems to be around 2 seconds.

It shouldn't either, integrated LUFS measurement is meant for longer parts/whole songs. Short term LUFS should give the level of last 3 seconds and Momentary LUFS last 400 ms.

[AZpercussion]

I tried to link compressor plugin dry/wet knob with new js loudness meter.
With lufs-s slider as example.
But it seems there's no influence. What i missed?

And there is many utility sliders, it seems. So it difficult to understand by name which are suit for linking.

If all sliders are utility for now, please take a look at use case, when the loudness have influence on other plugins through parameter linking.
It can be more careful, precision and softer than currently modulation by audio signal.

[alexgameaudio]

Originally Posted by xpander

It shouldn't either, integrated LUFS measurement is meant for longer parts/whole songs. Short term LUFS should give the level of last 3 seconds and Momentary LUFS last 400 ms.

I can understand that, but all the plugins I use will provide a value. It's insanely useful, because I'm working with short sounds very often, and the momentary value is is less reliable when comparing different sound effects.

[schwa]

In the latest +dev0614 build, LUFS-I should be displayed after 400ms of audio has been processed, like LUFS-M. LUFS-S will be displayed after 3000ms, and LRA after... a while (3000ms plus at least 2000ms of non-silent material).

[alexgameaudio]

Originally Posted by schwa

In the latest +dev0614 build, LUFS-I should be displayed after 400ms of audio has been processed, like LUFS-M. LUFS-S will be displayed after 3000ms, and LRA after... a while (3000ms plus at least 2000ms of non-silent material).

Thanks!

[Coachz]

In windows 10 with latest +dev0614, how do I turn on the LUFS-I on the TCP Master track ? I don't see it in right click, Project settings or actions. Thanks !

[schwa]

The loudness display is only on the master track in the mixer.

[Coachz]

Originally Posted by schwa

The loudness display is only on the master track in the mixer.

Grrr. I haven't used the mixer since I bought Reaper. TCP is where the rubber meets the road baby. He he. Oh well cheers.

[maralatho]

Originally Posted by Coachz

Grrr. I haven't used the mixer since I bought Reaper. TCP is where the rubber meets the road baby. He he. Oh well cheers.

You could keep the Mixer hidden, and dock the master track to the right edge of the screen.

[Coachz]

Originally Posted by maralatho

You could keep the Mixer hidden, and dock the master track to the right edge of the screen.

Thanks. Right now I'm using the tiny lufs meter fx on the master track in the TCP and that's working pretty good though it would be better if it was integrated into the master track meter. I have no desire to have the master track take up any more space than it currently does so docking it to the right edge is a no-go. I use all of my 28in monitor for track space and very little for TCP controls. Hopefully they will take the mixer lufs meter and add it to the TCP to make life easier. If I get one feature added every 3 years I'm thrilled. They don't really listen to my ideas apparently.

[deeb]

I never open mixer ! TCP is my mixer

[Coachz]

Originally Posted by deeb

I never open mixer ! TCP is my mixer

This guy gets it!

[deeb]

Having a second thought about this actually this differences between TCP and MCP kind make more complexity in terms of user point view and defines limitations to the user which could be avoided.

Cockos! Why not try to make them unified as much as possible! :/

Now different meters between TCP and MCP, we also have FX menu and Sends menu in MCP which does not exist in TCP. Leaving TCP unbalanced. I guess the list continues.

At some point Channels view would work for both and for small and big screens:



Simple please.