v7.0pre3 - August 5 2023

[dsyrock]

v7.0pre3 - August 5 2023

• * Includes feature branch: support rendering raw PCM data
• * Includes feature branch: Development_Theme theme
• * Includes feature branch: JSFX plug-in defined compile-time configuration parameters
• * Includes feature branch: LV2 non-automatable patch parameter support including atom:Path
• * Includes feature branch: video YUV gamut selection
• * Includes feature branch: visual track spacers
• * Includes feature branch: 128 channels per track
• * Includes feature branch: updated Windows manifest for newer OS features
• * Includes feature branch: always running non-bypassed FX when the UI is visible
• * Includes feature branch: crossfade new recording with existing media items if configured
• * Includes feature branch: video from background projects
• * Includes feature branch: FX containers
• * Includes feature branch: improvements to aligning takes after recording
• * Includes feature branch: arrange view override mouse modifier sections
• * Includes feature branch: toolbar armed/special animations
• * Includes feature branch: pooled and unpooled ARA edits
• * Includes feature branch: shortcut import/export improvements and multiple main keyboard sections
• * Includes feature branch: GR metering as embedded UI for third-party VSTs
• * Includes feature branch: media item fixed lanes
• + Media item lanes: improve shift+click item selection behavior in FIPM/fixed-lane tracks
• + Meters: add gain reduction metering preferences in Appearance/Track Control Panels
• + Meters: display gain reduction from plugins (for plugins that report it) in track meters
• + Preferences: move preference to control track parenting when mouse-dragging to Editing Behavior/Mouse page
• + ReaScript: update from Lua 5.3.5 to Lua 5.4.6 (this may affect existing ReaScripts)
• + Tracks: fix lane button and track grouping indicator display on retina/hidpi when preference allows maximum vertical zoom greater than 100%
• + Tracks: if preference allows maximum vertical zoom greater than 100%, allow manually resizing tracks to greater than the screen height
• + Tracks: if track height is greater than screen height, mousewheel scroll on TCP scrolls by screen height
• + Tracks: set maximum vertical zoom to 250% for new users (previous default was 100%)
• # Media item lanes: adjust comp areas when changing tempo and timebase is beats
• # Media item lanes: auto-name tracks created via action to explode lanes to tracks
• # Media item lanes: do not apply comp area fades to MIDI items if preference for MIDI fades is disabled [p=2698051]
• # Media item lanes: fix undo point after actions to explode lanes to tracks
• # Media item lanes: improve behavior when using razor edits on comp lane
• # Media item lanes: prevent edits on source lanes from affecting selected/grouped items on comp lane [p=2698003]
• # TCP/EnvCP resize indicators: fix retina drawing
• # Theme fixes
• # macOS: fix drawing of 1px-sized controls on retina displays

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

[fakemaxwell]

Reposting from the Theme Adjuster thread. The envelope divider is off a bit:



IMO the arrange view should be WALTER-able but have no idea how feasible that is.

[lexaproductions]

Originally Posted by dsyrock

v7.0pre3 - August 5 2023
[list][*]+ ReaScript: update from Lua 5.3.5 to Lua 5.4.6 (this may affect existing ReaScripts)[*][b]

Here are the incompatibilities:
https://www.lua.org/manual/5.4/manual.html#8
For example, the function:

io.lines

now return 4 parms.

[Mercado_Negro]

+ Meters: display gain reduction from plugins (for plugins that report it) in track meters

Thanks for this. How does a plug-in report this from a technical standpoint? I'm asking because most of my plug-ins are not reporting it: UAD and UADx, Softube, Empirical Labs, Vertigo Sound, Cytomic and iZotope just to name a few of them.

[cool]

+ ReaScript: update from Lua 5.3.5 to Lua 5.4.6 (this may affect existing ReaScripts)

Good! I had to do some manipulations to make my script work without errors.

Just for information: since the new version of lua doesn't need randomseed, lines containing math.randomseed now throw an error. I just removed those lines.

