v6.78+dev0322 - March 22 2023

[vitalker]

v6.78+dev0322 - March 22 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
• + Audio device channel naming/mapping: allow mapping ReaRoute/loopback devices as regular channels
• + Localization: improve localization of default audio device channel names
• + Loopback: add audio loopback support (Preferences/Audio) for up to 256 channels
• + Sends: add options to have sends, hardware outputs unaffected by mute/solo
• # Media item lanes: add action to copy unsynced comp area to new lane to comp area context menu
• # Media item lanes: edit comp area fades by editing media item fades directly in comp lane
• # Media item lanes: lots of internal changes
• # Media item lanes: prevent cluttering undo history when syncing comp areas
• # Media item lanes: simplify comp area appearance and editing

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]

The right click menu for comp areas has been removed in this pre?

Edit: It's there, but i had to restart reaper and then i could see it.

[ferropop]

Split Comp Area (ignoring snap) still not working as a Ctrl-LClick. Behaviour started in the last pre.

the With Snap version works.

[ferropop]

"Copy Unsynced Comp Areas to New Lane and ReComp for Track Under Mouse" not working as Shift-Ctrl-LClick MM, and also stopped working yesterday.

Tried remapping modifiers, no difference.


I'm specifying my mappings in case that adds a clue, but it doesn't matter what modifier combo I use.

[mykrobinson]

What means this?


* Includes feature branch: updated Windows manifest for newer OS features

[Klangfarben]

+ Loopback: add audio loopback support (Preferences/Audio) for up to 256 channels

For the idiots in the back (me) how does this differ from the 512 loopback audio channels we can already add in the reaper.ini?

+ Audio device channel naming/mapping: allow mapping ReaRoute/loopback devices as regular channels

Also for idiots that need an EL5 (again, me...) what does this mean exactly?

[ferropop]

But yeah these last couple pres have not been usable in a recording session because so many useful actions stopped working. Just me?

[Vagelis]

When I drop an area in lane add area, in the new lane the item height changes to the full height of the lane, which to me looks also nice

Maybe it would be nice to have an option in preferences, to see the full height of the items while editing like this? It's still possible to create an area at the bottom of the item.

[FeedTheCat]

Originally Posted by vitalker

# Media item lanes: lots of internal changes

What have you done schwa!

Let's take a minute and appreciate this beauty

[Vagelis]

Items in comping lane should move independently from comp areas, else it's easy to break them.

[vitalker]

Originally Posted by mykrobinson

What means this?


* Includes feature branch: updated Windows manifest for newer OS features

As I already asked this question in one of the previous threads, here are the answers (TLDR - nothing):

Originally Posted by Edgemeal

If manifest is working correctly then end user shouldn't notice anything different. You can see the reaper.exe manifest using Resource Hacker if at all interested, but unless you're a dev it will likely not make any sense, it basically the same thing you see here.

Originally Posted by Justin

Yep, this change was to improve compatibility for certain plugins, hopefully there will be no other noticeable change

[vitalker]

Originally Posted by vitalker

* Includes feature branch: FX containers

Context menus called from a container still can be closed only after second click.

[Vagelis]

Stretching comp areas with RE is still pretty buggy

[schwa]

Originally Posted by Vagelis

The right click menu for comp areas has been removed in this pre?

Seems to be working fine here? What behavior are you seeing exactly?

[Vagelis]

Originally Posted by schwa

Seems to be working fine here? What behavior are you seeing exactly?

Just edited my post before see your reply.

Previously opened the normal right click menu.

[Vagelis]

Originally Posted by FeedTheCat

What have you done schwa!

Let's take a minute and appreciate this beauty

Yes it's there, ready and pretty polished, I think we 're getting closer to the final touches <3

[Vagelis]

Hmm now it heals the splits in comp areas while moving the item in comping lane

[schwa]

Originally Posted by ferropop

Split Comp Area (ignoring snap) still not working as a Ctrl-LClick. Behaviour started in the last pre.

the With Snap version works.

Fixing along with some related bugs. A few things like this got overlooked for a couple of builds while we were changing some internals.

[Funkybot]

Originally Posted by mykrobinson

What means this?


* Includes feature branch: updated Windows manifest for newer OS features

Should just mean slightly better plugin compatibility on Windows 11 and nothing else. Justin indicated it should be pretty transparent.

