v6.35rc1 - August 16 2021

[musicbynumbers]

v6.35rc1 - August 16 2021

• + API: if track VU is metering loudness, API (ReaScript, control surface) peaks functions return loudness as well
• + Action list: optionally match synonyms of common words when searching for action names ("display" matches "show", etc)
• + Action list: pull list of synonyms from langpack actionlist_synonyms section
• + Area selection: support stretch markers in media items that contain empty take lanes, if there is at least one audio take [t=256443]
• + Automation: obey grid/snap settings when using freehand draw
• + Automation: restore 6.33 behavior when adding a single point via freehand draw [t=256406]
• + FX: add clear option to FX pin mapping dialog
• + FX: add reset button to FX pin mapping dialog
• + JSFX: support linked stereo channels in channel mapper user mix mode
• + MIDI: encode linear tempo changes on export as MIDI text messages that REAPER can interpret when reimporting (other applications will ignore these messages)
• + MP3: fix invalid memory access from unknown ETCO type in ID3v2
• + Marquee zoom: allow tracks to be sized smaller in order to fit on screen [t=256339]
• + Master VU: fix LUFS-S metering when readout set to current level rather than max or LRA [p=2471528]
• + Media item properties: support entering numeric values for take volume/pan
• + Metadata: fix embedding CART intro/segue markers that occur at the very start of the rendered file
• + Metadata: support embedding project markers/cues as XMP (for Premiere, After Effects, etc)
• + Performance: fix potential excessive UI CPU use/hang when closing project when edit cursor is offscreen [t=256285]
• + Project bay: increase project length if needed when dragging media items from project bay [t=254865]
• + Razor edits: fix editing envelope point that occurs at the start of an automation item [p=2471931]
• + ReaScript: add GetSetMediaTrackInfo support for getting/setting track VU mode
• + ReaSurround / ReaSurroundPan: allow plugin to support higher I/O channel count than the track or media item
• + ReaSurroundPan: add 9.1.2 surround setup
• + ReaSurroundPan: label an elevated speaker in the center of the room as "overhead", other elevated speakers as "height"
• + ReaSurroundPan: when LFE channel is selected, allow changing input faders to gain, but disable the channel text edit box
• + Render: add options to disable calculating loudness statistics
• + Render: display up to 512 vu meters, limited to the screen height
• + Render: iterate for increased precision when normalizing to LUFS-I
• + Render: more informative error message if target file cannot be created
• + Render: optimize loudness calculations
• + Render: separate render statistics header for clearer display when rendering many files
• + Render: support dithering primary and secondary render format to different bit depths [t=256483]
• + Render: support enabling LUFS-I/LUFS-M and LRA/LUFS-S statistics separately
• + Ripple editing: improve behavior of duplicate area selection action [t=256114]
• + Ripple editing: improve behavior of duplicate selected area of items action
• + Tempo markers: support tempo basis other than 1/4 note (affects displayed BPM number only, not metronome or tempo envelope display) [t=250880]
• + Theme: add meter_strip_h_rms image, consistently use loudness meter theme elements for tracks that are set to meter loudness
• + Track VU: add metering settings submenu to track context menu as well as track VU context menu
• + Track VU: support RMS stereo metering
• + Track VU: support metering RMS, LUFS-M, or LUFS-S
• + Tracks: support mono master/parent send
• + VST3: fix incorrect handling of IContextMenuItem flags
• + Windows: avoid potential splash screen hang when caught in an invalidate/postmessage loop [t=256285]
• # API: functions that return track peak levels (ReaScript, control surfaces, etc) still return peak levels even if the track is set to meter loudness
• # API: support optionally getting track loudness values (if track VU meters are displaying loudness) via Track_GetPeakInfo and Track_GetPeakHoldDB
• # Action list: ignore synonyms when using NOT qualifier
• # Dither: re-use the exact same dither if primary/secondary targets have the same bit depth
• # FX: don't reset pin connector if reset menu is closed without making a selection
• # JSFX: fix channel mapper mousewheel edits for linked channels
• # JSFX: improve stereo linking UI when horizontal scrollbar is showing
• # Master VU: localize loudness meter settings dropdown
• # Master/parent send: change .RPP storage of one-channel parent send setting (now warns if loaded in previous versions)
• # Media item properties: don't auto-update dialog while user is editing take volume or pan
• # Metadata: fix embedding XMP markers that occur at the very start of the rendered file
• # Meters: improve readout display on very small sizes
• # ReaSurroundPan: account for mono parent sends when setting channel display from sending track name/color
• # ReaSurroundPan: add action to set input channel display to sending track names/colors, option to automatically update if tracks change
• # ReaSurroundPan: minor labeling change for Auro speaker setups
• # Render: more optimizations to loudness calculations
• # Track VU: add option to display current instead of maximum value when track meters set to LUFS-S
• # Track VU: fix theme color for loudness readout in horizontal mode
• # Track VU: minor change to internal storage for track metering settings
• # Track VU: preserve playback peak metering behavior when record-armed and metering track output
• # Track VU: support post-fader loudness metering
• # Track meters: correct label tooltips for RMS vs LUFS
• # vst3: retain midi mapping, note expression controller and keyswitch controllers for lifetime of plug-in

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

