v6.61+dev0626 - June 26 2022

[daniellumertz]

v6.61+dev0626 - June 26 2022

• * Includes feature branch: render fade-in/fade-out
• * Includes feature branch: pan law/function improvements
• * Includes feature branch: media explorer loudness calculation
• * Includes feature branch: render statistics improvements
• * Includes feature branch: fixed lane play markers
• * Includes feature branch: improve experimental silent-track CPU reduction option to include FX tail length
• * Includes feature branch: media item fixed lanes
• * Includes feature branch: internal pin management overhaul for future extension
• + Pan: fix UI glitches when changing project and per-track pan modes [p=2572042]
• + Pan: improve behavior of hybrid taper with certain manually entered pan laws (thanks ErBird) [p=2572055]
• + 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: fix editing when partial measures exist in project [p=2572470]
• + Razor edits: fix trim action when there are multiple razor edit areas on a single automation item
• + VST: round VstTimeInfo::samplePos to nearest sample [t=268181]
• # FX: improve parameter link behavior on sample accurate automated fx [p=2572528]

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

[Mercado_Negro]

Please consider an option or modifier to change all selected tracks pan laws and/or pan modes at the same time

[musicbynumbers]

# FX: improve parameter link behavior on sample accurate automated fx [p=2572528]

Hi Justin.

Only been able to try this for a short period tonight but on the big 5 day orchestral set up and so far it seems to work great!

Thanks for the effort on this. You've saved my sanity knowing that those days weren't for nothing!

I'll try some other stuff tomorrow but seems fixed so thanks a googolplex for that!

[srdmusic]

I've been experiencing some odd GUI behavior with some of my VST3 instruments. The GUI's are not resizing correctly to fit my FX Chain window. East West Play and Opus opens too large. Softube Model 84 opens too small. Please see the images below for reference. As you can see the GUI get cut off or there is a large black area where the plugins not sizing up correctly.

I believe the issue may be related to the following pre-release updates:

v6.61 - June 17 2022
+ VST: improve initial size behavior with plug-ins that adjust size when UI opens (Kee Bass)

v6.60 - June 8 2022
+ FX: allow resizing FX windows beyond screen size on Windows

[srdmusic]

I've experimenting with the feature branch: improve experimental silent-track CPU reduction option to include FX tail length

I've noticed that some instruments that produce a small audio glitch when they come back online. For example, I have a session where there's no media playing back at Bar 1 of my sequence. So Reaper shuts off processing the plugins on the track. Then when media starts playing at bar 2, the instrument comes back online and I hear a small audio glitch as soon as audio is supposed to play back.

Perhaps we need a fail safe small fade in and out when an instrument or fx goes on/offline. That way if an instrument shuts off before the tail is fully played out, there won't be an audio glitch when the fx goes offline. Same goes for a small fade in on all instruments coming online.

This audio glitch also seems to be reproducible if an effect is automated on/offline while audio is still playing through the plugin. It hard cuts the audio and causes the glitch.

I believe a small fade similar to the following preference would fix the issue:

[Justin]

Originally Posted by srdmusic

I've been experiencing some odd GUI behavior with some of my VST3 instruments. The GUI's are not resizing correctly to fit my FX Chain window. East West Play and Opus opens too large. Softube Model 84 opens too small. Please see the images below for reference. As you can see the GUI get cut off or there is a large black area where the plugins not sizing up correctly.

I believe the issue may be related to the following pre-release updates:

v6.61 - June 17 2022
+ VST: improve initial size behavior with plug-ins that adjust size when UI opens (Kee Bass)

v6.60 - June 8 2022
+ FX: allow resizing FX windows beyond screen size on Windows

Can you tell me the exact release that each of these changed behavior with? Thanks.

[Justin]

Originally Posted by srdmusic

I've experimenting with the feature branch: improve experimental silent-track CPU reduction option to include FX tail length

I've noticed that some instruments that produce a small audio glitch when they come back online. For example, I have a session where there's no media playing back at Bar 1 of my sequence. So Reaper shuts off processing the plugins on the track. Then when media starts playing at bar 2, the instrument comes back online and I hear a small audio glitch as soon as audio is supposed to play back.

Perhaps we need a fail safe small fade in and out when an instrument or fx goes on/offline. That way if an instrument shuts off before the tail is fully played out, there won't be an audio glitch when the fx goes offline. Same goes for a small fade in on all instruments coming online.

This audio glitch also seems to be reproducible if an effect is automated on/offline while audio is still playing through the plugin. It hard cuts the audio and causes the glitch.

I believe a small fade similar to the following preference would fix the issue:

A fade is not the answer. (it shouldn't be at least)

If there's a plug-in that is misreporting it's tail length, you can try enabling the compatibility setting to use automatic tail length detection...

It could also be that the plug-in is not properly flushing at playback start, and you're hearing the result of previous output -- you can try toggling "hard reset on playback start" for a problematic plug-in, which could help.

[srdmusic]

Originally Posted by Justin

A fade is not the answer. (it shouldn't be at least)

If there's a plug-in that is misreporting it's tail length, you can try enabling the compatibility setting to use automatic tail length detection...

It could also be that the plug-in is not properly flushing at playback start, and you're hearing the result of previous output -- you can try toggling "hard reset on playback start" for a problematic plug-in, which could help.

Thanks for the quick response Justin. Most of the problems I'm hearing are not tail related. They are at the start of midi note. The midi note triggers which turns Kontakt back on, then I hear a pop before audio starts.

[mschnell]

Originally Posted by musicbynumbers

# FX: improve parameter link behavior on sample accurate automated fx [p=2572528]

Seem great. but what exactly does it mean ? No involvement of the GUI thread with envelope or Midi based parameter modulation ?

(I recently tried to do some tests but Juce did not support sample accurate parameter modulation yet. Right now a new Juce version is out. I did not et check out that one.)
-Michael

[srdmusic]

Originally Posted by Justin

Can you tell me the exact release that each of these changed behavior with? Thanks.

reaper659+dev0602_x64 seems to the the first occurrence of the error. Everything after this version also has the error.

reaper659_x64 Public Release and v6.58+dev0526 and every version before works as expected.

Strange thing is that there's nothing in the release notes for 659+dev060 version that would point to a change with plugin GUI's

Let me know if you need any more information.

Thanks Justin.

[Zmey79]

How tired I am of this:

https://disk.yandex.ru/i/2X7Enf4PxGdZqw

[cool]

Originally Posted by Zmey79

How tired I am of this:

https://disk.yandex.ru/i/2X7Enf4PxGdZqw

Привет. Создай тему в баг репортах, там это будет уместно и больше вероятности, что исправят. Эта тема только для багов dev версий.

eng:
Hi. Create a topic in bug reports, it will be appropriate there. This topic is only for bugs in dev versions.

[musicbynumbers]

Originally Posted by mschnell

Seem great. but what exactly does it mean ? No involvement of the GUI thread with envelope or Midi based parameter modulation ?

(I recently tried to do some tests but Juce did not support sample accurate parameter modulation yet. Right now a new Juce version is out. I did not et check out that one.)
-Michael

This is relating to a change in behaviour which had been done for vst2 but is also now done for vst3 (including if it's sample accurate).

All it means is that a vst parameter which is also controlled via midi input (using reaper's parameter linking) remembers its last value it received via midi CCs even after the project is closed and reopened.

Before it would chase back to 0 as if it was expecting values from midi items but now it stays at last value till it receives new input.

The sample accurate bit was because it was fixed in last build for vst2 but needed a secondary fix to sort out vst3 sample accurate parameters

[Zmey79]

Originally Posted by cool

Привет. Создай тему в баг репортах, там это будет уместно и больше вероятности, что исправят. Эта тема только для багов dev версий.

eng:
Hi. Create a topic in bug reports, it will be appropriate there. This topic is only for bugs in dev versions.

Да я создал и раньше создавал тоже. Джастин знает об этом, исправлял,чё-то там,так и не исправил нихрена). Там тоже создана тема и сейчас.

[PitchSlap]

Originally Posted by daniellumertz

v6.61+dev0626 - June 26 2022
* Includes feature branch: improve experimental silent-track CPU reduction option to include FX tail length

I really hope before this feature is finalized there's a way to enable auto-bypass in existing projects that doesn't require doing it one at a time.
I've probably opened 5,000 or more FX windows to enable this (which annoyingly always open in the top-left when my mixer is in the bottom right)

An action to have existing instances in a project use the default setting for new instances would turn hours of monotonous work into one-click per project.

There's also no easy way to know a plugin's auto-bypass status.
Studio One shows each plugin's "sleep" status and allows easily enabling/disabling all in one place. This would be ideal for the FX section of the Project Bay and solve multiple issues at once.

[Justin]

Originally Posted by PitchSlap

I really hope before this feature is finalized there's a way to enable auto-bypass in existing projects that doesn't require doing it one at a time.
I've probably opened 5,000 or more FX windows to enable this (which annoyingly always open in the top-left when my mixer is in the bottom right)

An action to have existing instances in a project use the default setting for new instances would turn hours of monotonous work into one-click per project.

There's also no easy way to know a plugin's auto-bypass status.
Studio One shows each plugin's "sleep" status and allows easily enabling/disabling all in one place. This would be ideal for the FX section of the Project Bay and solve multiple issues at once.

There's a project setting which can be enabled on your existing projects.

Once that is enabled, various plug-ins that properly report their tails will work. Plug-ins that don't properly report their tails will need some compatibility settings tweaked, which you can do (but doing it for problematic plug-ins is a per-plug-in thing and not a per-instance thing).

[Mercado_Negro]

But what if this feature was polished a bit more like StudioOne's? Just to make it easier for the end-user. Maybe use the Performance Meter to disable, enable, tweak, etc., auto-bypass on plugins? or maybe on the FX tab on the project bay?

[Justin]

Looking at some project bay improvements yeah

[srdmusic]

Originally Posted by Justin

Looking at some project bay improvements yeah

Thank you Justin, This performance window from Studio One looks nice. Maybe in the track list the user check a box to nap all plugins per track and we could have some kind of indicator like this moon shaped icon to let the user know that everything on that track is auto-bypassing.

If you think it's to problematic to auto-bypass on the track level, It would be nice to have a list of every plugin in the session like this studio one screen shot. That way a user could quickly adjust the auto-bypass setting per plugin.

[srdmusic]

Originally Posted by PitchSlap

I really hope before this feature is finalized there's a way to enable auto-bypass in existing projects that doesn't require doing it one at a time.
I've probably opened 5,000 or more FX windows to enable this (which annoyingly always open in the top-left when my mixer is in the bottom right)

An action to have existing instances in a project use the default setting for new instances would turn hours of monotonous work into one-click per project.

There's also no easy way to know a plugin's auto-bypass status.
Studio One shows each plugin's "sleep" status and allows easily enabling/disabling all in one place. This would be ideal for the FX section of the Project Bay and solve multiple issues at once.

Does anyone know what the "Dropout Protection" setting does in this Studio One screen shot? Is that similar to "Anticipatory FX processing/ media buffering" or ASIO guard in Cubase?

[musicbynumbers]

Did a few more orchestral bits today and the parameter linking fix still seems to be working great thanks!

[Funkybot]

Originally Posted by srdmusic

Does anyone know what the "Dropout Protection" setting does in this Studio One screen shot? Is that similar to "Anticipatory FX processing/ media buffering" or ASIO guard in Cubase?

Yeah, it's Studio One's version of a dual-buffer design. Tracks without input monitoring getting a higher buffer. It's a pretty piss-poor implementation though. What they do for the input monitored tracks is basically create a copy of the FX chain and link the live/monitored copy to the inactive copy via parameter automation to keept he FX in sync. The issue is that when you move a plugin parameter on the live FX chain, you will only hear the chain if the parameter has a VST automation parameter. So FX with modulor automation assignments, like Amplitube5 for example, will have you moving plugin parameters and not hearing the changes until you toggle input monitoring.

[Thonex]

SOLVED -- See this post: Post #29

I think I found a bug in the Fixed Lanes feature. After I've finished with fixed lanes on one track, if I decide to create another track and use the OLD lanes (without Fixed Lanes checked on the track), the track switches to Fixed Lanes as soon as I record a 2nd overlapping item.

Cheers,

Andrew K

[Thonex]

Bug:

Option-Dragging (copy-dragging) an item track creates a TON of undo points when using a trackpad... and only fewer unnecessary ones when using a mouse.

MBP OS 12.2.1

[tonalstates]

Originally Posted by Thonex

Bug:

Option-Dragging (copy-dragging) an item track creates a TON of undo points when using a trackpad... and only fewer unnecessary ones when using a mouse.

MBP OS 12.2.1

Yesterday I experienced this too but in the official 6.61 release. This also happened when cutting items with razor edit then muting them, when trying to undo all that, it had like 10 undo point before the razor edit area appeared back. I just restarted reaper and it worked fine again.

I'll see if it happens again.

[Thonex]

Originally Posted by tonalstates

Yesterday I experienced this too but in the official 6.61 release. This also happened when cutting items with razor edit then muting them, when trying to undo all that, it had like 10 undo point before the razor edit area appeared back. I just restarted reaper and it worked fine again.

I'll see if it happens again.

Yeah... I didn't try restarting, but I did notice it was even adding unnecessary Undo points when using a mouse. I use an older version on my "official rig" (v6.38) and the Option-Drag (drag copy) worked without issue on the older system.

[schwa]

Originally Posted by Thonex

I think I found a bug in the Fixed Lanes feature. After I've finished with fixed lanes on one track, if I decide to create another track and use the OLD lanes (without Fixed Lanes checked on the track), the track switches to Fixed Lanes as soon as I record a 2nd overlapping item.

In the Options menu, what is enabled under "new recording that overlaps existing media items" ?

[PitchSlap]

Originally Posted by srdmusic

I've been experiencing some odd GUI behavior with some of my VST3 instruments. The GUI's are not resizing correctly to fit my FX Chain window. East West Play and Opus opens too large. Softube Model 84 opens too small. Please see the images below for reference. As you can see the GUI get cut off or there is a large black area where the plugins not sizing up correctly.

I believe the issue may be related to the following pre-release updates:

v6.61 - June 17 2022
+ VST: improve initial size behavior with plug-ins that adjust size when UI opens (Kee Bass)

v6.60 - June 8 2022
+ FX: allow resizing FX windows beyond screen size on Windows

I've also been having similar issues. GUI's cut off, incorrect window resizing, and I had a problem where Fab-Filter/DMG plugins would have the GUI blown up about 3-4x the size in the same space (most controls inaccessible).
Sometimes switching to the generic GUI and back fixes things, but not always.

I recently upgraded to 4K monitors so thought it might be specific to my system.

[Thonex]

Originally Posted by schwa

In the Options menu, what is enabled under "new recording that overlaps existing media items" ?

Hi Schwa... sorry for not getting back earlier.

Here were my settings:



Ahh... I guess I should use the top one for default Takes functionality.

Thanks Schwa!

Cheers,

Andrew K

[Embass]

[Embass]

[Embass]

[Embass]

[Embass]

[Embass]