Old 06-20-2021, 02:43 PM   #1
mabian
Moderator
 
mabian's Avatar
 
Join Date: Aug 2007
Location: Italy
Posts: 4,150
Default v6.30rc1 - June 20 2021

v6.30rc1 - June 20 2021

(First part)
  • * Includes feature branch: render normalization
  • * Includes feature branch: EEL2 x86_64/SSE
  • * Includes feature branch: VST3 bridging
  • + API: fix deadlock with MIDI_GetAllEvts() and too small of buffer [t=254625]
  • + Actions: add action to calculate loudness of selected items via dry-run render
  • + Actions: add action to calculate loudness of selected tracks via dry run render
  • + Actions: add action to calculate loudness of selected tracks within time selection via dry run render
  • + Automation items: add preference to pool/unpool automation items when split due to media item edit or razor edit
  • + Automation items: filter out duplicate points on load [t=254759]
  • + Automation items: fix hang/slowness when adjusting very large automation items [t=254759]
  • + Batch converter: support normalizing when converting
  • + Consolidate: support wildcards in consolidated file name
  • + Envelopes: fix unexpected behavior when moving multiple sets of envelope points with no transition time between selected and unselected points [t=254611]
  • + JSFX: add help for sliderchange() function
  • + JSFX: add peak/RMS/LUFS loudness meter
  • + JSFX: add slider_show() function, to hide or display sliders
  • + JSFX: calculate "true peak" in loudness meter
  • + JSFX: display true peak clip count in loudness meter
  • + JSFX: fix slider_automate() when hidden sliders exist
  • + JSFX: improve LUFS loudness calculation
  • + JSFX: improve LUFS meter display when embedded
  • + JSFX: support writing output automation of loudness meter
  • + LV2: fix multichannel non-default pin mapping state on project load [t=254704]
  • + MIDI editor: fix editing event properties from list editor with filter applied [t=254671]
  • + Master VU: apply loudness display gain but not display offset to loudness readout numbers
  • + Master VU: display LUFS loudness values before they are fully seasoned
  • + Master VU: if theme does not define meter_bg_mcp_master or meter_bg_mcp image, fill loudness readout area with "VU (indicator) - no signal" theme color
  • + Master VU: support oversampled peak display ("true peaks")
  • + Master meters: display a single value for LUFS, because it's not a per-channel calculation
  • + Master track: don't show master mixer metering options when right-clicking TCP master
  • + Master track: support LUFS-M metering
  • + Master track: support displaying LUFS-I in mixer (loudness meter will display LUFS-M, but displayed number will be LUFS-I)
  • + Master track: support loudness metering in TCP
  • + Meters: more informative tooltips
  • + Mixer: add option to display LUFS-S current rather than max value
  • + Mixer: support displaying LRA (loudness range) in master meter
  • + Project bay: improve drag-drop preview and cursor behavior
  • + Project bay: improve handling of MIDI items and tempo changes (existing retained items will have to be re-retained to include QN information) [t=243315]
  • + ReaScript: GetSetProjectInfoString(project, "RENDER_METADATA", "", false) will return a list of all defined project metadata identifiers [t=254407]
  • + ReaScript: add GetEnvelopeInfo_Value(I_SEND_IDX) etc
  • + ReaScript: add GetEnvelopeInfo_Value(P_DESTTRACK) for send envelopes
  • + ReaScript: add GetSetProjectInfo_String("RENDER_STATS"), to retrieve statistics for the most recently rendered files
  • + ReaScript: support getting/setting render normalization mode and target
  • + ReaScript: support running a caller-specified action before returning render statistics (see API help for details)
  • + Render queue: add button to cancel all remaining renders [t=234691]
  • + Render: add actions to calculate loudness of master mix via dry run render
  • + Render: add info button to render statistics display
  • + Render: add options to normalize render to target peak or RMS
  • + Render: add preference to calculate true peak on render when not normalizing to it
  • + Render: apply dither/noise shaping to secondary render format if enabled and format supports
  • + Render: disable audio normalizing for video renders
  • + Render: display LRA (loudness range) after render
  • + Render: display LUFS, support normalizing to target LUFS
  • + Render: display peak, RMS, overs even if not normalizing
  • + Render: display peak, rms, and overs when normalizing
  • + Render: display statistics for all rendered files
  • + Render: draw peaks on first pass of 2nd pass render
  • + Render: ignore preference to auto-close render dialog if normalizing or dummy rendering
  • + Render: improve render speed when normalizing
  • + Render: optionally mark overs (samples over +0dbFS, potential digital clipping) in render peaks display
  • + Render: support dry run rendering (everything is processed as normal, but no output files are written)
  • + Render: support normalizing stems to master mix
  • + Render: support normalizing to LUFS-M max or LUFS-S max
  • + Render: support optional LUFS handling of LFE and surround channels when normalizing
  • + Theme: support separate loudness readout colors for unlit and lit background in WALTER [p=2454121]
  • + Tracks: prevent tiny (<0.1%) volume change on initial track fader click [t=191454]
  • + VST3: add IPlugInterfaceSupport, for plugins to request compatibility features
  • + VST3: add support for IMidiLearn interface
  • + VST3: avoid threading conflicts when processing expression and keyswitch information
  • + VST3: internal threading changes to MIDI controller and program change handling
  • + Video: option to choose which monitor is used for fullscreen display
  • # Actions: action to calculate loudness of selected tracks will calculate master mix loudness if the master track is the only track selected
  • # Automation items: entirely un-pool automation items when editing with preference enabled [p=2446337]
  • # Batch converter: fix button positioning when window is resized
  • # Convert: fix normalization for source files that do not have an embedded source start time [p=2450739]
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
__________________
Instagram: @mabian_art - Twitter:: @MabianArt
Music: https://www.reverbnation.com/errepici - https://www.facebook.com/errepici
mabian is offline   Reply With Quote
Old 06-20-2021, 02:45 PM   #2
mabian
Moderator
 
