v6.65rc1 - August 10 2022

[Edgemeal]

v6.65rc1 - August 10 2022

* Includes feature branch: pan law/function improvements
+ Audio Units: fix support for AUv3 musical time/tempo/transport state callbacks
+ Automation items: fix behavior of action to split items without changing selection
+ Configuration files: fix various issues for FX shortcut/safemode/etc settings on plug-ins/themes with odd filenames
+ Envelope window: improve appearance with scrollbars and retina displays
+ Envelopes: encode FX envelope name in project file, use when loading with FX offline [t=269009]
+ FX browser: allow configuring defaults per-plugin of want-all-keyboard, TCP/MCP embed, and oversampling
+ FX browser: move compatibility settings to submenu
+ FX: add option to use space key to start/stop transport in plug-in text edit fields [t=268837]
+ FX: add oversample options to floating FX window context menu
+ FX: fix generic UI when last parameter is an enum
+ FX: improve syncing displayed value in generic UI [p=2583032]
+ FX: optimize performance with many docked-but-invisible FX chains [t=267313]
+ FX: when setting compatibility settings, update all open FX instances
+ Grouping matrix: add grouping specific help, accessible via the (?) button
+ Grouping: right-click in grouping matrix opens group settings dialog for already-selected tracks, rather than auto-selecting tracks
+ Linux: improve behavior of text edit fields with ctrl+shortcuts
+ MIDI editor: actions to move edit cursor by grid respect snap setting
+ Media explorer: support typing in preview volume
+ Media items: fix flickering when moving media items across tracks and "automatically display affected envelopes" is enabled
+ Media: sort insert-media file description/extension dropdown in alphabetical order
+ Mouse modifiers: add modifier to move or tilt envelope (fine adjustment)
+ Pan: document ReaScript/API setting for pan law flags
+ Pan: explicitly support constant power, linear taper, or restricted constant power pan functions [p=2571092]
+ Pan: fix implementation of constaint power pan law restricted to linear above -3dB when applying gain compensation
+ Pan: fix pan evaluation offset when stopped [p=2571736]
+ Pan: improve behavior of hybrid taper with certain manually entered pan laws (thanks ErBird) [p=2572055]
+ Pan: only list deprecated pan mode in pan law dialog if the project already has pan mode set that way
+ Pan: rename pan law options to sin/cos taper, linear taper, and hybrid taper
+ Pan: simplify pan law preferences
+ Pan: special case -3dB and -6dB pan law to be exactly equivalent to equal power and equal gain respectively; preserve existing settings in existing projects
+ Razor edits: ignore razor edit areas on envelopes when running action to crossfade media items [p=2579146]
+ ReaGate: implement string to parameter conversion for threshold
+ ReaLimit: fix continuous automation recording [t=268807]
+ Region render matrix: add region render specific help, accessible via the (?) button
+ Region/Marker Manager: fix display glitch when resizing
+ Render: add button to display rendered file in Media Explorer
+ Routing/Grouping/Render matrix: dynamically adjust margins to fit text
+ Theme: fix 3 small issues [p=2581377]
+ Theme: fix mixer send knob 150% image
+ VST3: IContextInfoProvider3 support
+ VST3: fix return value for IContextInfoProvider::setContextInfoValue
+ VST: support IComponentHandler2::setDirty [t=268392]
+ WALTER: fix h variable in tcp.fxembed context [p=2584238]
+ Windows: improve alt-key behavior relating to menu activation and cursor updating
+ macOS: support decoding .rx2 files on native Apple Silicon
# FX: fix delayed plug-in UI opening when showing chains manually [p=2566273]
# FX: fix duplicate parameter label in generic UI for some plugins [p=2584487]
# Pan: ensure consistent checkbox state when opening pan law dialog [t=267957]
# Pan: rename sin/cos taper to sine taper (just as descriptive and a little less odd sounding)
# VST: remove previous allow spaces in reaper-vstplugins.ini filenames function (preserve existing behaviors/bindings/etc)

