v7.0rc1 - September 23 2023 !!!

[Jae.Thomas]

v7.0rc1 - September 23 2023
* Includes feature branch: support up to 32 main toolbars, 16 MIDI toolbars
* Includes feature branch: MIDI CC vertical zoom/scroll
* Includes feature branch: optionally hide collapsed tracks within a folder
* Includes feature branch: export mouse modifiers as a script
* Includes feature branch: target individual fixed lanes when pasting media items
* 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: 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
+ API: preserve FXID (if unique to project) when pasting FX/importing track templates
+ Dynamic split: properly handle leading/trailing pad when splitting grouped tracks [p=2714123]
+ Menus: support customizing fixed lane controls context menu
# Media item lanes: fix pasting tracks containing comped MIDI lanes [p=2714225]
# Media item lanes: only snap comp area fadeout start to grid if the comp area contains a fadeable media item [p=2714280]

[STOP]

v7.0rc1 - September 23 2023

Changelog - Pre-Releases

Generated by X-Raym's REAPER ChangeLog to BBCode

[Jae.Thomas]

Originally Posted by STOP

v7.0rc1 - September 23 2023

Changelog - Pre-Releases

Generated by X-Raym's REAPER ChangeLog to BBCode

thanks, I used some other program to do it and didn't know how to add that

[mccrabney]

Originally Posted by schwa

Drawing a border around notes is configurable via the MIDI editor view/color notes menu, so maybe if the settings call for using the theme border for selected notes, we use the unselected track/item color for the selected note body, and if the settings do not call for using the theme border, we use the selected track/item color for the selected note body?

did this make it in? i'm still seeing tinting on selected color-by-track midi notes:

[schwa]

Originally Posted by mccrabney

did this make it in? i'm still seeing tinting on selected color-by-track midi notes:

No, still thinking about this. At present if you are coloring MIDI notes by track or media item, then selected notes will have the selected track/item color and unselected notes will have the unselected track/item color.

[Vagelis]

Originally Posted by Jae.Thomas

v7.0rc1 - September 23 2023

+ Menus: support customizing fixed lane controls context menu

Nice one, thanks a lot!

[mccrabney]

Originally Posted by schwa

No, still thinking about this. At present if you are coloring MIDI notes by track or media item, then selected notes will have the selected track/item color and unselected notes will have the unselected track/item color.

got it. it's been a while since i've done arrange screen theme tweaking and it's probably already possible to specify selection by outline alone, but that's the goal here, in both Arrange and the MIDI editor (edit, yes just checked and you can do it by editing item_bg_sel.png)

my track colors are intended to convey unchanging categorical information about the contents of the track. when those colors get changed due to selection status, i lose the context of the color i chose, and if i'm using nearby similar colors (a few shades of blue for different octaves of a string section), the selection tint may make one colored track/item's object look like another. this is especially problematic when working in the MIDI editor and viewing/editing MIDI notes from other tracks.

[gofer]

I am with mccrabney in that I‘d much prefer the body color stays the same and selection is indicated only with the border changing color. I like to be able to identify my tracks via color which is why I designed my theme to not change track/item colors with selection. As of now eg. selected bassoon notes (darker green) look like they are coming from the flute track (brighter green).

The only problem I can see is that for non-editable items the midi editor doesn‘t show any borders on notes, so note selection will be invisible there. But they aren‘t editable anyway, so it may not matter?

[elcalen]

I'm still seeing this bug. Ending drag while the mouse is on top of the track being dragged changes folder depth, even though it clearly shouldn't.

[Justin]

Originally Posted by elcalen

I'm still seeing this bug. Ending drag while the mouse is on top of the track being dragged changes folder depth, even though it clearly shouldn't.

ah yes, ancient behavior... fixing!

[IXix]

RC1?!! Bloody hell, that was quick!

[Edgemeal]

Minor thing mentioned in Pre2, still there,
Bypass track envelope, label displays "(bypasse"

Win10_x64
https://stash.reaper.fm/47144/0803pr...pe%20label.png

[MonkeyBars]

+ MIDI editor: when switching active MIDI item, adjust vertical scroll if all notes would be offscreen