mabian's Avatar
 
Join Date: Aug 2007
Location: Italy
Posts: 4,150
Default

v6.30rc1 - June 20 2021

(Second part)
  • # JSFX loudness meter: expose current LUFS-M/I/S and LRA values as parameters for script accessibility/etc
  • # JSFX loudness meter: expose true peak and RMS readings as parameters
  • # JSFX: add LUFS-M histogram support
  • # JSFX: add alert settings to loudness meter
  • # JSFX: add loudness range calculation to loudness meter
  • # JSFX: add option to loudness meter to reset data on playback start
  • # JSFX: add separate momentary RMS measurement to loudness meter
  • # JSFX: add short-term LUFS to loudness meter
  • # JSFX: don't display partially-calculated LUFS
  • # JSFX: fix auto-reset of loudness meter when not processing FX when stopped
  • # JSFX: fix hidden sliders altering FX parameter count [p=2451177]
  • # JSFX: fix initial layout of loudness meter when not processing FX on stop
  • # JSFX: fix loudness peak meter channel order
  • # JSFX: fix reversed LUFS-M current and maximum value display
  • # JSFX: improve LUFS meter scaling
  • # JSFX: improve loudness meter layout at small sizes, hide RMS by default
  • # JSFX: loudness meter is LUFS-multichannel-aware
  • # JSFX: optimize loudness meter CPU use when not displaying true peak
  • # JSFX: support customizable colors in loudness meter
  • # Master VU: attempt to be clearer about what loudness is being displayed in the meter and readout number
  • # Master VU: ensure that muted/automuted text covers the entire meter area
  • # Master VU: fix loudness readout offset on retina/hidpi displays
  • # Master VU: fix tooltip for certain preference combinations
  • # Master VU: increase loudness meter update rate
  • # Master VU: indicate in TCP master when displaying true peaks
  • # Master VU: smooth loudness meters slightly
  • # Master track: support LUFS-S metering in mixer
  • # Mixer: draw master loudness readout below meters
  • # Mixer: fix label display when showing loudness at bottom of master meter
  • # Mixer: support UTF-8 translations in master meter settings dialog
  • # Mixer: support combined-channel RMS loudness display
  • # ReaScript: automatically close render window when calling RENDER_STATS with a render action
  • # ReaScript: slightly change the output of GetSetProjectInfo_String("RENDER_STATS") for consistency and futureproofing
  • # Render: add separate button for dry run render
  • # Render: change to internal storage for render normalization (project normalization settings saved in +dev0520 may load differently)
  • # Render: display render meters post-normalization
  • # Render: display render meters post-normalization for greater-than-mono tracks
  • # Render: don't calculate true peak for meters during render (saves CPU)
  • # Render: don't display "show in explorer" or "launch file" buttons after dry run render
  • # Render: fail silently if attempting dry run render of selected tracks with no tracks selected or other obvious failure modes
  • # Render: fix 1-pixel peaks drawing error
  • # Render: fix LUFS calculation
  • # Render: fix dummy render of multichannel files
  • # Render: fix embedding bwf position when normalizing
  • # Render: fix incorrect rounding of near-silence [p=2453577]
  • # Render: fix multichannel peaks/overs drawing
  • # Render: fix normalizing selected media items or multiple time regions per track
  • # Render: fix peaks drawing with multichannel renders
  • # Render: fix saving normalization settings to render presets
  • # Render: fix up peaks drawing
  • # Render: if normalization would require adding more than 60dB, don't normalize
  • # Render: improve LUFS loudness calculation
  • # Render: potentially improve precision of normalization slightly
  • # Render: support normalizing to digital peak or true peak
  • # Render: use fixed 400ms window for RMS normalization
  • # Render: use project name as (unused but displayed) target file name when dry run rendering master mix
  • # Rendering: fix denormal issues with silence [p=2450456]
  • # Theme: preserve appearance of themes that use fixed-height master vu meter images
  • # VST3: require ModuleEntry on linux
  • # jsfx loudness meter: make LUFS dB display rounding match that of master meter [p=2454211]
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
__________________
Instagram: @mabian_art - Twitter:: @MabianArt
Music: https://www.reverbnation.com/errepici - https://www.facebook.com/errepici
mabian is offline   Reply With Quote
Old 06-20-2021, 03:08 PM   #3
Phazma
Human being with feelings
 