Full changelog - Latest pre-releases

[playtimer]

I just posted about this VST2 -> VST3 bug earlier today, so can we have some info about it?

https://forum.cockos.com/showthread.php?t=269523

Thanks!

[sockmonkey72]

Originally Posted by playtimer

I just posted about this VST2 -> VST3 bug earlier today, so can we have some info about it?

https://forum.cockos.com/showthread.php?t=269523

Thanks!

Are you being serious?

[playtimer]

Originally Posted by sockmonkey72

Are you being serious?

Yes, why?

[citizenkeith]

Originally Posted by playtimer

Yes, why?

Feature requests: please do not post general feature requests in the pre-release forum. If you have a suggestion DIRECTLY related to the behavior and/or scope of a new feature of the build in question, it is generally polite to post and discuss there.

[playtimer]

Originally Posted by citizenkeith

Feature requests: please do not post general feature requests in the pre-release forum. If you have a suggestion DIRECTLY related to the behavior and/or scope of a new feature of the build in question, it is generally polite to post and discuss there.

Ah, forgot about it. Wrong direction - my bad!

[Funkybot]

Originally Posted by Edgemeal

+ FX: add option to use space key to start/stop transport in plug-in text edit fields

Any way to get the spacebar working to create spaces in Softube plugin preset fields? That's been a minor pet peeve of mine for a while and I can't seem to find a combination of settings to get that working.

[dom64]

Originally Posted by Funkybot

Any way to get the spacebar working to create spaces in Softube plugin preset fields? That's been a minor pet peeve of mine for a while and I can't seem to find a combination of settings to get that working.

Yep - no idea. Would be cool.

[Edgemeal]

Did you try setting Space key Scope to Global, and using Shift+Space keys to enter space in GUI plugins?
EDIT What I meant to say was, If you have space key scope set to global then try using shift+space.

I mainly set space key Scope to Global because after removing an FX from an FX Chain window REAPER's input focus goes to no mans land and space key no longer worked (to toggle play/stop), but then in plugins that use a GUI (not textbox) I have to use Shift+Space keys to enter a space key in them.

[EvilDragon]

Originally Posted by Funkybot

Any way to get the spacebar working to create spaces in Softube plugin preset fields? That's been a minor pet peeve of mine for a while and I can't seem to find a combination of settings to get that working.

Shift+Space should work in all such instances where regular Space doesn't work, I think.

[dom64]

Not so with Amproom... haven't tried other Softube plugins.

[Funkybot]

Originally Posted by Edgemeal

Did you try setting Space key Scope to Global, and using Shift+Space keys to enter space in GUI plugins?

Tried that. No dice. Nothing adds a space in the Softube preset field. Thanks for the reply though (ED too)!

To reproduce:

1. Load up any Softube plugin
2. Click on the Preset box and select "Add Preset"
3. Try anything you can think of to get the space character in the preset name (Send all Keyboard shortcuts to plugin, Space (global) + Shift+Space, etc.)

Result: no space, no matter what.

I got to the point where I questioned if Softube just didn't allow it and confirmed that this box works fine in Studio One and spaces are allowed.

[Justin]

Originally Posted by Funkybot

Any way to get the spacebar working to create spaces in Softube plugin preset fields? That's been a minor pet peeve of mine for a while and I can't seem to find a combination of settings to get that working.

what OS? which state is your spacebar/fx option set to? does "send all keyboard input to plug-in" help?

[Funkybot]

Originally Posted by Justin

what OS? which state is your spacebar/fx option set to? does "send all keyboard input to plug-in" help?

Windows. VST and VST3 versions of the plugins.

Preferences -> Keyboard -> Spacebar from FX to Main Window unchecked. EDIT: tried checked just to be thorough, made no difference.

"Send all keyboard input to plugin" does not help.

Thanks for inquiring! Hope this can get squished like a spotted lantern fly (for those not in the Northeastern united states, these have become an invasive pest).

[Justin]

Originally Posted by Funkybot

