v6.48rc1 - February 18 2022

[Meo-Ada Mespotine]

v6.48rc1 - February 18 2022

• + Actions window: fix issue with SWS cycle action editor on macOS/Linux (Windows will require sws update) [p=2527059]
• + Custom actions: fix add of actions to custom action via keyboard
• + Custom menus: fix support for more than 1024 menu items per menu
• + Custom menus: fix support for more than 32 submenus per menu
• + FX envelopes: copy/move envelopes correctly between instances of ReaSurroundPan with different configurations [p=2526379]
• + JSFX: channel_mapper uses dropdown instead of +/- buttons to set number of channels
• + JSFX: fix adjusting user-mix faders [p=2528443]
• + Knobs: improve alignment of wet/dry knobs
• + Media explorer: cancel metadata edit if file list is scrolled
• + Media explorer: prevent unnecessary scroll-to-left when browsing
• + Media item properties: reset volume/pan slider on double-click [t=263028]
• + Media item ruler: always label item start and end if possible [t=262144]
• + Media items: fix possible incorrect calculation when running action to clear and recalculate auto-stretch at project tempo changes
• + Media items: fix possible stretch marker corruption when applying auto-stretch at tempo changes [t=257439]
• + Media items: recalculate auto-stretch markers when undoing tempo envelope edits [t=257439]
• + Media items: set default normalization mode to peak for new users
• + Menus/toolbars: in customize menus/toolbars window, leave OK button enabled even if there have been no changes [p=2526098]
• + Preferences: include mouseover help text in search terms
• + ReaLimit: rename "link" control to "constant gain"
• + ReaLimit: set default threshold and ceiling both to 0dB
• + ReaScript: IDEs allow changing font name via ide_font_face= in reaper.ini
• + ReaScript: do not run scripts from cwd rather than reascript path [t=262921]
• + Render: fix persistence of preference to embed XMP markers [t=263105]
• + Render: fix rendering to mp3 when sample rate is set higher than 48k [t=263248]
• + Render: support jumping to loudest sample in project after render (including dry run render)
• + Takes: fix theme preference to display colored bar on active take when empty, not-displayed take lanes exist [t=262607]
• + VST3: set channel index context correctly for track 1 [t=263201]
• + VST: fix various UI sizing quirks
• + macOS: disable input event throttling by default
• + macOS: fix ExecProcess() handle leakage [t=263197]
• + macOS: fix Metal issue where an occluded window would end up stale on macOS 12
• + macOS: fix knob background drawing after switching to/from dark-mode
• # FX: improve sizing of certain plugins when auto-resize is not enabled [p=2526450]
• # JSFX: fix radio buttons in channel_mapper
• # VST: enable container wrapper windows by default for vst2 [p=2524015]

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

[Paul Eye]

Originally Posted by Meo-Ada Mespotine

+ ReaLimit: rename "link" control to "constant gain"

Any particlar reason for this? Apart from the possible confusion with "stereo link" that I remember came up when ReaLimit was still in the +dev versions. I'm not sure if "constant gain" gets the function of the checkbox across any better. Of course, keeping the gain constant is what it does, by linking the values of the threshold and ceiling faders, so now it's just swapping the checkbox name to the other part of what it does.
Yeah, I know, probably just nitpicking

[Gass n Klang]

Originally Posted by Meo-Ada Mespotine

v6.48rc1 - February 18 2022[*]+ Render: support jumping to loudest sample in project after render (including dry run render)

It would be so nice to have an option that creates a marker at every clipping sample.

[creal]

Originally Posted by Gass n Klang

It would be so nice to have an option that creates a marker at every clipping sample.

You're right. I second this too!

[amagalma]

Originally Posted by Gass n Klang

It would be so nice to have an option that creates a marker at every clipping sample.

Nice idea, if the clips are just a few.

[BartR]

Item lanes and Oversampling definitely dropped?

[BartR]

Originally Posted by creal

You're right. I second this too!

This will be really nice!

[Gass n Klang]

Originally Posted by amagalma

Nice idea, if the clips are just a few.

yes, could be also just an option to jump to clipping samples. I think sequoia can do that. Quite helpful!

[schwa]

Originally Posted by BartR

Item lanes and Oversampling definitely dropped?

Not dropped, but not yet ready to be released. These features will continue to be in +dev builds for now.

[Lynx_TWO]

Originally Posted by schwa

Not dropped, but not yet ready to be released. These features will continue to be in +dev builds for now.

Good to know! I really appreciate the work y’all are putting in on oversampling FX. Loving that feature!

[mschnell]

Originally Posted by Gass n Klang

It would be so nice to have an option that creates a marker at every clipping sample.

Clipping when rendering ? I.e. feeding the information from the rendering process back into the project ?

(I suppose we don't have an infinite count of markers )

-Michael

[Meo-Ada Mespotine]

Originally Posted by Gass n Klang

It would be so nice to have an option that creates a marker at every clipping sample.

+1,that would be really helpful

Originally Posted by mschnell

Clipping when rendering ? I.e. feeding the information from the rendering process back into the project ?

(I suppose we don't have an infinite count of markers )

-Michael

Regions perhaps instead of markers? For areas with a lot of clippings coming one after another.

If not feasible, some actions to go forward/backwards through the found clipping positions from the last used render would be helpful too.

[Gass n Klang]

Originally Posted by mschnell

Clipping when rendering ? I.e. feeding the information from the rendering process back into the project ?

(I suppose we don't have an infinite count of markers )

-Michael

well, reaper already shows read lines where clipping occurs. So jumping to these points shouldn't be a big thing.

[mschnell]

That would mean leaving the render result window open while restarting to work in the project, avoiding additional "clip markers".
Seems viable.

-Michael

[bobobo]

i think we have

.Jump to the first clip position in project

in dry run
just click the stats button

.

greetings

[Funkybot]

Originally Posted by Meo-Ada Mespotine;2528604[*

+ macOS: disable input event throttling by default

I'm guessing this would impact mousewheel events. I noticed that mousewheeling over FX Paramaters suddenly had a way bigger effect than I was used to. I'd also recently installed Smooze Pro to improve mousewheel scrolling using a third-party mouse. Anyway, turning "disable input even throttling" back on improved the behavior. Just not sure what the rationale was for turning it off by default was, and/or the overall pros and cons. On my particular setup, definitely preferred it on.

[gkurtenbach]

When I open a file with stretch markers mapped to tempo changes the first stretch marker gets moved.

I've attached a project that shows the bug. Open it with v6.45 and you will see the first stretch marker is at 1.0 stretch (and track lines up with click).

Open the same project with v6.48 and the first marker is changed to 0.97 stretch (and the track is out time with click until the next stretch marker).

Stretch markers at around bar 25, 63, 76 also seem to have wrong stretch values.

(I can't attach the rar of the project file--says I need a security key) Here's a link to rar:

https://www.dropbox.com/s/9n7w6tkdc8...poBug.rar?dl=0

[schwa]

Originally Posted by gkurtenbach

When I open a file with stretch markers mapped to tempo changes the first stretch marker gets moved.

Ah, thank you for posting the project. This bug was caused by the fix to this bug!

We'll put out a new build shortly with the fix.

[gkurtenbach]

Thanks!

Yeah, kill one bug and another shows up for the funeral, as they say.

[Breeder]

Originally Posted by Meo-Ada Mespotine

+ Custom menus: fix support for more than 1024 menu items per menu
+ Custom menus: fix support for more than 32 submenus per menu

Thank you so much for this!