Join Date: Jun 2019
Posts: 1,515
Default

Wonderful release incoming Thanks devs!
Phazma is online now   Reply With Quote
Old 06-20-2021, 03:34 PM   #4
BethHarmon
Human being with feelings
 
BethHarmon's Avatar
 
Join Date: Feb 2021
Location: https://github.com/ElizabethHarmon
Posts: 162
Default

This is absolutely amazing work!
BethHarmon is online now   Reply With Quote
Old 06-20-2021, 04:44 PM   #5
ovnis
Human being with feelings
 
ovnis's Avatar
 
Join Date: Oct 2011
Posts: 2,062
Default

great work
ovnis is offline   Reply With Quote
Old 06-20-2021, 05:00 PM   #6
akademie
Human being with feelings
 
Join Date: Mar 2007
Posts: 2,472
Default

Quote:
Originally Posted by mabian View Post
v6.30rc1 - June 20 2021
  • + Project bay: improve handling of MIDI items and tempo changes (existing retained items will have to be re-retained to include QN information) [t=243315]
Thanks the reported bug seems to be fixed, but another (not new) bug is revealed - more in new Bug report thread:
"Project Bay bug - items added to timeline registration bug"

Last edited by akademie; 06-21-2021 at 06:40 PM. Reason: changed link to new bug report
akademie is offline   Reply With Quote
Old 06-20-2021, 08:04 PM   #7
Delucci
Human being with feelings
 
Join Date: May 2017
Posts: 289
Default

Why midi note reorder isn't in this RC yet?
Delucci is online now   Reply With Quote
Old 06-20-2021, 08:33 PM   #8
kytdkut
Human being with feelings
 
Join Date: May 2017
Posts: 67
Default Mono metering

hello devs,

could you add a way to measure LUFS of mono media in JSFX and/or master meter?

for this I rely on disabling a pin on every LUFS meter or on substracting 3 db before metering and adding them back later...

game audio folks would be very pleased

also thanks for this fantastic round of updates

edit:
if "stop playback at end of loop if repeat is disabled" is enabled, LUFS readout in JSFX loudness meter blanks when automatically stopping i.e. reached the end of the time selection
the readout does not disappear when stopping via action or pressing spacebar
it is not possible to measure LUFS of selected region if the meter behaves like this

Last edited by kytdkut; 06-20-2021 at 10:17 PM.
kytdkut is online now   Reply With Quote
Old 06-21-2021, 12:27 AM   #9
Phazma
Human being with feelings
 
Join Date: Jun 2019
Posts: 1,515
Default Render queue: Normalize to master target

Btw devs, I know this comes a bit late now... but would it be possible to allow normalizing renders from the queue to a master target level, similar to how it works for stems?

Reason: Instead of doing a traditional stem render of all tracks individually I often find myself creating stems from combinations of multiple tracks and AFAIK the easiest/safest way to do this is by soloing the tracks needed on a stem and adding that combination as a 'Master mix' render to the queue.

If this feature was added it would allow flexible stem creation via render queue while being able to normalize and keep the proportions between the tracks.

I can imagine this to work by first rendering the master mix to calculate the gain adjustment and then go through the render queue with the gain adjustment already applied.
Phazma is online now   Reply With Quote
Old 06-21-2021, 02:20 AM   #10
luiza177
Human being with feelings
 
Join Date: Mar 2020
Posts: 23
Default