This commit from pre21 is cool and works! However, on first open, MIDI items don't open vertically scrolled to show the notes contents, which I consider a bug. Proper UX would be to run this "vertical scroll to contents function" on first MIDI item open too.

[deeb]

Pitch changes are not listenable while we are dragging. Would be much better if you could hear while dragging.



Thanks!

[YuriOl]

Indicator peaks are not displayed when the option "Theme has interlaced VU meters" is activated.
Will this be fixed?

[deeb]

Originally Posted by Justin

ah yes, ancient behavior... fixing!

since you are at this maybe you can check this. It is for SWS but still from the world of reaper.



Otherwise is missleading. In the end of the GIf is what would be desired.

Thanks!

[Justin]

Originally Posted by YuriOl

Indicator peaks are not displayed when the option "Theme has interlaced VU meters" is activated.
Will this be fixed?

for default7 you mean? yeah, fixing that.

[Justin]

Originally Posted by deeb

since you are at this maybe you can check this. It is for SWS but still from the world of reaper.



Otherwise is missleading. In the end of the GIf is what would be desired.

Thanks!

what you're saying is, a child track whose parent folder is hidden should be viewed as a top-level track and not indented? not sure if that's a good idea, we'll think about it at some point but not in RC land

[deeb]

Originally Posted by Justin

what you're saying is, a child track whose parent folder is hidden should be viewed as a top-level track and not indented? not sure if that's a good idea, we'll think about it at some point but not in RC land

Of course Justin, but that's it. Go go RC !

[Mercado_Negro]

Originally Posted by Justin

what you're saying is, a child track whose parent folder is hidden should be viewed as a top-level track and not indented? not sure if that's a good idea, we'll think about it at some point but not in RC land

Justin, could you please consider this?

https://forum.cockos.com/showpost.ph...9&postcount=23

I think it's not a good idea to put a new track inside a folder if this folder is fully collapsed (hidden children).

[VZStudios]

The new GR gain reduction function does not work from Pre11 to current, in the Pre10 version it still worked.

[sockmonkey72]

Would you consider fixing up this TCP redraw issue pre-v7? Thanks!

[Edgemeal]

Originally Posted by VZStudios

The new GR gain reduction function does not work from Pre11 to current, in the Pre10 version it still worked.

Seems OK here (Win10).

