v7.0pre9 - August 17 2023

[sockmonkey72]

v7.0pre9 - August 17 2023

• * 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: 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
• + Envelopes: do not change envelope height when resizing tracks with mouse
• + Mixer: improve click descriptions for send context menu
• + Tracks: if max vertical zoom preference is 100% or less, keep the focused track entirely onscreen while zooming
• # Envelopes: allow setting envelope zoom preference to 0% of track height (so envelopes are not affected by vertical zoom)
• # Media item lanes: fix crash when mouse is near lane-collapse button [p=2701981]
• # Media item lanes: handle customized mouse modifiers properly when handling mouse click in comping source lanes outside of existing comp areas [p=2702246]
• # Media item lanes: if track setting to play only last recorded lane is disabled, new loop recording does not change existing lane playback but also plays the last recorded lane [p=2702073]
• # Media item lanes: improve stability of comp lane syncing

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

[smandrap]

Originally Posted by sockmonkey72

[*]+ Envelopes: do not change envelope height when resizing tracks with mouse

Great!!
However this is still happening:

Originally Posted by smandrap

If Maximum vertical zoom is less than 100% the action "View: Toggle track zoom to maximum height of arrange view" doesn't toggle between maximum zoom/previous zoom.



"View: Toggle track zoom to maximum height (even if not 100% of arrange view)" goes from minimum height -> default height -> maximum height. Is this intended?

[deeb]

+ Envelopes: do not change envelope height when resizing tracks with mouse

it works when in 0%. Great!

[Vagelis]

Originally Posted by sockmonkey72

v7.0pre9 - August 17 2023
[*]# Media item lanes: improve stability of comp lane syncing

Bug with fades:

[deeb]

+ Tracks: if max vertical zoom preference is 100% or less, keep the focused track entirely onscreen while zooming

works great so far !

edit: this detail could maybe be optimised: when zooming a track with header already out of view maybe zooming could happen to the down direction only (and scroll if necessary) .. maybe to much tho..

[Vagelis]

Bug with move contents in comp lane:

[Vagelis]

Items disappear in the comp lane while splitting a source, then moving the source is moving with the comp area.

[Vagelis]

How much sense does it make to move comp areas with the adjacent edges attached in the comp lane?
This is super dangerous because 1) we can't see what's going on and we just want to move the comps separately most of the times without comping random stuff, 2) we can't even unstick them from the cursor! This works with other modifiers but not with this one which is a huge bummer and makes things so complicated for such a simple thing.

[ferropop]

Thanks schwa, sync seems more stable esp with duplicated items.

I noticed this:



While this might be purely aesthetic, notice the ARA Pool indicators sort of randomly appear/disappear depending on what is selected. Just thought I'd send, both because I'm assuming this is a bug aesthetically, but also because it might point to something more going on tied to yesterday's behaviours.

[Vagelis]

Some weird behavior with updating the comp lane and undo:

[deeb]

# Media item lanes: if track setting to play only last recorded lane is disabled, new loop recording does not change existing lane playback but also plays the last recorded lane [p=2702073]


still there is no way to do this AFAICS:

empty Fixed Lanes -> record 3 cycles (cycle1, cycle2 and cycle3) and play last cycle (cycle3)

record again 3 cycles in same track (cycle4, cycle5 and cycle6) and keep last cycle and previous recorded one (cycle3 + cycle6)

[Vagelis]

It would be nice if there was some improvement with RE and comp areas in the comp lane when all lanes are visible.
Moving a piece of the comp area in comp lane it unsyncs the whole area. It would be much better if it could add split points to the edges of RE on the comp area and unsync only that part instead of the whole area.

[Funkybot]

Did the Do not animate toolbar buttons preference recently break? I'm still getting the radar effect on the mouse modifier override buttons even with it off. Or am I looking at the wrong preference for that?

EDIT: disregard. The correct setting is under the Customize Toolbar section by right clicking the action. Thanks Edgemeal!

[schwa]

Originally Posted by ferropop

While this might be purely aesthetic, notice the ARA Pool indicators sort of randomly appear/disappear depending on what is selected. Just thought I'd send, both because I'm assuming this is a bug aesthetically, but also because it might point to something more going on tied to yesterday's behaviours.

Thanks, fixing.

[Edgemeal]

Originally Posted by Funkybot

Did the Do not animate toolbar buttons preference recently break? I'm still getting the radar effect on the mouse modifier override buttons even with it off. Or am I looking at the wrong preference for that?

IIRC that option is just for armed action.
To disable toolbar animation > Customize toolbar > right click action > Highlight animation settings

[Phazma]

Originally Posted by sockmonkey72

[*]+ Envelopes: do not change envelope height when resizing tracks with mouse

Envelope zooming/resizing is perfect now. Thanks!

[FeedTheCat]

Originally Posted by sockmonkey72

* Includes feature branch: visual track spacers

When you click in the empty TCP area to insert a track/template, the track/template is not added into the empty TCP area. Instead it gets added below the last focused track.

Not sure if this is new, but now that we have have track spacers it would be nice if the behavior was consistent (and logical).

[schwa]

Originally Posted by deeb