Quote:
Originally Posted by Delucci View Post
Why midi note reorder isn't in this RC yet?
I'm also curious about this. I couldn't get it to work in earlier builds as well.
luiza177 is offline   Reply With Quote
Old 06-21-2021, 03:30 AM   #11
benf
Human being with feelings
 
benf's Avatar
 
Join Date: Oct 2008
Location: France
Posts: 3,286
Default

Quote:
Originally Posted by Delucci View Post
Why midi note reorder isn't in this RC yet?
I suppose that's because they got to improve it yet.
__________________
Ecouter et télécharger ma musique sur : https://benest.bandcamp.com/
benf is offline   Reply With Quote
Old 06-21-2021, 05:51 AM   #12
Thunderfinger
Human being with feelings
 
Join Date: Jun 2020
Posts: 25
Default

Thanks on the amazing work on this update!

There is still only one thing that is sub-optimal for me. In the JS loudness meter and in the master track meter, the LUFS numbers are tiny, almost unreadable. Could there be a way to have a mode that gets rid of the visual meters that takes all of the screen real estate, and only shows big easily readable numbers?

I work on dialog post all day every day, and all I need to know is the exact LUFS-I level i'm at at every single moment. I'm looking at that number almost at all times, and I don't need the visual moving "bands" (and I would bet everyone working in dialog post is in the same boat). I love how you implemented loudness as a JS and in the master meter, but unfortunately, as it is, i'll have to keep using a 3rd party plugin. Reading those tiny numbers all day would certainly give me headaches from the squinting.
Thunderfinger is offline   Reply With Quote
Old 06-21-2021, 06:29 AM   #13
BethHarmon
Human being with feelings
 
BethHarmon's Avatar
 
Join Date: Feb 2021
Location: https://github.com/ElizabethHarmon
Posts: 162
Default

Quote:
Originally Posted by Thunderfinger View Post
Could there be a way to have a mode that gets rid of the visual meters that takes all of the screen real estate, and only shows big easily readable numbers?
+1 on a "big numbers" version of the JSFX loudness meter in particular. As nice as the meters are, the only thing I care about at the end of the day are the numbers.
BethHarmon is online now   Reply With Quote
Old 06-21-2021, 06:55 AM   #14
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 11,992
Default

Quote:
Originally Posted by kytdkut View Post
h
if "stop playback at end of loop if repeat is disabled" is enabled, LUFS readout in JSFX loudness meter blanks when automatically stopping i.e. reached the end of the time selection
It's not a great fix for this, but it will not reset if you change the loudness meter setting to not reset on playback start. You can also use the action to calculate loudness of selected tracks within the time selection.

Last edited by schwa; 06-21-2021 at 07:12 AM.
schwa is offline   Reply With Quote
Old 06-21-2021, 07:40 AM   #15
Thunderfinger
Human being with feelings
 
Join Date: Jun 2020
Posts: 25
Default

Quote:
Originally Posted by kytdkut View Post
could you add a way to measure LUFS of mono media in JSFX and/or master meter?

for this I rely on disabling a pin on every LUFS meter or on substracting 3 db before metering and adding them back later...
+1 for mono mode, I also have to disable a pin on every LUFS meter and it does add a risk, especially when working with less experienced engineers.
Thunderfinger is offline   Reply With Quote
Old 06-21-2021, 07:42 AM   #16
bolgwrad
Human being with feelings
 
bolgwrad's Avatar
 
Join Date: Mar 2011
Location: On my arse in Glasgow, Scotland
Posts: 879
Default

Quote:
Originally Posted by Thunderfinger View Post
Thanks on the amazing work on this update!

There is still only one thing that is sub-optimal for me. In the JS loudness meter and in the master track meter, the LUFS numbers are tiny, almost unreadable. Could there be a way to have a mode that gets rid of the visual meters that takes all of the screen real estate, and only shows big easily readable numbers?
.
I'm the opposite. Every update of the Loudness Meter I have to edit the font size from 11 to 8, or the numbers overlap in the MCP. This is no doubt the fault of my default theme font, but I wonder if increasing from 11 would help you.

Edit: overlap not happening in rc01, thanks. It's a stoater!
__________________
www.sachetsofrelish.com

Last edited by bolgwrad; 06-21-2021 at 09:29 AM.
bolgwrad is offline   Reply With Quote
Old 06-21-2021, 08:24 AM   #17
Meo-Ada Mespotine
Human being with feelings
 
Meo-Ada Mespotine's Avatar
 
Join Date: Apr 2020
Location: Leipzig
Posts: 2,632
Default

I just noticed, that the docs for GetMediaItemInfo_Value and SetMediaItemInfo_Value miss the information for lock to active take:

C_LOCK : char * : locked, &1=locked, &2=lock to active take
__________________
Use you/she/her.Ultraschall-Api Lua Api4Reaper
Off for some time. Bugreports&Docs notes please do here:https://github.com/Ultraschall/ultra...-reaper/issues - Donate, if you wish
Meo-Ada Mespotine is offline   Reply With Quote
Old 06-21-2021, 08:30 AM   #18
Zeno
Human being with feelings
 
Zeno's Avatar
 
Join Date: Sep 2018
Location: HH
Posts: 512
Default

Quote:
Originally Posted by mabian View Post
Project bay: improve handling of MIDI items and tempo changes (existing retained items will have to be re-retained to include QN information) [t=243315]
Thank you!
Zeno is offline   Reply With Quote
Old 06-21-2021, 08:42 AM   #19
Thunderfinger
Human being with feelings
 
Join Date: Jun 2020
Posts: 25
Default

Quote:
Originally Posted by bolgwrad View Post
I'm the opposite. Every update of the Loudness Meter I have to edit the font size from 11 to 8, or the numbers overlap in the MCP. This is no doubt the fault of my default theme font, but I wonder if increasing from 11 would help you.
Thanks for the tip, Increasing the font dramatically and resizing the window allowed me to make it much better for me. I would still love to have this function natively without having to mess with the script.

Thunderfinger is offline   Reply With Quote
Old 06-21-2021, 10:28 AM   #20
AZpercussion
Human being with feelings
 
Join Date: Oct 2019
Location: Moscow, Russia
Posts: 290
Default

Awesome update!!!
Thanks!

And thanks for linking enable.

My big +1 to others about big font for loudness meter.
By the way there's space for bigger numbers in master too.

Trying to change font manually produce mess with overlapping elements.
AZpercussion is offline   Reply With Quote
Old 06-21-2021, 11:39 AM   #21
Paul Eye
Human being with feelings
 
Join Date: Feb 2006
Location: Helsinki, Finland
Posts: 133
Default

Quote:
Originally Posted by kytdkut View Post
if "stop playback at end of loop if repeat is disabled" is enabled, LUFS readout in JSFX loudness meter blanks when automatically stopping i.e. reached the end of the time selection
the readout does not disappear when stopping via action or pressing spacebar
it is not possible to measure LUFS of selected region if the meter behaves like this
Quote:
Originally Posted by schwa View Post
It's not a great fix for this, but it will not reset if you change the loudness meter setting to not reset on playback start. You can also use the action to calculate loudness of selected tracks within the time selection.
That's odd, this doesn't happen over here. The meter keeps running (registering delay/reverb tails for example) after playback auto stops at the end of a loop. I have the loudness meter JS as my only monitoring FX and I have my settings saved into an active (and default) preset, if that makes any difference.
Edit: "Flush FX when looping" is off, "Run FX when stopped" is on, "Flush FX on stop" is off.

Last edited by Paul Eye; 06-21-2021 at 12:01 PM.
Paul Eye is offline   Reply With Quote
Old 06-22-2021, 06:07 AM   #22
Edgemeal
Human being with feelings
 
Edgemeal's Avatar
 
Join Date: Apr 2016
Location: ASU`ogacihC
Posts: 2,554
Default

Quote:
+ Master track: don't show master mixer metering options when right-clicking TCP master
FWIW, the "Master VU Setting" dialog window now opens (tested on RC2) on right clicking TCP Master meter regardless if Mixer is open or not, but probably a good idea.
Edgemeal is online now   Reply With Quote
Old 06-26-2021, 01:50 PM   #23
mawi
Human being with feelings
 
Join Date: Apr 2011
Posts: 846
Default

Quote:
Theme: support separate loudness readout colors for unlit and lit background in WALTER [p=2454121]
How does this WALTER work?
__________________
"If this is a 4:1 ratio, then I am a cheese toastie." Dan Worrall
mawi is offline   Reply With Quote
Old 06-26-2021, 01:58 PM   #24
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 11,992
Default

Quote:
Originally Posted by mawi View Post
How does this WALTER work?
That change got reverted because we settled on this instead:

- Mixer: draw master loudness readout below meters
schwa is offline   Reply With Quote
Old 06-26-2021, 02:13 PM   #25
mawi
Human being with feelings
 
Join Date: Apr 2011
Posts: 846
Default

Quote:
Originally Posted by schwa View Post
That change got reverted because we settled on this instead:

- Mixer: draw master loudness readout below meters
Ok, thanks!
__________________
"If this is a 4:1 ratio, then I am a cheese toastie." Dan Worrall
mawi is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 01:29 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, vBulletin Solutions Inc.