[musicbynumbers]

lots of awesome stuff here guys thanks!

[EpicSounds]

😍 + Action list: optionally match synonyms of common words when searching for action names ("display" matches "show", etc)

Good to know I'm not the only one that has needed a Thesaurus to make custom actions.

👍 + FX: add clear option to FX pin mapping dialog
👍 + FX: add reset button to FX pin mapping dialog

👍 + Media item properties: support entering numeric values for take volume/pan
👍 + Tracks: support mono master/parent send

This is a great update

[vitalker]

Originally Posted by EpicSounds

😍 + Action list: optionally match synonyms of common words when searching for action names ("display" matches "show", etc)

Good to know I'm not the only one that has needed a Thesaurus to make custom actions.

Here is more:
https://forum.cockos.com/showpost.ph...5&postcount=22

Originally Posted by Justin

The current thought is that eventually the synonyms will be definable within each language pack.

[nofish]

This contradicts, but probably just because as the changelog isn't cleaned up yet.

Originally Posted by musicbynumbers

v6.35rc1 - August 16 2021

+ API: if track VU is metering loudness, API (ReaScript, control surface) peaks functions return loudness as well

# API: functions that return track peak levels (ReaScript, control surfaces, etc) still return peak levels even if the track is set to meter loudness

[Triode]

Thank you

[schwa]

Originally Posted by nofish

This contradicts, but probably just because as the changelog isn't cleaned up yet.

Yes, the first line is superseded by the second.

[nofish]

Originally Posted by schwa

Yes, the first line is superseded by the second.

Ah ok, thanks.
I was confused shortly because usually (often) it's the #... lines which don't end up in the final changelog I think but I vaguely remembered that you eventually ditched loudness metering via API so in this case it's the other way round.

[Mr. Data]

Originally Posted by musicbynumbers

• + Action list: optionally match synonyms of common words when searching for action names ("display" matches "show", etc)

Sounds interesting!
How is this handled, respectively will this be handled in localizations?


-Data

[schwa]

Originally Posted by Mr. Data

How is this handled, respectively will this be handled in localizations?

It's handled via localization. These are the lines in the sample langpack (available at landoleet.org) that represent the default synonyms, you can add or change whatever you want to:

[actionlist_synonyms]
;1=display,view,show,hide
;2=delete,clear,remove
;3=insert,add

[Mr. Data]

Thanks Schwa,

That's really awesome!


-Data

[RovingEye]

Originally Posted by musicbynumbers

v6.35rc1 - August 16 2021
[*]+ JSFX: support linked stereo channels in channel mapper user mix mode

Awesome!

[amagalma]

Originally Posted by schwa

It's handled via localization. These are the lines in the sample langpack (available at landoleet.org) that represent the default synonyms, you can add or change whatever you want to:

[actionlist_synonyms]
;1=display,view,show,hide
;2=delete,clear,remove
;3=insert,add

I have never messed with langpacks, so maybe my question is silly: will the changes get overwritten after a Reaper update?

[GonZ]

Still the bug which antomations items can be drag & drop from project bay just on track one, the rest are denied.

[Delucci]

Why isn't midi note reorder in the newest releases?

[deeb]

+ Action list: optionally match synonyms of common words when searching for action names ("display" matches "show", etc)

it's interesting and i think same concept could be applied for searches in Media Browser:
Example:
Drums .. drum .. DR
Kicks .. kick .. Bass drum .. BD
Snares .. snare .. SN ..
vocals .. vocal .. voice .. voices .. VOX

[Javier Robledo]

Originally Posted by schwa

It's handled via localization. These are the lines in the sample langpack (available at landoleet.org) that represent the default synonyms, you can add or change whatever you want to:

[actionlist_synonyms]
;1=display,view,show,hide
;2=delete,clear,remove
;3=insert,add

Really useful.
Thanks

[nofish]

Originally Posted by Delucci

Why isn't midi note reorder in the newest releases?

Probably because it's not release-ready yet.

edit:
For clarity, this is a rc (=release candidate) changelog,
I guess MIDI note reorder will come back in the next +dev cycle, after v6.35 has been released.

[Yanick]

It seems to me that already in several + dev versions the multichannel track metering was broken - it is impossible to turn on/off

[schwa]

Originally Posted by Yanick

It seems to me that already in several + dev versions the multichannel track metering was broken - it is impossible to turn on/off

It looks like the action "toggle full multichannel metering" isn't working properly, we'll fix that. But the other non-toggle track metering actions (there are eight of them) and the menu items seem to work as expected.

[Edison]

Originally Posted by schwa

It looks like the action "toggle full multichannel metering" isn't working properly, we'll fix that. But the other non-toggle track metering actions (there are eight of them) and the menu items seem to work as expected.

Hi schwa, (Posted here, because v6.35rc2 was not yet in the forum)

When opening the window, Batch File/Item Converter, it is correct to appear as 'Normalize ON' and not 'Normalize...'?

Ps. The Render to File window is as 'Normalize...'

Windows 7 64bit

Best regards,

[schwa]

In both cases the button should read "Normalize ON" only if normalizing is enabled.

[Edison]

Originally Posted by schwa

In both cases the button should read "Normalize ON" only if normalizing is enabled.

I know, so I found it strange because every time the Reaper is opened, the Batch File/Item Converter window is enabled to Normalize ON. See Pics


Best regards,

[akademie]

Originally Posted by schwa

In both cases the button should read "Normalize ON" only if normalizing is enabled.

Yeah, but just checked and the difference is really subtle "Normalize" vs "Normalize ON" ... for example checkmarks are much more apparent at first sight when one looks over the dialog window which options are ON or OFF. Try to think about it, please.
Thanks

EDIT: I was referring to Render dialog here.

[akademie]

Originally Posted by Edison

I know, so I found it strange because every time the Reaper is opened, the Batch File/Item Converter window is enabled to Normalize ON. See Pics


Best regards,

I think it's because the setting and status (enabled/disabled) is independent from each other (in Batch versus Render dialogs).
In batch it remembers your last settings (probably you converted files with Normailze enabled). Do some conversion with disabled and since then it will open in disabled state,, well until ...

[schwa]

Originally Posted by Edison

I know, so I found it strange because every time the Reaper is opened, the Batch File/Item Converter window is enabled to Normalize ON. See Pics

The batch converter has a global state, so if you normalized the last time you converted something, normalization will remain on until you disable it.

[Edison]

Originally Posted by schwa

The batch converter has a global state, so if you normalized the last time you converted something, normalization will remain on until you disable it.

@schwa

When you mentioned about 'Global state' to Bath Converter, it helped me in understanding. Now everything is Ok.

Thanks!