empty Fixed Lanes -> record 3 cycles (cycle1, cycle2 and cycle3) and play last cycle (cycle3)

record again 3 cycles in same track (cycle4, cycle5 and cycle6) and keep last cycle and previous recorded one (cycle3 + cycle6)

I believe that is what happens if the setting "after recording into a new lane, play only that lane" is disabled (it's enabled in your screencap).

The behavior is not easily explained in a menu item description, but this is what is supposed to happen:

Originally Posted by schwa

Setting enabled (default): after new recording, only the last recorded lane plays.

Setting disabled: after new recording, any previously existing lanes that were playing are unchanged. The last recorded lane *in that recording pass* also plays.

[Fabian]

I loaded into R7pre9 the theme I use in R6, and then I loaded an old project, and in R7 the track colors are lost:

R6:


R7:

(Click the images to view larger)

Is this as it should be?

EDIT: This is on W10, BTW

[vitalker]

Originally Posted by Fabian

I loaded into R7pre9 the theme I use in R6, and then I loaded an old project, and in R7 the track colors are lost:

R6:


R7:

(Click the images to view larger)

Is this as it should be?

No, they both look like v4-alpha theme.

[Funkybot]

Originally Posted by Edgemeal

IIRC that option is just for armed action.
To disable toolbar animation > Customize toolbar > right click action > Highlight animation settings

Thank you! I knew it was somewhere and thought I might have the wrong preference.

[Fabian]

Originally Posted by vitalker

No, they both look like v4-alpha theme.

Yes, it is the same theme, tweaked by me, and I have been using it since... forever (probably since v4, yes). It works fine in R6, but as you see the track colors are lost in R7.

Old themes are not supposed to work in R7, is that what you say?

[vitalker]

Originally Posted by Fabian

Old themes are not supposed to work in R7, is that what you say?

Ah, sorry. No, they should work. By the way, I have the same "issue" with v4 theme in 6.81 (track panels have default color).

[Fabian]

Preferences > Appearance > Track Control Panels > Tint track panel backgrounds have to be checked.

Originally Posted by vitalker

Ah, sorry. No, they should work. By the way, I have the same "issue" with v4 theme in 6.81 (track panels have default color).

Maybe checking the box to tint track panel backgrounds solves that for you also.

[schwa]

Originally Posted by deeb

I know schwa I am just telling this is still not possible.

Argh, yes, it's not working as intended if the track has never been recorded into. This is the intended behavior:

[deeb]

^^
Yes yes!

Originally Posted by schwa

The behavior is not easily explained in a menu item description:

If this setting does what you showed on the last gif you posted then maybe you can name it “layering” or “overdubing” on/off

[vitalker]

Originally Posted by Fabian

Maybe checking the box to tint track panel backgrounds solves that for you also.

Thanks, looks like my mod is just broken.

[Vagelis]

Originally Posted by schwa

Argh, yes, it's not working as intended if the track has never been recorded into. This is the intended behavior:

Hmmm, I tried to record some midi and audio for layering with this method and what I don't like is that you have to be precise and stop before the loop, because then the lane won't be audible since the full pass gets muted and the last audible pass is not at full length.
Or, is it still possible as previously to record only audible lanes for layering?

[schwa]

That's usually what this preference is used for:

[Vagelis]

Originally Posted by schwa

That's usually what this preference is used for:

So I guess I have to stop it on each pass in order to stay audible. Ok, thanks!

[deeb]

schwa, can you make available Media Takes as recording method? maybe experimental? for comping maybe can go in both directions or conflict or give extra power, or simply is a user preference, maybe having media takes helps having better and more filtered comping material between several recordings, .. i don't know.

but For layering is the best - no doubt (IMO).

And since RE Tool now exists maybe some constrains about adicional modifiers that contributed at that time to not include them in Fixed Lanes by default don't exist anymore. Just wondering and asking to consider. Thanks

[schwa]

If you choose "record into lane", then loop recording will create takes in that lane. You could then enable "play all takes" or choose individual takes, just as if the lane were a regular track. Not sure if that's what you're talking about.

[akademie]

"Do not process muted tracks" option stopped working in later pre- and dev- releases.
Muted tracks still consume CPU!

Bug Report here:
Do not process muted tracks STOPPED WORKING

EDIT 20230819:
and new thread with more tresting and revealation:
REAPER Pre-Release Discussion > Do not process muted tracks STOPPED WORKING

[deeb]

Originally Posted by schwa

If you choose "record into lane", then loop recording will create takes in that lane. You could then enable "play all takes" or choose individual takes, just as if the lane were a regular track. Not sure if that's what you're talking about.

what you saying is vey good but for layering no, specially since layering most of the times is your self doing it with an instrument in your hands and maybe away form the computer (remote). If for every time you record a new layer (Overdubbing) you need to take your hands from the instrument and go to the computer and use hands for setting a new layer for recording is not musical friendly.

What i am saying is having the option to have default recording with Classic Media Takes and not just takes has is now.

the difference is with default recording media takes we have this steps:

- pick instrument
- start record with a keyboard key/ or remote
- play instrument
- stop with space key / or remote
- start record with a keyboard key/ or remote
- play instrument
- stop with space key / or remote
- start record with a keyboard key/ or remote
- play instrument
- stop with space key / or remote


and we have 3 layers organised with Classic Takes.

has you saying - totally remote not possible and we have this steps to achieve the same:

- Leave hands from instrument
- add empty lane with mouse
- set lane for record with mouse
- start record with a keyboard key
- pick instrument
- play instrument
- stop with space key or remote
- Leave hands from instrument
- add empty lane with mouse
- set lane for record with mouse
- start record with a keyboard key
- pick instrument
- play instrument
- stop with space key or remote
- Leave hands from instrument
- add empty lane with mouse
- set lane for record with mouse
- start record with a keyboard key
- pick instrument
- play instrument
- stop with space key or remote

It's not musical friendly for someone recording midi keyboard or an instrument by him self, while the other way around is a joy .. it's fun to use, invites us to use.

[musicbynumbers]

Originally Posted by akademie

"Do not process muted tracks" option stopped working in later pre- and dev- releases.
Muted tracks still consume CPU!

Bug Report here:
Do not process muted tracks STOPPED WORKING

Ah, that might be why I got crackles on a large orchestra template where most of it is muted most of the time and is normally ok.

I'll have to check that tomorrow

[schwa]

I don't really understand what you are saying, sorry.

In a fixed lane track, if you record multiple passes as you have described, each will be in its own lane and by default only the last recording pass will play back. If you disable "after recording, play only that lane", then all lanes will play back.

In a regular track, if you record multiple passes as you have described, each will be a separate take and by default only the last take will play back. If you set the item to "all takes play", then all takes will play back.

It sounds like what you want maybe is to have loop recording in a fixed lane track create a new lane, but record multiple passes into takes on that lane? If so I will call that out of scope for now. There will be plenty of time during the v7 cycle for all kinds of feature additions and improvements.

[deeb]

Originally Posted by schwa

I don't really understand what you are saying, sorry.

In a fixed lane track, if you record multiple passes as you have described, each will be in its own lane and by default only the last recording pass will play back. If you disable "after recording, play only that lane", then all lanes will play back.

It's ok! sorry also for not being the best at comunication sometimes.

Originally Posted by schwa

In a regular track, if you record multiple passes as you have described, each will be a separate take and by default only the last take will play back. If you set the item to "all takes play", then all takes will play back.

yes , that is what happens, actually i had a fixed idea that we could do it in FIP the way i described , which we can't either. Thanks for pointing

Originally Posted by schwa

It sounds like what you want maybe is to have loop recording in a fixed lane track create a new lane, but record multiple passes into takes on that lane?

yes i think you got it right. it is exactly That.

Originally Posted by schwa

If so I will call that out of scope for now. There will be plenty of time during the v7 cycle for all kinds of feature additions and improvements.

Ok! take your time and make good use of your good time for the things with priority. I think this will be very beneficial and fun for many people so i am convicted at the right time it will probably be implemented. Thank you very much for taking your time to clear this one for me as it means a lot to me. ufff!

[Funkybot]

Originally Posted by schwa

I don't really understand what you are saying, sorry.

In a fixed lane track, if you record multiple passes as you have described, each will be in its own lane and by default only the last recording pass will play back. If you disable "after recording, play only that lane", then all lanes will play back.

From what I can tell, if one wants layering to work with fixed item lanes, where each pass is it's own lane, but all prior passes are audible, you need to:

1. Set "Track Properties: Fixed Item Lanes"
2. Ensure "Monitor track media when recording" is on
3. Run the action "Track: After recording into a new lane, play only that lane"

Note: the "Track: After recording into a new lane, play only that lane" action 1) doesn't report it's state (would be nice if I knew if it was enabled or disabled), and 2) here seems to be in an "on" state by default. I have to run the action to make all lanes play. Based on the way it's worded, I'd expect the opposite.

My steps, in case there's a bug:

1. Drag a drum VSTi to a new track in the TCP
2. Set a 4 measure loop, and enable looping
3. Set "Track Properties: Fixed Item Lanes"
4. Ensure "Monitor track media when recording" is on
5. Record a hat pass
6. Record a kick pass
7. Record a snare pass

Result: only the current pass and the prior pass are heard, by pass 3 the hat is no longer audible.

Expected Result: all passes are audible.

Ok so something isn't right...

8. Delete all 3 passes
9. Run the action "Track: After recording into a new lane, play only that lane"
10. Record a hat pass
11. Record a kick pass
12. Record a snare pass

Result: now I'm hearing everything as expected.

Is that how this is intended to work?

[deeb]

Originally Posted by Funkybot

Is that how this is intended to work?

Originally Posted by schwa

Argh, yes, it's not working as intended if the track has never been recorded into. This is the intended behavior:

there is a fix for that coming. schwa refer to it earlier in this thread.

that response is a feed back about my porpose to be able to record Classic Media Takes (full of individual takes and ready to be selected the best) per lane by default (or as an option), which in my opinion is perfect at least for layering.

like this 💛:

[daxliniere]

@Justin, not sure if you intended it to, but this release does not fix the Windows Manifest crash bug.