v6.31rc1 - July 5 2021

Edgemeal · 07-06-2021, 05:55 AM

v6.31rc1 - July 5 2021
+ JSFX: comment out slider_automate for the JSFX loudness meter output parameters, because it can cause those parameters to always be the last touched FX parameter [p=2460020]
+ Master VU: don't show clip indicator in TCP meter when set to loudness, even if peaks clip
+ Normalization: use 64-bit intermediate file when rendering to normalized 32-bit PCM
+ ReaScript: fix SetEnvelopePointEx when used with automation items [p=2459830]
+ ReaTune: improve readout text on Windows [p=2459803]
+ Render: always run dry-run render actions at full speed regardless of other render preferences [p=2459647]
+ Render: fix embedding project markers/regions as cues [t=255268]
+ Render: make it extra super duper clear that no output file is created during dry run render
+ VST3: fix bridged UI support for some plug-ins [p=2459517]
+ VST3: fix issues that could cause stale reaper_host processes to stick around after removing plug-ins
# VST3: fix possible bridging over-release of objects [p=2459810]
# VST3: re-fix possible bridging over-release of objects [p=2459810]

Full changelog / Latest pre-releases

Travesty · 07-06-2021, 06:50 AM

+ Render: fix embedding project markers/regions as cues [t=255268]

Fixed, thanks

MrTsonts · 07-06-2021, 07:25 AM

+ JSFX: comment out slider_automate for the JSFX loudness meter output parameters, because it can cause those parameters to always be the last touched FX parameter [p=2460020]

Thank you, fixed.

EpicSounds · 07-06-2021, 08:33 AM

" + Render: make it extra super duper clear that no output file is created during dry run render"

hahahaha

Phazma · 07-06-2021, 08:59 AM

Quote:

Originally Posted by Jae.Thomas

+ Render: display overall render progress indicator

Why is this not included? I really liked it! Does it need further testing? Hope it will be back in the next dev version...

blumpy · 07-06-2021, 09:37 AM

Please make the render window resizable. When rendering stems you only see the first few tracks.

Meo-Ada Mespotine · 07-06-2021, 10:29 AM

Quote:

Originally Posted by blumpy

Please make the render window resizable. When rendering stems you only see the first few tracks.

Scrollable is better. No monitor on earth would show hundreds of stems no matter how much you resize the window.
Important for orchestral projects.

Phazma · 07-06-2021, 10:35 AM

Quote:

Originally Posted by Meo-Ada Mespotine

Scrollable is better. No monitor on earth would show hundreds of stems no matter how much you resize the window.
Important for orchestral projects.

How about both?

Resizing would be great to either make it bigger to see the waveform more precisely (and the full file name) or make it smaller to use less screen real estate when doing other things while rendering and the window is just in the way.

Also a combination of resizing and scrolling could make it possible to first resize to see as many tracks as possible simultaneously and then scroll up and down if needed.

blumpy · 07-06-2021, 10:43 AM

Both would be great. I’m running multiple 4k monitor at 1:1…more information on the screen is better.

Coachz · 07-06-2021, 11:16 AM

Was this removed for this latest version ? I don't see it when I render.
+ Render: display overall render progress indicator

v6.30+dev0704 - July 4 2021
+ Render: display overall render progress indicator

schwa · 07-06-2021, 11:29 AM

This is an RC that is mostly quick fixes. All of the other features will be back for the next +dev cycle.

Phazma · 07-06-2021, 11:41 AM

Quote:

Originally Posted by schwa

This is an RC that is mostly quick fixes. All of the other features will be back for the next +dev cycle.

Happy to hear this! Thanks for the info

mschnell · 07-06-2021, 12:08 PM

Quote:

Originally Posted by EpicSounds

" + Render: make it extra super duper clear that no output file is created during dry run render"

hahahaha

For certain usera this should be the only option allowed

EpicSounds · 07-06-2021, 01:14 PM

Quote:

Originally Posted by Phazma

Why is this not included? I really liked it! Does it need further testing? Hope it will be back in the next dev version...

is it not this?

Phazma · 07-06-2021, 01:29 PM

Quote:

Originally Posted by EpicSounds

is it not this?

No, it is the green progress bar:

EpicSounds · 07-06-2021, 01:39 PM

thanks. I didn't see that before.

I'm still wishing for an audible alert when finished.

Juca · 07-06-2021, 03:33 PM

Why not name the button "Render Preview" or "Render Test" instead of "Dry Run"?
I believe it's much more coherent and self-explanatory.
Greetings.

X-Raym · 07-06-2021, 04:14 PM

Quote:

+ JSFX: comment out slider_automate

