v6.37rc3 - September 30 2021

Not that it super matters to me, but I think at least some of the usefulness of a loudness meter is removed when it can't measure things in stop/pause mode. IF one was trying to use it to set input levels for external sources or perhaps the levels coming out of a VSTi, they would have to run the transport to do so, which is...maybe not ideal in many cases. I personally expect this kind of meter to fade down when it has no input because that's how math works. Everything else I have that tries to do this kind of thing in real time does so. It's maybe not super convenient, but we've got so many other ways to get those numbers and display them in a more permanent form. Maybe this just isn't the tool for that particular job. Integrated readings tend to depend on the exact period over which they are measured. I know LUFS gates out some of the lowest levels, but it still doesn't make much sense (to me) to try to look at it in real time. All that matters is how it integrates over the full length of the thing, so selecting that time and using one of the offline processes to analyze is (in my mind) the only right way to do it.

I just upgraded to todays version and was trying to use the "take system", but instead of getting 3 takes in a single file, I ended up with 3 separate takes. Also they aren't even lined up where I played them. I know it has to do with some new things associated putting items on the same track, but how do I turn it off??:( I know this can be a good thing, but I think it's going to require some special actions to deal with it. But for now I just want to turn it off. :)

The new item lanes features are not in this build or any release candidate or released version. In any case, the takes/items behavior is controlled by the preferences in the options menu, under "new recording that overlaps existing items."

ReaLimit Bug 

ReaLimit is not remembering the Release setting in saved project. I have two instances of it in a project (one at 60, other at 80 on dirfferent tracks), when I reload project both instances are set back to the default of 15. Win10_x64 EDIT It doesn't remember the zoom amount either, but maybe that is intended?

having an issue with ReaXcomp moving the threshold handles after resizing the plugin big gif here

Anyone else seeing MCP meters flicking for no apparent reason? Example here: Noticed this since 6.36+dev0924, but could have occurred a little earlier.

Got it, fixing, thanks.

Thanks for catching it. Part of the bug is actually not new, not-soloed tracks that clip (as in your project) would always show clip indicators. Also notice that if you clear the solo state after playing back, the previously muted tracks that clipped will show clip indicators.