v6.73+dev0102 - January 2 2023

[vitalker]

v6.73+dev0102 - January 2 2023

• * Includes feature branch: routing matrix/track wiring input activity indicators
• * Includes feature branch: preview item selection for grouped tracks
• * Includes feature branch: VST3 per-channel silence reporting compatibility option
• * Includes feature branch: better .RfxChain media explorer and clipboard integration
• * Includes feature branch: ReaReaRea timestretch mode
• * Includes feature branch: GR metering as embedded UI for third-party VSTs
• * Includes feature branch: JSFX new features and EEL2 preprocessor
• * Includes feature branch: render dialog statistics display improvements
• * Includes feature branch: selected media item appearance changes
• * Includes feature branch: media item fixed lanes
• + Color theme: add theme elements for razor edit area fill/outline in fixed-lane tracks
• + IDEs: improve autocomplete behavior when using EEL2 namespaces [t=274334]
• + Media item lanes: add controls to razor edits on fixed lane tracks to move area without contents, copy contents to first playing lane
• + Media item lanes: when razor edit areas exist on fixed-lane tracks, play only the media within the razor edit area
• + Preferences: fix searching when starting from plug-in registered preferences page [t=274326]
• + Razor edits: fix restoring master track razor edits on project load
• + Track routing menu: improve keyboard navigation/screen reader behavior for sends
• + Track routing menu: improve screen reader behavior for hardware output list
• + Undo: consolidate undo points when inserting multiple FX via action [t=274365]
• + Windows: reduce flicker in actions window
• # Media item lanes: always allow editing the top/bottom edge of razor edits on fixed lane tracks
• # Media item lanes: improve lane header button hit testing [p=2629798]
• # Media item lanes: optimize some processing to only occur after media item edits on fixed-lane tracks
• # Razor edit: fix action to create automation item within razor edit on master track
• # Razor edit: fix undo when moving razor edits containing media items across tracks
• # Razor edits: fix pasting to play rate envelope when razor edit spans multiple tracks [p=2629769]

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

[vitalker]

Originally Posted by vitalker

+ Media item lanes: when razor edit areas exist on fixed-lane tracks, play only the media within the razor edit area

Now we should push it to the limit!
We need non-contiguous playback/render based on razor edits. Non-contiguous not only in time, but also in tracks.

[vitalker]

Originally Posted by vitalker

Now we should push it to the limit!
We need non-contiguous playback/render based on razor edits. Non-contiguous not only in time, but also in tracks.

Also freezing/locking razor edits makes even more sense since now.

[Mercado_Negro]

I think having two or more lanes playing simultaneously when razor edit areas are superposed is not something desired. The last razor edit area should delete part of a previous razor edit area and play only that.

[ferropop]

This is nice and approximates the "cycle takes" in classic Reaper comping.

When committing to top lane, I don't think the Razor Area should move TO the top lane. It should stay where it was, as you are focused on the material AT the RE.

[ovnis]

Originally Posted by ferropop

This is nice and approximates the "cycle takes" in classic Reaper comping.

When committing to top lane, I don't think the Razor Area should move TO the top lane. It should stay where it was, as you are focused on the material AT the RE.

+1000 Faster and logic.

[schwa]

FWIW here is an example of using the new razor edit preview to choose between multiple recording passes:

[ferropop]

What's the workflow intention here?

ie,

1. Make a track
2. Set it to Fixed Lanes
3. Record Arm
4. Record multiple passes
5. Make a RE to listen to a section

All good so far.

6. Commit to Top Lane, or First Playing lane?

The "Top Lane" can't be assumed to be a "comp" lane, it just happens to be the first recording pass.

The "First Play Lane" can't be assumed to be a "comp" lane either, it just happens to be your last recording pass.


...so do we have to first create an empty "top lane" and remember to keep it as a dedicated "comp" lane? Is that level of freedom (ie lack of rigidity) really a good idea?

I'm comparing this to classic comping which enforces a functional "active take" workflow. I can see this behaving wildly if you don't super carefully plan to not destroy your takes.

[Mercado_Negro]

Originally Posted by schwa

FWIW here is an example of using the new razor edit preview to choose between multiple recording passes:

This is great, schwa. I tested it a few minutes ago and it works nicely that way. Now, what I see that's counterproductive is having two or more razor edit areas on two or more different lanes playing at the same time like this:



I think only the latest created razor edit area should delete the previous and play.

[vitalker]

Originally Posted by vitalker

Now we should push it to the limit!
We need non-contiguous playback/render based on razor edits. Non-contiguous not only in time, but also in tracks.

And I was not talking about only fixed-laned tracks.

[ovnis]

Originally Posted by vitalker

Now we should push it to the limit!
We need non-contiguous playback/render based on razor edits. Non-contiguous not only in time, but also in tracks.

If I have well understood: on a regular track, only the area which is inside the razor edit is played (with a specific mouse modifier)?



It could be great!

[Vagelis]

Originally Posted by vitalker

v6.73+dev0102 - January 2 2023[*]+ Media item lanes: when razor edit areas exist on fixed-lane tracks, play only the media within the razor edit area

Thanks for this but i feel it's a half baked feature. Can you please give us the same functionality with previous markers where everything outside them was muted but for razor edits in lanes?

I have a couple of items in lanes and i choose some parts of it. When it's playing the parts without razor edits i can hear all items in lanes which is not very relative to comping.

I don't want to solo a lane each time we comp with razor edits, i would prefer if all lanes become automatically muted when razor edits exists and play only those parts.

[Kenny Gioia]

Originally Posted by Vagelis

Thanks for this but i feel it's a half baked feature. Can you please give us the same functionality with previous markers where everything outside them was muted but for razor edits in lanes?

I have a couple of items in lanes and i choose some parts of it. When it's playing the parts without razor edits i can hear all items in lanes which is not very relative to comping.

I think you already have this if you don't solo any lanes.

[Vagelis]

Originally Posted by Kenny Gioia

I think you already have this if you don't solo any lanes.

How? In order to comp I have to solo at least one lane.

Also another problem regarding REs and comping, if i make multiple comps which is the most common thing, how can i move just the one of them if i want to change it during playback?

[mccrabney]

edit, nvm, this is unchanged and just a result of vertical zoom focusing on track under mouse instead of an unmoving target.

regarding the new zoom behavior, here's a gif showing some jerky movement that occurs if you zoom out vertically to shrink all tracks, and then continue to scroll out. once you hit the minimum, the tracks "shake" as you continue to scroll.



compare to 6.64, where the same over-scrolling does not cause the screen to shake.

[mccrabney]

scratch that, sorry. this is just what happens when you have the vertical zoom set to "track under mouse"

[Justin]

Originally Posted by mccrabney

edit, nvm, this is unchanged and just a result of vertical zoom focusing on track under mouse instead of an unmoving target.

regarding the new zoom behavior, here's a gif showing some jerky movement that occurs if you zoom out vertically to shrink all tracks, and then continue to scroll out. once you hit the minimum, the tracks "shake" as you continue to scroll.

by "continue to scroll" do you mean continue to zoom, or switching from zoom to scroll once you've zoomed all the way out?

[souk21]

Originally Posted by vitalker

[*]+ IDEs: improve autocomplete behavior when using EEL2 namespaces [t=274334]

Thanks

+ IDE/gfx.getchar: more international keyboard support tweaks for Windows (will probably break things)

About this, I wanted to let you know that there are multiple reports of scripts breaking.
I came across these: Quick Adder, Build Your Own Toolbar, Key Sequences

The bugs seem related to gfx_getchar and possibly the JS_API as well.
I can't reproduce on OSX but I'll try to pinpoint it for key sequences on Windows asap

[Vagelis]

Also can we have a top master lane dedicated for comping that would always show/add automatically the sum of all razor edits in lanes and which it could be hidden at any time, including an option to collapse the rest lanes and show only the master top lane?

Edit: Maybe would be easier and more simple if we could change to comping mode when we show this top lane and when we hide it lanes would work only for layering?

[vitalker]

Originally Posted by Vagelis

Also can we have a top master lane dedicated for comping that would always show/add automatically the sum of all razor edits in lanes and which it could be hidden at any time, including an option to collapse the rest lanes and show only the master top lane?

It would make sense, if we were able to freeze/lock razor edits, because now you can accidentally change it and your comps are gone.

[vitalker]

Originally Posted by Vagelis

Edit: Maybe would be easier and more simple if we could change to comping mode when we show this top lane and when we hide it lanes would work only for layering?