No more automation for this in the future ?
I would imagine this could have open some things, like building graph based on the envelope. (just an idea, in the contrary, Heda loudness graph use regular check of plugin parameter value to not spam the project with envelope points).
(anyway, DPMeterFree still has loudness value automation in the worst case)

schwa · 07-06-2021, 04:37 PM

You can uncomment the slider_automate line. We'll add a parameter to control this, so you can switch loudness output automation on or off.

BlackScreen · 07-07-2021, 02:32 AM

A quick follow up to my post from 6.30rc8 where I checked the loudness measurements of REAPER with the EBU test files:

I have checked the failed tests with the release version of 6.31 and found the following:

3341-6 - failed (surround files) - just for the record
3341-13 (2-5) - failed (file-based, I know, but not in tolerance)
3341-13 (7-10) - failed (file-based, I know, but not in tolerance)
3341-13 (12-15) - failed (file-based, I know, but not in tolerance)
3341-13 (17-20) - failed (file-based, I know, but not in tolerance)
3341-14 - failed (Max M value not in tolerance)

Max M and Max S tests with JSFX-plugin
I-tests with dry run render

The rest of the tests, that failed last time, passed this time. So, very good job!

Maybe we could fix the rest of them too?
And also: Maybe we could add the Max M and Max S values to the dry run? Would be really awesome and helpful.

Coachz · 07-07-2021, 03:36 AM

Quote:

Originally Posted by schwa

This is an RC that is mostly quick fixes. All of the other features will be back for the next +dev cycle.

Thanks. I love the progress bar in BOTH render and freeze dialogs. Can the LUFS meter on TCP master track be set pre-fader?

schwa · 07-07-2021, 05:17 AM

Quote:

Originally Posted by BlackScreen

3341-6 - failed (surround files) - just for the record

That's a 5.0 file. REAPER track channels are always even numbers of channels, so there's no way for REAPER to know the difference between 4.1, 5.0, or 5.1, and the EBU loudness spec is different for each of those file types (LFE is ignored, which I disagree with, but that's what the spec says). The user would have to specify what the channel layout is. So, this is a live-with-it, I think.

Quote:

Originally Posted by BlackScreen

3341-13 (2-5) - failed (file-based, I know, but not in tolerance)
3341-13 (7-10) - failed (file-based, I know, but not in tolerance)
3341-13 (12-15) - failed (file-based, I know, but not in tolerance)
3341-13 (17-20) - failed (file-based, I know, but not in tolerance)
3341-14 - failed (Max M value not in tolerance)

These tests assume a meter update rate of 20ms or faster. The EBU spec does not specify an update rate for LUFS-M. The JSFX meter updates at 100ms. At a 20ms update rate, these tests pass. We can add an internal parameter to the JSFX to change the update rate.

BlackScreen · 07-07-2021, 05:21 AM

Quote:

Originally Posted by schwa

These tests assume a meter update rate of 20ms or faster. The EBU spec does not specify an update rate for LUFS-M. The JSFX meter updates at 100ms. At a 20ms update rate, these tests pass. We can add an internal parameter to the JSFX to change the update rate.

Thanks for the infos. I can live with the surround file problem.
And sure, adding it would be great. Also I would love to customize the loudness meter from JSFX in the TCP (horizontal bars or only integrated value or something like that). Maybe this would also be an option.
So far: Thanks for this great add-on and the continuing support and awesomeness of REAPER!

nofish · 07-07-2021, 05:47 AM

Quote:

Originally Posted by schwa

These tests assume a meter update rate of 20ms or faster. The EBU spec does not specify an update rate for LUFS-M. The JSFX meter updates at 100ms. At a 20ms update rate, these tests pass. We can add an internal parameter to the JSFX to change the update rate.

Will/could this parameter be user settable?
As I assume update rate 100 ms -> 20 ms -> ~5x more CPU and I'd consider these test files a 'corner case'?
(SWS uses an optional high precision mode that these pass.)

schwa · 07-07-2021, 06:36 AM

Those particular tests are an intentionally contrived corner case. For the next build the JSFX will have an internal parameter to change the update rate, you'll be able to edit the JSFX if you want to change it. There are already internal parameters to adjust the colors and ballistics.

nofish · 07-07-2021, 06:43 AM

Got it, nice, thanks.

sonicowl · 07-07-2021, 11:34 AM

+ Render: make it extra super duper clear that no output file is created during dry run render

After running a dry run to check levels, I always wish there was a button to do a final render.

Now I run dry render, and say I'm happy with it, but have to close that window and make a render again. And I'm never really sure if settings remain the same, is normalize set the same for final render...

It would be really handy to have button to commit to a final render from within dry render window.