v6.37rc3 - September 30 2021

[vitalker]

v6.37rc3 - September 30 2021

• * Includes feature branch: multichannel, multi-mono, multi-stereo ReaPlugs
• * Includes feature branch: ReaLimit and render limiting
• * Includes feature branch: MIDI editor note reordering
• + JSFX: loudness meter integrated values (LUFS-I, LRA, RMS-I) only update when playing back
• + ReaScript: add TakeFX/TrackFX_GetParamIdent/GetParamFromIdent
• + ReaScript: for Lua, make final string parameter to various Get functions that return strings optional
• # FX: put Delta parameter back at end of list -- existing ReaScripts should be updated to use TrackFX_GetParamFromIdent(":wet") etc
• # ReaComp: fix gain reduction meter peak hold display

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

[chmaha]

[*]+ JSFX: loudness meter integrated values (LUFS-I, LRA, RMS-I) only update when playing back

Thanks so much!

EDIT: I still think freezing everything including all the meters is the right approach...The LUFS-S meter slowly dwindling down feels weird and is not the behavior I'd expect from a loudness meter when transport is stopped.

[Funkybot]

Originally Posted by vitalker

# FX: put Delta parameter back at end of list -- existing ReaScripts should be updated to use TrackFX_GetParamFromIdent(":wet") etc

Thanks!

[ashcat_lt]

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.

[chmaha]

Originally Posted by ashcat_lt

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 hear you. I think it can be both. For example, press play then stop and the meters and values freeze but on double-clicking it resets and is ready for measuring things in stop/pause mode. Pressing play again resets...

Already there is a "reset on playback start" option so perhaps the freezing on stop could also be an option so everyone is happy? I agree with you that measuring a live signal during stop/pause is important but I don't consider LRA or LUFS-I part of that calculation. I'd only be concerned with peak or perhaps an average like a VU meter in those circumstances.

[Tod]

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.

[schwa]

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."

[Tod]

Originally Posted by schwa

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."

Thanks for the quick reply schwa.

[heda]

Originally Posted by vitalker

[*]+ ReaScript: add TakeFX/TrackFX_GetParamIdent/GetParamFromIdent

nice. thank you. it's good now.

[Edgemeal]

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?

[ThomasE]

v6.37rc1 - September 27 2021
...
# Delta solo: output is wet signal + inverted dry signal

Perfect!

It's still not possible to route the delta signal to any other channel than 1-2 though.

I also noticed that when using the wet/dry knob, only the wet signal follows if the output is routed to any other channel than 1-2. The same thing seems to happen in older versions as well so this isn't new, but I would guess that this isn't the intended behavior.

[EpicSounds]

having an issue with ReaXcomp moving the threshold handles after resizing the plugin
big gif here https://imgur.com/ryshaFb

[Justin]

Originally Posted by EpicSounds

having an issue with ReaXcomp moving the threshold handles after resizing the plugin
big gif here https://imgur.com/ryshaFb

ah thanks for spotting this, fixing!

[daxliniere]

Anyone else seeing MCP meters flicking for no apparent reason?

Example here:
https://youtu.be/sDlaXxkzmk4

Noticed this since 6.36+dev0924, but could have occurred a little earlier.

[schwa]

Originally Posted by daxliniere

Anyone else seeing MCP meters flicking for no apparent reason?

Did you ever send the project file?

It's not easy to see what's happening in the video, but in general, if a track is not soloed, there is a "not soloed" theme element (meter_unsolo.png) that should display in the track meters. You should see it if you switch to the default theme. Does your theme have that element?

[daxliniere]

Originally Posted by schwa

Did you ever send the project file?

I think so. Coming to you (support@) again via WeTransfer

Originally Posted by schwa

It's not easy to see what's happening in the video, but in general, if a track is not soloed, there is a "not soloed" theme element (meter_unsolo.png) that should display in the track meters. You should see it if you switch to the default theme. Does your theme have that element?

Yes, yellow [S] is solo'd, grey is not solo'd.

Here's a video I shot this morning: https://youtu.be/HA6TiyDs4Ig

[schwa]

Got it, fixing, thanks.

[daxliniere]

Originally Posted by schwa

Got it, fixing, thanks.

JEEEZ, you're quick!

[schwa]

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.

[daxliniere]

Ahh, I see. That's a good find.

P.S. Clipping is a dirty word, floats prefer the name 'overs' XD