v6.32rc1 - July 8 2021

Edgemeal · 07-08-2021, 10:59 AM

v6.32rc1 - July 8 2021
+ Batch converter: inform FX if channel count is higher than 4 [t=255033]
+ Envelopes: fix FX automation envelope defaults when moving media items [t=253431]
+ JSFX: add a parameter to control whether the JSFX loudness meter outputs loudness values as automation
+ JSFX: add internal meter update rate parameter to loudness meter
+ JSFX: fix stereo super8 export issues [t=255367]
+ Master VU: when master is set to mono, display identical RMS stereo loudness on the right meter channel [p=2460681]
+ Render: disregard setting to save copy of project before rendering when dry-run rendering
+ Wildcards: improve help for $marker(name) and $region(name) wildcards
+ Windows: fix VST3 loading from paths with UTF-8 characters (6.30 regression) [p=2461031]
# Render: make sure the correct sample rate is used for dry run render actions

Full changelog / Latest pre-releases

airon · 07-08-2021, 11:17 AM

Quote:

+ Envelopes: fix FX automation envelope defaults when moving media items [t=253431]

This appears to fix that issue nicely. The pesky, well hidden, multi-year bug has been put to rest. This greatly boosts my confidence in Reapers automation system.

Thank you very much.

javiramallo · 07-08-2021, 11:30 AM

Quote:

Originally Posted by Edgemeal

v6.32rc1 - July 8 2021

+ Windows: fix VST3 loading from paths with UTF-8 characters (6.30 regression) [p=2461031]

This fix seems to work well.
Now is possible to open again previous sessions.

Really thanks Justin and co.

Vadium · 07-08-2021, 01:10 PM

Hi devs,

There is the same issue in this version, as in 6.31: It takes 1min 48sec to open Vienna Ensemble Pro VST3 Instrument (last version for macOS, intel), also CC messages (CC1, for example) are not transmitted to Vepro slave computer. Rolled back to 6.29. In 6.29 it takes 1 sec to open Vepro and all works ok.

BartR · 07-08-2021, 02:17 PM

Great!

May I suggest to change the name "Dry Rendering" with something more intuitive?
Many thought it was a rendering without FX chain.

Vadium · 07-08-2021, 02:40 PM

Quote:

Originally Posted by BartR

Great!

May I suggest to change the name "Dry Rendering" with something more intuitive?
Many thought it was a rendering without FX chain.

+1

idle rendering?
rehearsal rendering?

Justin · 07-08-2021, 02:40 PM

Quote:

Originally Posted by Vadium

Hi devs,

There is the same issue in this version, as in 6.31: It takes 1min 48sec to open Vienna Ensemble Pro VST3 Instrument (last version for macOS, intel), also CC messages (CC1, for example) are not transmitted to Vepro slave computer. Rolled back to 6.29. In 6.29 it takes 1 sec to open Vepro and all works ok.

Is it running bridged, by chance?

Vadium · 07-08-2021, 03:02 PM

Quote:

Originally Posted by Justin

Is it running bridged, by chance?

how can I check it? (an option "Run as dedicated process" selected) and "Automatic bridging" selected in the Preferences
As I know, VePro Vst3 v7.0.1056 is 64bit (as it presents in a white list of plug-ins in Cubase 11), VST 3.6.14 SDK

Justin · 07-08-2021, 03:13 PM

Quote:

Originally Posted by Vadium

how can I check it? (an option "Run as dedicated process" selected) and "Automatic bridging" selected in the Preferences
As I know, VePro Vst3 is 64bit

You should have it set as "Default" not "run as dedicated process"

bolgwrad · 07-08-2021, 03:23 PM

Quote:

Originally Posted by Vadium

+1

idle rendering?
rehearsal rendering?

Actually, 'No output' is a bit ambiguous. How about, 'Test Run (no file)'?

Vadium · 07-08-2021, 03:38 PM

Quote:

Originally Posted by Justin

You should have it set as "Default" not "run as dedicated process"

Hm, it helps! thanks a lot!

Juca · 07-08-2021, 05:51 PM

Quote:

Originally Posted by BartR

Great!

May I suggest to change the name "Dry Rendering" with something more intuitive?
Many thought it was a rendering without FX chain.

I had suggested switching to "Rendering Preview".
I believe it's much more self-explanatory than "Dry Rendering"....
Greetings.

Zeno · 07-09-2021, 03:59 AM

Ok, it's not 100% related to the pre-release (it's not even a new behavior), but....

The approach described in the following post could lead to significant misinterpretation of the displayed meter values:

https://forum.cockos.com/showpost.ph...9&postcount=15

When Multichannel Peakmetering is turned off, only peak for channel 1/2 is displayed, but all channels are included in the loudness calculations. I know "Peak!" is not loudness, but wouldn't it make more sense to also apply the loudness calculations only to 1/2 when multichannel metering is off?

Meo-Ada Mespotine · 07-09-2021, 06:37 AM

Geez, haven't even finished 6.30 docs yet

Quote:

+ Batch converter: inform FX if channel count is higher than 4 [t=255033]

Does this affect settings directly like batch-converter settings for command line or is it more an internal thing?

Ideosound · 07-09-2021, 06:49 AM

Would it be possible to get the font style used to show the new LUFS info on the render window, to match the rest of the font style? No need to have a different font. Would look and feel cleaner if it matched the 'output file' font etc.

Funkybot · 07-09-2021, 06:56 AM

Quote:

Originally Posted by Ideosound

Would it be possible to get the font style used to show the new LUFS info on the render window, to match the rest of the font style? No need to have a different font. Would look and feel cleaner if it matched the 'output file' font etc.

I suspect the font choice has to do with keeping the columns aligned when rendering multiple files. A variable width font might mean more of a redesign than just a simple font change.

souk21 · 07-09-2021, 06:57 AM

I think it's definitely better to have a monospace font for the render stats

Arthur · 07-09-2021, 07:15 AM

Quote:

Originally Posted by BartR

Great!

May I suggest to change the name "Dry Rendering" with something more intuitive?
Many thought it was a rendering without FX chain.

+1
Maybe "Rendering Preview"

Meo-Ada Mespotine · 07-09-2021, 07:16 AM

Rather "Loudness Calculation".

Ideosound · 07-09-2021, 07:19 AM

Quote:

Originally Posted by Funkybot

I suspect the font choice has to do with keeping the columns aligned when rendering multiple files. A variable width font might mean more of a redesign than just a simple font change.

That's a good point that I hadn't considered. Still think it would look better in one uniform font but if it's a huge undertaking and might mean different layout/display issues then I can live with it.