[Sexan]

Ability to vertically zoom selected lane to center of the screen (like "Last Selected Track") would be very welcome. Replacing the preferences to "Track Under Mouse" just to work with lanes is little awkward and any other vertical zoom options on lanes are pretty much useless (resetting the view, unintentional scroll etc) so user IS required to change it to "Under mouse" if he is working on the lanes. Been using Last selected track for years

[Sexan]

Originally Posted by fakemaxwell

IMO the arrange view should be WALTER-able but have no idea how feasible that is.

Or expose theme tweak/configuration parameters to script

[cyril_meysson]

Originally Posted by dsyrock

• + Meters: add gain reduction metering preferences in Appearance/Track Control Panels
• + Meters: display gain reduction from plugins (for plugins that report it) in track meters

Looks great and much more useable now, thanks a lot!

[mlprod]

Originally Posted by Sexan

Or expose theme tweak/configuration parameters to script

Definitely! Including the ruler.

[mlprod]

Theme again, the item vol knob should slightly change appearance when not at 0, like before.

[musicbynumbers]

always running non-bypassed FX when the UI is visible

Hi guys, could we have a temporary option in prefs to disable this?

The reason is I'm getting some weird stuck buffers when stopping/playing and glitches at 64 buffer size when before I wasn't and would be convenient if I could turn this on and off globally to test in each situation if this is the cause (rather than jumping back to a much older version which might break the projects I'm testing).

Sorry for the late feedback on this feature I know I begged for, I've only just started using reaper again for music writing and finding out some artifacts from it.

Thanks,

[White Tie]

Originally Posted by fakemaxwell

Reposting from the Theme Adjuster thread. The envelope divider is off a bit:

Actually this got fixed about 12 years ago, I had forgotten to add it. Thanks to FeedTheCat in said thread!

Originally Posted by fakemaxwell

IMO the arrange view should be WALTER-able but have no idea how feasible that is.

Originally Posted by Sexan

Or expose theme tweak/configuration parameters to script

There's a time and a place for theming feature requests, particularly these really fundamental ones that stretch back years. But given that we've only just got a rare major WALTER update, the custom elements, that we're supposed to be testing, that time is not now and that place is not here.

[musicbynumbers]

Default fade in and out on importing media from media explorer.

I really think this should be off by default. (it's now been turned on in 7 for me)

Newcomers surely won't expect imported media to be different to what they auditioned and when I use to teach reaper, the students were sometimes confused by the soft transient on the beats and drum hits they dragged in when this option was on and they didn't know it was

[White Tie]

Originally Posted by mlprod

Theme again, the item vol knob should slightly change appearance when not at 0, like before.

There's been occasional complaint about that in the v6 theme, though I completely agree that "this is unchanged" is a vital bit of state info, not the same as 'knob points at zero'. If I do it in the v7 theme, and there is complaint, don't be a stranger yeah?

[lucas_LCS]

Sorry, I haven't been able to pay attention to this.

Question 1:
Will the strip (Layout B) be give the Sidebar?
It would make the strip twice as useful to have the FX Sidebar show up when a track is selected.

Question 2:
How close is this to being released?
I see several things in the Theme adjuster that don't seem to work and also a couple of graphic anomalies.
I don't have time to test, document and report at the moment.

::

[musicbynumbers]

Audio from background projects

Please consider a feature for audio from background projects too.

I know we have the ability to route audio from background projects now manually but could we have a project tab tick box that, when the subproject is opened and synced to the main project, would take the subprojects main audio output and automatically route it to the track in the main project that the subproject audio resides on so effects and automation and routing are also heard.

This would then allow subprojects to be heard the same way when open for editing as they were when being played back simply as a "frozen" audio item.

We have a very old FR from the subprojects wishlist thread here that would really round out subprojects and make the more useful for music use.

https://forum.cockos.com/showthread....81#post1617081

It would make a lot of people use them more and be a big Reaper 7 feature for composers etc.

[Sexan]

Originally Posted by White Tie

There's a time and a place for theming feature requests, particularly these really fundamental ones that stretch back years. But given that we've only just got a rare major WALTER update, the custom elements, that we're supposed to be testing, that time is not now and that place is not here.

Was not a FR, was just saying. Anyway:

[White Tie]

Originally Posted by lucas_LCS

How close is this to being released?

The theme : very close. The theme adjuster : not close at all.

[OLSHALOM]

Originally Posted by cool

Good! I had to do some manipulations to make my script work without errors.

Just for information: since the new version of lua doesn't need randomseed, lines containing math.randomseed now throw an error. I just removed those lines.

Thanks for this one.
Could please someone with the privileges start a thread at its best place, where we could collect all these informations about Lua 5.4.6?
As a sticky?

[vitalker]

Originally Posted by cool

Good! I had to do some manipulations to make my script work without errors.

Just for information: since the new version of lua doesn't need randomseed, lines containing math.randomseed now throw an error. I just removed those lines.

It means that your script won't work correctly with <7.0 versions.

[OLSHALOM]

Originally Posted by lexaproductions

Here are the incompatibilities:
https://www.lua.org/manual/5.4/manual.html#8
For example, the function:

io.lines

now return 4 parms.

Ah, uups, just saw this, but still...

[vitalker]

Originally Posted by OLSHALOM

Thanks for this one.
Could please someone with the privileges start a thread at its best place, where we could collect all these informations about Lua 5.4.6?
As a sticky?

I think the link lexaproductions posted mentions all the differences + whole Lua syntax.

https://www.lua.org/manual/5.4/manual.html

[Vagelis]

Originally Posted by dsyrock

v7.0pre3 - August 5 2023
[*]# Media item lanes: prevent edits on source lanes from affecting selected/grouped items on comp lane

Fixed!
So far I can't break it anymore

[Sexan]

Originally Posted by vitalker

It means that your script won't work correctly with <7.0 versions.

lua_ver = _VERSION

if lua_ver:match("5.4") then
   
end

maybe something like this for backward compatibility ?

[Vagelis]

When dropping areas on lane add area, depends on the zoom level.

[Vagelis]

Moving areas with RE in source lanes trims the rest areas even when there's an empty space in RE selection. Could this be improved a little more so that it trims them only when the areas overlap?

[X-Raym]

@vitalker
the fix can be made by checking reaper or lua version, and just make a condition to add math randomseed only if necessary. not deal breaker.


@olshalom
this only cause issue if the io.line return was inside brackets and even in this case it may not be an issue.


--
The main idea about Lua 5.4 is about 40% performance update (according to benchmark I linked in my FR thread), so I think this will be beneficial.
Just tested with Audio accessor, and it seems to be approx the case (on average). still not as fast as EEL for audio accessor but this is just a test exemple.

https://github.com/ReaTeam/ReaScript...%20samples.lua

For now the compatibility issue we found which need more work is the Mavriq Reaper extension with Lua Socket. Surely fixable though.

[OLSHALOM]

• + Tracks: fix lane button and track grouping indicator display on retina/hidpi when preference allows maximum vertical zoom greater than 100%
• + Tracks: if preference allows maximum vertical zoom greater than 100%, allow manually resizing tracks to greater than the screen height
• + Tracks: if track height is greater than screen height, mousewheel scroll on TCP scrolls by screen height
• + Tracks: set maximum vertical zoom to 250% for new users (previous default was 100%)

Smirk on my face on a sunday morning.

While there are really great scripters in this community, in my opinion it still would make sense to have some native actions for zooming.

Maybe something like:
- Set selected tracks to a lane height of "x" pixels

Or define sizes for three actions: small, medium, big?

???

[BartR]

About

+ ReaScript: update from Lua 5.3.5 to Lua 5.4.6 (this may affect existing ReaScripts)

can you please post a link where to find the differences? I'm more interested into
Deprecated
Obsoleted

[vitalker]

Originally Posted by Sexan

lua_ver = _VERSION

if lua_ver:match("5.4") then
   
end

maybe something like this for backward compatibility ?

Yes, maybe even checking whether lua_ver < 5.4 or >= 5.4

[vitalker]

Originally Posted by X-Raym

@vitalker
the fix can be made by checking reaper or lua version, and just make a condition to add math randomseed only if necessary. not deal breaker.

Of course, fortunately I am not using this function.

[vitalker]

Originally Posted by BartR

About

+ ReaScript: update from Lua 5.3.5 to Lua 5.4.6 (this may affect existing ReaScripts)

can you please post a link where to find the differences? I'm more interested into
Deprecated
Obsoleted

The link's been posted in this thread at least thrice.

[inthevoid]

Originally Posted by musicbynumbers

Audio from background projects
Please consider a feature for audio from background projects too.

This would really complement the new ‘video from background projects’ feature well for us film composers - and if it meant you could render the subproject with the background project’s audio, even more so. Would save a ton of additional routing & real-time printing to make the workflow viable for use.

[Vagelis]

Probably the last edge case for breaking the comp areas in source lanes and we're set to go!
It happens only when the adjacent areas are on the same lane. If their edges snap and we drag the edge of the item everything works ok, but when there's a gap between areas and doing the same, the area breaks with the crossfade.

[BartR]

for LUA I found something.

I hope "that's it"

https://lwn.net/Articles/826134/

[BartR]

Originally Posted by vitalker

The link's been posted in this thread at least thrice.

ok I was not reading all pages.
TLDR 🤣

[Sexan]

this is the reason why vertical zooming should be centered (these are new defaults 250%). Waveform goes off the screen

https://imgur.com/0nh5NO3

This is normal track zooming (lane is collapsed)

[Vagelis]

Could we please have this action added in the right click lane header menu? Love it, very useful.

"Tracks: Explode selected items on fixed lane tracks to one new track per lane"

[Phazma]

Originally Posted by dsyrock

v7.0pre3 - August 5 2023[*] * Includes feature branch: visual track spacers

I noticed that dragging to-be-inserted media onto spacers makes them jump to the bottom of the tracklist. Not very intuitive and visually distracting.



IMO spacers should not be considered in this situation and the spacer area should be seen as part of the track before or after it, or as new track area if that option is enabled, or if all that makes no sense just make it an invalid dragging destination.

Adding the media at the bottom of the tracklist can cause confusion, especially in bigger sessions where the bottom is not visible. If the user works in a rush and releases the mouse button, the media is not visible. The user might think that the item has not been added (because there is no new item anywhere near the dragging destination) and try again, just to later be surprised by an item that was added to the bottom unintentionally.

Originally Posted by dsyrock

v7.0pre3 - August 5 2023 [*]# TCP/EnvCP resize indicators: fix retina drawing

Ah that's how it was supposed to look! Don't mind it now. Was worried I'd have to get used to a line going through the middle of a track when hovering over the resize area, which I had considered a questionable design choice :P

Btw I hope you can still consider the idea I proposed on the last pre to add the feature to drag copies of tracks (including items/envelopes) when holding a modifier. It's just too handy to leave out, especially if we can do the same thing with spacers (unless adding it to tracks is much more complicated).

[eungang]

Originally Posted by Mercado_Negro

Thanks for this. How does a plug-in report this from a technical standpoint? I'm asking because most of my plug-ins are not reporting it: UAD and UADx, Softube, Empirical Labs, Vertigo Sound, Cytomic and iZotope just to name a few of them.

I'd like to add here that the only plugin maker's whose dynamics processors seem to report GR to Reaper's standard are Waves, FabFilter, Eventide (except Newfangled), Pulsar Audio, Black Rooster and 8 or so of the companies at Plugin Alliance (including the Vertigo VSC-2, interestingly).

If we could know what it means for plugins to report GR correctly, user's could request updates from plugin manufacturer's.