Yes, it should be different somehow than normal lanes.

[Vagelis]

Originally Posted by vitalker

Yes, it should be different somehow than normal lanes.

Yes I strongly believe that, We can't have both layering and comping at the same time, so this could be a way to separate them and let us work the way we want. Right now i feel they interfere with each other and comping gets less than layering.

[Triode]

Conversely, I'm used to organising Pro Tools sessions and in that DAW the first lane doesn't have any special status. Since we can label and create new lanes after initial layering, I'd be happy to comp to a labeled comp lane as is.

I'm open to other options if they occur but a "special status comping lane" could be limiting in other ways depending on how it's implemented.

[cfillion]

+ Preferences: fix searching when starting from plug-in registered preferences page [t=274326]

Thank you!

[Embass]

[Vagelis]

Another problem i've noticed when comping with razor edits, is that when i make a selection e.g to the first lane and then a second selection to the second lane that's overlapping with the first one, RE automatically selects both lanes and when we commit the result we get overlapped items.
I would prefer to automatically move the edges of the selections when they overlap so it gets selected only one lane when this happens. Just like the first implementation of play markers. Maybe all these could be solved with a dedicated comping tool that could act that way.

[Embass]

[Embass]

[Embass]

[Mercado_Negro]

Originally Posted by Vagelis

Another problem i've noticed when comping with razor edits, is that when i make a selection e.g to the first lane and then a second selection to the second lane that's overlapping with the first one, RE automatically selects both lanes and when we commit the result we get overlapped items.
I would prefer to automatically move the edges of the selections when they overlap so it gets selected only one lane when this happens. Just like the first implementation of play markers. Maybe all these could be solved with a dedicated comping tool that could act that way.

This is exactly what I was suggesting because it doesn't make any sense to have two or more razor edit areas playing at the same time.

[vitalker]

Originally Posted by Mercado_Negro

This is exactly what I was suggesting because it doesn't make any sense to have two or more razor edit areas playing at the same time.

They make sense, but not in context of comping.

[Mercado_Negro]

Originally Posted by vitalker

They make sense, but not in context of comping.

I think comping is the goal here, no?

[vitalker]

Originally Posted by vitalker

+ IDEs: improve autocomplete behavior when using EEL2 namespaces [t=274334]

Would be also great to have independent shortcuts for saving and running code in IDE.

[MonkeyBars]

Originally Posted by vitalker

[*]+ Undo: consolidate undo points when inserting multiple FX via action [t=274365]

Works perfectly now, thanks for the fix!

[Embass]

[Embass]

[Thunderfinger]

Originally Posted by vitalker

[*]+ Media item lanes: add controls to razor edits on fixed lane tracks to move area without contents, copy contents to first playing lane

The new "copy area contents to first playing fixed lane" action is a great addition to my type of workflow. Copying to a specific lane allows for easy custom actions to repeat the same tasks quickly.

Request: Could we get a toggle to only display the soloed lane? When I'm done comping, I don't need to see all of the item lanes anymore, I only want to see my comp.

2nd request: Could we get actions to solo next/previous lane, and first/last lane? It would give more options to focus the correct lane in custom actions without having to click.

[BartR]

Originally Posted by vitalker

+ Windows: reduce flicker in actions window

This worked. Thanks a zillion

[nofish]

Originally Posted by vitalker

v6.73+dev0102 - January 2 2023[*]+ Media item lanes: add controls to razor edits on fixed lane tracks to move area without contents, copy contents to first playing lane

I know it's very early days (but so maybe a good time to mention it), I hope this new comping system eventually also gets useable for when not all recording passes are necessarily the same length (i.e. non beat-based music).
That's were the old takes comping totally falls short with the auto-splits imo.

I'm thinking if we could not just copy vertically but additionally set a destination point where it should be copied (edit: in time) (aka source destination editing) we'd be quite close already.

[ferropop]

Hoping this can be retained from current comping :

Cycling takes (or areas of takes) in a collapsed state.

It's easy in current Reaper because there's no comp lane, and the take borders are splits, so you just run the actions and it cycles the selected items even if collapsed.

The corollary might be to Swipe a RE on an area of the collapsed lane, and the cycle actions would (internally) "cycle the area up/down a lane and comp it to top".

This would operate very much like the current (very fast and desirable) functionality.