GR is not enabled by default, Select track and run action "Track: Display gain reduction in track meters for plug-ins that support it" (note the action is actually a toggle, kind of weird with multiple tracks selected as it doesn't toggle them individually, they all set to off or all on.)

Or right click track vu meter > Meters > Display gain reduction...

[akademie]

The layout of Reaper main window (arrange/mixer layout) is wrong by default after installation.
The mixer is almost invisible...
This is regression to v6.xx versions.


Reported already for v7.0pre24 (and older) here:

v7.0pre24 - September 16 2023

v7pre24 - wrong default arrange-mixer layout on lower screen resolutions

And it was confirmed that it is even on higher resolutions, like 1920x1080.

Screenshot:

[BartR]

Great RC1 I didn't expect so early however great achievement.

please just a question: is there any plan to add an API that can decode the content of the wildcards?

I mean suppose I have a wildcard called $isrc and the value is BECCD82300001 ... the PAI should just return the BECCD82300001 when we call it by giving $isrc ...

thanks and enjoy the week-end

[akademie]

Originally Posted by Jae.Thomas

v7.0rc1 - September 23 2023
+ Dynamic split: properly handle leading/trailing pad when splitting grouped tracks [p=2714123]

Well, now it DOES HANDLE the padding for grouped tracks, but the behavior is broken.
See screenshots pre and post split with the pads setting large enough to have items overlapped. (I switched to "Offset overlapping media items vertically" option to better see what's happening.)


(pre-split):


(post-split)!!!:


(dynamic split settings):


(grouping settings):



...and here is also test project attached...

INFO: If needed and/or requested, I can create BugReport just for this issue if it will not be possible to fix in current "rc" cycle.

.
EDIT_20230926: Fixed in following RC2 build

[Phazma]

Originally Posted by Jae.Thomas

+ Menus: support customizing fixed lane controls context menu

Nice, thanks for providing this.

Btw I know it's RC phase, but maybe can also allow customizing envelope control panel context menu? That one is irking me since a while as the one that can't be customized.

[mccrabney]

the lack of an ability to hide the TCP fixed lane selection controls is a major space hog, i have to change my ancient screensets in order to widen TCP to make room for it, at the cost of Arrange space

please, please give us an option to hide this somehow - i can manage it with actions and toolbars and can't afford the space it takes

[OLSHALOM]

Originally Posted by Vagelis

Nice one, thanks a lot!

+1

[mschnell]

I don't think that it's good to have no scale with the track meters as a default...

[Phazma]

Originally Posted by mccrabney

the lack of an ability to hide the TCP fixed lane selection controls is a major space hog, i have to change my ancient screensets in order to widen TCP to make room for it, at the cost of Arrange space

please, please give us an option to hide this somehow - i can manage it with actions and toolbars and can't afford the space it takes

That is likely a theme thing, in the theme I use the FL header area shows/hides based on available space:

Personally I wish there was a way to see the fixed lane header buttons without having to make space for the fixed lane header area. But I can't think of how that would be achievable. Early in development they didn't have a FL header part in the TCP but the buttons showed on top of tracks next to the TCP. I found that cool but the buttons need to be redrawn all the time during playback which apparently is bad for performance iirc.

[Phazma]

Originally Posted by krahosk

I agree; like "Options: preview note when inserting/editing", this is necessary for listening what we are doing in real-time.

I can agree we dragging a point. But when adjusting a curvature like in the screencap, what are you expecting to hear?

[OLSHALOM]

Originally Posted by Justin

for default7 you mean? yeah, fixing that.

Btw, it seems interlaced vu meters do not scale right for retina (14" MacbookPro 2021).

[Phazma]

I find it pretty confusing how the on/off state of collapsed lane buttons is displayed. Is this intentional?





I would expect it to show as "on" if at least one lane is playing.

[mccrabney]

Originally Posted by Phazma

That is likely a theme thing, in the theme I use the FL header area shows/hides based on available space:

nice, thanks for the gif. is there an up to date Walter anatomy showing the value that needs to be adjusted in order to control the collapse hierarchy?

[AZpercussion]

Devs, please, why we can't have the same peaks view with full lane/track heigth as on regular tracks?
It's useful to have already recorded items and peaks, that in progress, the same heigth to easy compare them, and at least to see anything, because now such thin line just useless.

[smandrap]

This issue is still present:





Also, i don't think the following behaviour is desirable when comping midi. I feel the crossfade thing shouldn't happen

[Loulou92]

I'm awful...

Would it be possible to have 48 main toolbars ? 32 is great don't get me wrong, but I know for a fact that I'll use them all by reaper 8... So while you're at it, & if it's not troublesome, why not make 48 main toolbars ?

Thanks
Awful Louis

[Phazma]

Originally Posted by mccrabney

nice, thanks for the gif. is there an up to date Walter anatomy showing the value that needs to be adjusted in order to control the collapse hierarchy?

This is how it (luckily) works by itself in the theme I use. White Tie evidently designed the default theme in a way that the buttons don’t hide as first element when the TCP gets small.
I don’t have time to dig around Walter or check the default theme adjuster now but if nobody else comes back to you I can give it a look when I have time.

[schwa]

Originally Posted by BartR

please just a question: is there any plan to add an API that can decode the content of the wildcards?

I mean suppose I have a wildcard called $isrc and the value is BECCD82300001 ... the PAI should just return the BECCD82300001 when we call it by giving $isrc ...

There is an existing function ResolveRenderPattern(), which will resolve global or project-level wildcards. For wildcards that cannot be resolved without more context (which part of the timeline? which media items?) you can use GetSetProjectInfo_String("RENDER_TARGETS") to get the resolved wildcards for the current RENDER_PATTERN. You can also use that function to set the render pattern, and/or use GetSetProjectInfo() to set up the render bounds.

If you have more questions about this please start another thread as it doesn't have anything to do with this release candidate build.