v6.78+dev0324 - March 24 2023

[Vagelis]

v6.78+dev0324 - March 24 2023

• * Includes feature branch: configurable naming for in-project MIDI items
• * 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: fixed lane comping
• * Includes feature branch: shortcut import/export improvements and multiple main keyboard sections
• * Includes feature branch: preview item selection for grouped tracks
• * Includes feature branch: GR metering as embedded UI for third-party VSTs
• * Includes feature branch: media item fixed lanes
• + Hardware outputs: improve quality when muting/unmuting tracks that have hardware outputs
• + Media explorer: add actions to edit metadata tags
• + Media item lanes: double-click unsynced comp area indicator to copy unsynced area to new lane and re-comp
• + Sends: apply mute fades to post-fader sends when muting/unmuting tracks
• + Super8: add optional per-channel fadeout of configurable loop-length multiple [t=275137]
• + Super8: avoid small glitch when stopping the last channel
• + Super8: fix quirky behavior when the same CC is used to record multiple channels [t=260223]
• + Super8: improve quality and performance of reverse function [p=2646530]
• + Super8: use linear fades when starting/stopping playback
• + Terminology: update various Pre-FX labels to be 'Pre-Fader (Pre-FX)'
• + Track record settings menu: separate output recording latency compensation option from channel modes
• # FX containers: fix duplicate menu displays
• # Media item lanes: don't adjust unsynced comp area edges when editing media item edges
• # Media item lanes: don't move edit cursor when changing comp area source lane
• # Media item lanes: fix comp area edges sometimes not moving with media item edges [p=2662258]
• # Media item lanes: prevent moving media items when switching comp source lane [p=2662258]
• # Sends: fix slight glitch with pre-fader sends surviving mute
• # Windows: update manifest to support Windows 8.1 features
• # macOS: fix menu items for custom actions/scripts/etc

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

[Vagelis]

[*]# Media item lanes: don't adjust unsynced comp area edges when editing media item edges

Yay, thanks a lot Schwa, now it's way more safe to edit in comping lane

But I still find a bit tedious to unsync an area so we could move it without the source, because it needs to move an item first to unsync.
Sometimes we just want to move the unsynced area without previously moving the item to unsync. Could there be a better way like to add to the right click menu an action to unsync, or with double click on the area in comping lane? (maybe should be added in double click context)

[Vagelis]

Also I guess the reports regarding RE and comp areas are not fixed in this pre.

[schwa]

Originally Posted by Vagelis

Also I guess the reports regarding RE and comp areas are not fixed in this pre.

No, we haven't gotten around to polishing the razor edit interaction yet.

[ovnis]

bug: "offset overlapping media items" doesn't work.



- On a track where 2 items are overlaped with offset, I set the track on "fixed lane"

- I uncheck "fixed lane"
-> The 2 items are not offest anymore (bug).

[benmiller]

Originally Posted by ovnis

bug: "offset overlapping media items" doesn't work.



- On a track where 2 items are overlaped with offset, I set the track on "fixed lane"

- I uncheck "fixed lane"
-> The 2 items are not offest anymore (bug).

i think that's to be expected as you lose info when switching out of fixed lane.

Fixed lanes are not really intended to be switched on and off too much. If you are in fixed lanes mode and make use of multiples lanes, then that track should stay in fixed lane mode.

[Vagelis]

Originally Posted by schwa

No, we haven't gotten around to polishing the razor edit interaction yet.

Ok! Overall the existing pre feels very very good so far <3

[FeedTheCat]

Originally Posted by Vagelis

Ok! Overall the existing pre feels very very good so far <3

My thoughts exactly. Thanks schwa!

[tonalstates]

Originally Posted by Vagelis

# Media item lanes: don't move edit cursor when changing comp area source lane

Thank you for that!

[FeedTheCat]

Originally Posted by Vagelis

# Media item lanes: don't adjust unsynced comp area edges when editing media item edges

Perfect! I think this is the way to go

Don't know if there's an elegant solution, but there are 2 situations where this creates unwanted gaps when interacting with synced areas.

1. When you grab 2 items edges at once (1 unsynced/ 1 synced)
2. When you crossfade an unsynced area into a synced area.



Not the biggest of deals, as you can get the desired behavior by:

1. Grabbing the comp areas directly
2. Doing it the other way round (crossfade synced into unsynced).

Just thought I'd post in case there's a sensical way to avoid them.

[Aikido123]

As of at least the last two DEV releases (323 and 324) MIDI Step Input is not working for me. F1-F12 input does work, but not from the keyboard. Switching back to the last full release (678) it does work - everything else being equal.

[Justin]

Originally Posted by Aikido123

As of at least the last two DEV releases (323 and 324) MIDI Step Input is not working for me. F1-F12 input does work, but not from the keyboard. Switching back to the last full release (678) it does work - everything else being equal.

thanks, will look into this!

[Mercado_Negro]

+ Sends: apply mute fades to post-fader sends when muting/unmuting tracks

Thanks for this!

[FeedTheCat]

Was thinking about this potential simplification lately:

From a user perspective, what is the difference between an unsynced comp area and no comp area?

• You can see unsynced areas and you can switch by single click.
• You can't see non-existing areas but you can switch by double click.

So what if we made the entire comp lane look like a large unsynced comp area by default?

(synced areas in this mockup are green)



You can split this large area wherever you want. When a comp area unsyncs it leaves behind split points. You would never get gaps between areas, just split points.

What do you guys think? Does it make sense? Would it simplify or complicate things?

I'm not 100% convinced btw, just an interesting thought imo.

[lexaproductions]

Originally Posted by vitalker

[*]+ Sends: add options to have sends, hardware outputs unaffected by mute/solo[/list]

Can somebody tell me how to revert this? I tried to click/unclick the item in the preferences but now when I solo a track, my sends (to the loopback bus) are always on.

[Justin]

Originally Posted by lexaproductions

Can somebody tell me how to revert this? I tried to click/unclick the item in the preferences but now when I solo a track, my sends (to the loopback bus) are always on.

If you have a configuration that behaves differently than 6.78 with those options not enabled, post a minimal .rpp, thanks!

[Vagelis]

Originally Posted by FeedTheCat

Was thinking about this potential simplification lately:

From a user perspective, what is the difference between an unsynced comp area and no comp area?

• You can see unsynced areas and you can switch by single click.
• You can't see non-existing areas but you can switch by double click.

So what if we made the entire comp lane look like a large unsynced comp area by default?

(synced areas in this mockup are green)



You can split this large area wherever you want. When a comp area unsyncs it leaves behind split points. You would never get gaps between areas, just split points.

What do you guys think? Does it make sense? Would it simplify or complicate things?

I'm not 100% convinced btw, just an interesting thought imo.

Gaps are necessary sometimes imo, especially when we want to move an unsynced area to a place where we removed an area previously. I think now it's safe like this because it's pretty clear where the synced comp areas are and we can't mess it with unsynced areas easily while editing or comping accidentally above them.

[Daodan]

+ Media item lanes: double-click unsynced comp area indicator to copy unsynced area to new lane and re-comp