Windows. VST and VST3 versions of the plugins.

Preferences -> Keyboard -> Spacebar from FX to Main Window unchecked. EDIT: tried checked just to be thorough, made no difference.

"Send all keyboard input to plugin" does not help.

how about with "send all keyboard input to plugin" AND in the floating window (rather than the chain window)?

[Funkybot]

Originally Posted by Justin

how about with "send all keyboard input to plugin" AND in the floating window (rather than the chain window)?

I previously was using floating plugin windows and it wasn't working. So I just tested an FX Chain window and same result. Not working.

And while this was almost certainly clear, just in case it wasn't, I'm using Softube's internal preset system.

[Justin]

ah got it, actually a trivial fix

[Funkybot]

Originally Posted by Justin

ah got it, actually a trivial fix

Great news. Thanks Justin!

[bolgwrad]

Reaper's a keeper, though.

[BrokenTriplet]

Originally Posted by Funkybot

Any way to get the spacebar working to create spaces in Softube plugin preset fields? That's been a minor pet peeve of mine for a while and I can't seem to find a combination of settings to get that working.

In plugins where I have this issue, I normally press shift-space and it works, it does so in Model 84, but that's the only softube plugin with presets that I have.

[ovnis]

+ FX: optimize performance with many docked-but-invisible FX chains

There are issues performance if the FX window is docked to the right (there is no issue when the window is docked to the bottom).

The FX window disapears a short time. It seems worst when the plugs are big and built with bitmap.
When the FX window disapears, reaper arrangement window freezes. The edit cursor or the play cursor freezes:



There is no issue with FX windows docked to the bottom. It's fast. No window which disapears:

[Justin]

hmm if a plug-in UI is slow to open, it should be the same regardless of where it is docked (or if not docked at all!) -- the UI thread is responsible for opening the UI and its updates should likely block while it does that.

[ovnis]

There is this slow issue even with the midi editor docked to the right (like with the midi editor, it seems there is a "parasite" frame which slows down the display):

https://forum.cockos.com/showpost.ph...&postcount=275
And after this message, I have talked with Feedthecat about the issue.

-------------------------

I have used the 2 same plugs with docked to the right and to the bottom.


Here, it's slow. We can this that fx window disapears a short time:




Here, it's fast. We can this that fx window remains:

[ovnis]

I have pasted the good gif for the last exemple.

[Justin]

hmm those examples also have playing back in one gif and stopped in the other

[ovnis]

After lots of tests, I have realized than this "parasite" frame happens if there are at least two dockers docked at the same side. For exemple, two dockers docked at the bottom or at the right.

It's pretty odd. I have been fooled by gif and the action I have used to open FX window.

The action used is:
Select track under mouse
View FX chain for current track.

When the FX chain is docked inside a docker which shares the same side slot with an another docker, "select track under mouse" works very fast, but not always when the FX chain is docked inside a docker which doesen't shares his side slot.

IF the FX chain is docked in a shared side slot, there is an amount of time between the selected track and the opening of the FX chain.

If the FX chain is docked in a shared side slot, there is an amont of time between the action trigger and the track selection/FX chain opening. So, if we look a gif recording of this sequence, we can think it's very fast (because we don't know when I have triggered the action) or it's not very fast. It's probably the same amount of time.

In this case, I prefer the first behaviour because the track is selected faster.

It remains than "parasit" frame / FX chain which disapears a short time looks bad/bugged.


--------------


And for the MIDI editor + MIDI Editor Magic script, this parasit frame is a real issue because the display of the MIDI editor becomes really slow:


Feedthecat has added this code to avoid this issue with MIDI editor docked
(they are some flashing when we switch between MIDI item which are not on the same track (One MIDI editor per project. Open all MIDI on the same track).
It happens @stock (without script), too :


An another exemple of the issue with slow motion (If I switch between items, the midi editor scrolls twice... It should move only once time.):


But with the FIX, even on a docker who doesn't share his slot, his fix seems to slow the display, so I will probably not use it. I don't know yet.