[schwa]

Originally Posted by ferropop

"Copy Unsynced Comp Areas to New Lane and ReComp for Track Under Mouse" not working

Fixing this, and adding it as a native mouse modifier too.

[musicbynumbers]

+ Loopback: add audio loopback support (Preferences/Audio) for up to 256 channels

Very exciting stuff! Nervously hoping this is leading to the automatic routing for openly editing subprojects!

[FeedTheCat]

So much has changed, so much to unpack...
Here are the first things I noticed:

Trimming only works from the right (intentional?):



Splitting an item currently just trims the existing comp area.
Would be very handy if it would create new areas for the split parts:

[Vagelis]

Originally Posted by ferropop

Split Comp Area (ignoring snap) still not working as a Ctrl-LClick. Behaviour started in the last pre.

the With Snap version works.

Split an area on grid doesn't work in comping lane though.

[FeedTheCat]

Edge case:

[Vagelis]

Using RE with items in fixed lanes always copy the item instead of moving it.

[Justin]

Originally Posted by Klangfarben

For the idiots in the back (me) how does this differ from the 512 loopback audio channels we can already add in the reaper.ini?

It doesn't collide with ReaRoute, and you can use both at once...

Also for idiots that need an EL5 (again, me...) what does this mean exactly?

You can remap those channels to be interleaved in with your audio interface channels.

[BirdBird]

Some things I couldn't find/figure out how to do while using the media item lanes:

• Recording new material on a new lane under comp lane (for recording new material towards the comp lane rather than away from it)
• Action to clear all comp areas
• Quick way to solo the comp lane (maybe a mouse modifier on lane buttons or an action?)
• Mouse modifier to create comp lane area, remove area after mouse release while keeping the propagated item (for promoting items to the comp without any areas)

Some nitpicks:

• Moving comp areas do not respect "Snap relative to grid" setting in snap preferences
• The toolbar button for enabling/disabling mouse overrides for drawing comp areas behaves as its separate from track lane state, hovewer, disabling this toggle also puts all tracks out of comp mode (easy to accidentally hit)
• Duplicating a razor edit selection empty with space into a comp area on the comp lane sometimes does not remove empty space

For the sake of those of us that would like to use something dumber, but simpler with media item lanes, any chance we could get preferences to:

• Remove the center dot
• Disable automatic change of lane state when recording new material
• Disable automatic propagation of new items when recording and there is an active comp lane (don't touch existing areas)
• Hide all comp areas on comp lane

My apologies if some of the above already exist and I couldn't find them.

[Vagelis]

I don't know why, but other than a better crossfade feature in this pre, everything else felt and looked better in previous pre. For me it was almost perfect.

Btw is there any change on the brightness of the comp areas in this pre? Or is it me that the colors of the comped items looked better previously?

dev0321:

[Jae.Thomas]

Originally Posted by musicbynumbers

+ Loopback: add audio loopback support (Preferences/Audio) for up to 256 channels

Very exciting stuff! Nervously hoping this is leading to the automatic routing for openly editing subprojects!

what would this mean, to "openly" edit subprojects? I can edit them already?


sounds intriguing

[Vagelis]

Also dev0321 had the best behavior in comping lane. Everything was predictable. We could move the items independently of areas, or we could move the area with or without the item source.



I don't find the existing behavior in comping lane more flexible or predictable than the above gif.

[FeedTheCat]

Originally Posted by Vagelis

I don't know why, but other than a better crossfade feature in this pre, everything else felt and looked better in previous pre. For me it was almost perfect.

Btw is there any change on the brightness of the comp areas in this pre? Or is it me that the colors of the comped items looked better previously?

Lots of internal changes usually break a ton of stuff, wouldn't worry too much about it.

Also seems to me like the area color changed. It's a bit more brown or smth.

[Vagelis]

Originally Posted by FeedTheCat

Lots of internal changes usually break a ton of stuff, wouldn't worry too much about it.

Also seems to me like the area color changed. It's a bit more brown or smth.

I just hope we get the behavior as my gif above in comping lane, together with the existing crossfade. Because editing is not predictable now.

And the colors of previous pre, was perfect.

[musicbynumbers]

Originally Posted by Jae.Thomas

what would this mean, to "openly" edit subprojects? I can edit them already?


sounds intriguing

It would hopefully mean that if you open a subproject from the main project (double clicking on the subproject item etc),

If you then go into the subproject tab and press play.. Instead of the synced subproject coming out of it's own master output (and therefore bypassing any effects, automation and level changes you have done to it in the main project)..

it would instead use these loopback channels automatically behind the scenes to route the subproject back to it's main project output and act as if it's properly mixed instead of just being "raw" out of it's own separate non related master output.

This would make an absolute massive difference to how useful subprojects are

[Jae.Thomas]

Originally Posted by musicbynumbers

It would hopefully mean that if you open a subproject from the main project (double clicking on the subproject item etc),

If you then go into the subproject tab and press play.. Instead of the synced subproject coming out of it's own master output (and therefore bypassing any effects, automation and level changes you have done to it in the main project)..

it would instead use these loopback channels automatically behind the scenes to route the subproject back to it's main project output and act as if it's properly mixed instead of just being "raw" out of it's own separate non related master output.

This would make an absolute massive difference to how useful subprojects are

but then it would actually negate any performance benefits of using subprojects but it would be more a workflow thing? Obviously it would be an option so it wouldn't hurt anything but

[lexaproductions]

Originally Posted by Justin

You can remap those channels to be interleaved in with your audio interface channels.

1- But if I make an alias on one channel, the tracks that was assigned to the channel are not assigned to the alias?
I don't understand the need to have both the alias and the original channel in the Routing Matrix?
2- Also, should be able to alias a stereo pair? Right now we must alias both L-R channels and only then, it will appear as a pair in the Routing Matrix Window. Aren't we polluting the view if we want to setup only stereo busses?

[musicbynumbers]

+ Audio device channel naming/mapping: allow mapping ReaRoute/loopback devices as regular channels

I was just trying this as a test with subprojects to see how easy it might be to set what I mentioned above as a script..

.. I couldn't get loopback to work though, either on the subproject master output or on a folder hardware out and then arming the track back in the main project with the loopback selected or on a new track.

Maybe, when playing back from the subproject it blocks these things?

Either way, hopefully it won't matter at some point anyway but thought I'd mention it as it seems like it's not working for me between projects yet.

[Mercado_Negro]

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

This is great

[Vagelis]

Originally Posted by musicbynumbers

It would hopefully mean that if you open a subproject from the main project (double clicking on the subproject item etc),

If you then go into the subproject tab and press play.. Instead of the synced subproject coming out of it's own master output (and therefore bypassing any effects, automation and level changes you have done to it in the main project)..

it would instead use these loopback channels automatically behind the scenes to route the subproject back to it's main project output and act as if it's properly mixed instead of just being "raw" out of it's own separate non related master output.

This would make an absolute massive difference to how useful subprojects are

sounds amazing, does this also means that we won't have to save the subproject to get the sound in main project as it's going to pass by automatically? If so damn then we need a way to dock a subproject bellow the main and have it as a second view for many many things.

[Thonex]

Originally Posted by FeedTheCat

What have you done schwa!

Let's take a minute and appreciate this beauty

AGREED!!

Very nicely done Devs!!

[musicbynumbers]

Originally Posted by Jae.Thomas

but then it would actually negate any performance benefits of using subprojects but it would be more a workflow thing? Obviously it would be an option so it wouldn't hurt anything but

The subprojects would still be bounced down (not taking resources) and acting as they do now but when you double click it, and it opens in a new tab. Instead of hearing that subproject out of context when playing it back synced to the main project.

The only difference would be that you now hear the subproject synced to the main project but routed back through the track it came from so you can actually hear it correctly mixed.

The subprojects are only live still when open.

Right click on the project tab area if you haven't found this great feature yet and enable "synchronize any parent projects on playback" and also "run background projects" as that might make what I'm talking about make more sense).


I use subprojects for 3 main things and this would make all of them better.

1. to bounce down very complex clusters of tracks cut from the main project and converted to a subproject into something that takes up very little resources like drums or complex dolby atmos routings (yes it supports multichannel)

2. For film work whereby the subprojects will be whole complex music pieces or sfx work from shared projects on say google drive.

3. complex sound effects in game sound whereby I can create the sound once inside of a subproject but sync the same sound multiple times to a video of the game (in the main project) but only have to edit the one subproject to change all of them.


all of these would benefit from having the live subprojects routed to their correct main project tracks