v6.79+dev0423 - April 23 2023

[Edgemeal]

v6.79+dev0423 - April 23 2023
* 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: 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
+ Actions: add action to explode items on fixed lane track to one new track per lane
+ Actions: add action to implode items across tracks to one fixed lane track
+ Command line: support -reascript parameter to run script immediately after opening project
+ Render: flush FX when normalizing audio during video render [t=278518]
+ Render: support $directory, $directory2, etc wildcards, representing the project directory parent (parent's parent, etc) on disk
+ Takes: changing active take via mouse affects grouped media items and tracks even if those tracks are hidden [t=278470]
+ Track manager: indicate tracks that have spacers above them
+ Track manager: support adding/removing track spacers
+ Track manager: when multiple contiguous tracks are selected, spacers will be added at the start and end of the set
# Media item lanes: fix track setting to automatically remove empty lanes not persisting after unrelated undo
# Mixer: fix mousewheel scroll when displaying track spacers

Full Changelog - Pre-Releases - Feature Requests - Generated by WhatsNew2

[Phazma]

Originally Posted by Edgemeal

v6.79+dev0423 - April 23 2023
+ Actions: add action to explode items on fixed lane track to one new track per lane
+ Actions: add action to implode items across tracks to one fixed lane track

Thanks, I was sure these would eventually come

Btw they seem to act on selected items instead of selected tracks. That feels a little fiddly to me. I would prefer if it exploded/imploded all items on the selected track.

------

Also, the implode action again shows some weird behavior. Apparently only if multiple tracks with lanes are present. No running scripts this time:




------

Originally Posted by Edgemeal

# Media item lanes: fix track setting to automatically remove empty lanes not persisting after unrelated undo

Thanks for the fix!

------

And btw another little request: can we have an option/action to hide the lane add area visibility (as does the collapse button on a single-lane track)?

I prefer to add lanes via actions/context menu and then add items to them, so the lane add area is mostly wasted space for me. I am sure I am not the only one to work like this?

[musicbynumbers]

This might be a known oversite rather than a new bug but hopefully it's not intended as it breaks using fixed lanes for sound design or layering samples on the same track when using lanes and track grouping.

issue
Fixed lane items that are not on the top (1st) fixed lane are not included in groups between tracks.
This is important if we want to use fixed lanes for other non comping uses in both music and sound design.

As an example of a use. I found this out because I was trying to use an empty midi item on the parent track as a "folder" for the child tracks using the group system and this works but falls apart when fixed lanes don't get included in the group and therefore, copied


reproduce
-Create 2 tracks

-make track one the lead and track two the the follower.

-Put a single 1 bar long midi item on track one.

-put 2 single bar long midi items on track two but use two fixed lanes with the 1st midi item on fixed lane 1 and the 2nd on fixed lane 2.


Expected outcome
Grabbing and moving the midi item on track one should also move both items on track two.

actual outcome
The 2nd midi item on track two, fixed lane 2 doesn't move at all and is not included in the group.



EDIT
Maybe we can have this as an optional tick box in group settings?

[Vagelis]

Originally Posted by Edgemeal

v6.79+dev0423 - April 23 2023
+ Actions: add action to explode items on fixed lane track to one new track per lane
+ Actions: add action to implode items across tracks to one fixed lane track

Cool features thanks! I would prefer though if a track is selected to implode items in this track, or it could create a new track to implode the items if no track is selected.

Bug:

[Vagelis]

Bug with undo

[bolgwrad]

Not a bug, but just a use case: the five BV tracks being imploded here were recorded in different fixed lanes, so they retain the various lane IDs - with the result that when they are imploded, the target lane track is irregularly arranged and needs a few more steps (at least 2 keyboard shortcuts to switch track modes) to get the desired result of five ordered fixed lanes. The desired neat & tidy result only happens when the imploded lane items originate from their respective lane 1, or the lane item to-be-imploded is moved to lane 1 in advance.
I wonder if there is any way of indicating an item's stored lane ID to forestall this, or forcing imploded lane items to respect their track order, rather than giving precedence to their original lane number.
Thanks.

[dangguidan]

Originally Posted by Edgemeal

+ Command line: support -reascript parameter to run script immediately after opening project

How is this new feature used?

[kytdkut]

Originally Posted by Edgemeal

v6.79+dev0423 - April 23 2023
+ Command line: support -reascript parameter to run script immediately after opening project

holy shit

[mschnell]

Seems VERY useful !
-Michael

[smandrap]

Originally Posted by Edgemeal

+ Command line: support -reascript parameter to run script immediately after opening project

Wait, does this mean that we can (for example) run the render queue at night automagically and have renders ready in the morning via bash script?

[nikolalkc]

This is HUGE!

[sockmonkey72]

Double-clicking on a spacer (in the arrangement, with a double-click action "Track: Insert New Track") always adds that track to the end of the track list, as opposed to after the last-selected track (as "Insert New Track" from the menu seems to do).

Is that intentional?

[schwa]

By design, double-clicking a track spacer, or right-clicking a spacer and choosing "insert new track", should insert the track immediately above the spacer.

[sockmonkey72]

Originally Posted by schwa

By design, double-clicking a track spacer, or right-clicking a spacer and choosing "insert new track", should insert the track immediately above the spacer.

That works as expected. It's the 'Track' MM context double-click action, as it applies to double-clicking on spacer space, or "empty" arranger view space, which is adding the track to the end of the track list.

[schwa]

Double-clicking empty track space does nothing by default, so you must have that customized?

[sockmonkey72]

Originally Posted by schwa

Double-clicking empty track space does nothing by default, so you must have that customized?

Yep, that's what I wrote in Post #12 above, but maybe it wasn't clear. The Track double-click action was changed (for testing this) to the built-in action "Track: Insert New Track".

[_Stevie_]

I'm trying the new $directory wildcard, but either I'm doing something wrong or it's not working as I hoped.

This is without any data in the file name field:



And this is with $directory2




I had hoped, we can completely replace the path by using $directory2, but apparently it get's added to the file name? Is that the intended behavior?

My goal would be to go up one directory (= "Album") where "Projects" and "Export" sit and render to the Export directory.

[schwa]

Originally Posted by _Stevie_

I'm trying the new $directory wildcard, but either I'm doing something wrong or it's not working as I hoped.

If your project file is C:\artist\album\song.RPP, and you are rendering to C:\renders\, then wildcards will resolve like this:

$directory => C:\renders\album.wav
$directory2 => C:\renders\artist.wav
$directory2-$directory => C:\renders\artist-album.wav
$directory2-$directory-$project => C:\renders\artist-album-song.wav

[Fergler]

Visual track spacer is cool, are there going to be right click actions for adding them though? Couldn't find anywhere except action list - is this correct?

For FX containers, seems they're likely going to have a lot of space where the preset dropdown is. Might be a good use of some of it to have a Container name text box for quickly renaming them so we don't have to bring up the modal from right click.

https://i.imgur.com/vdXXohJ.png

And maybe move the UI button to the left so all those buttons can be vertically justified for my OCD?

[vitalker]

Originally Posted by Fergler

Visual track spacer is cool, are there going to be right click actions for adding them though? Couldn't find anywhere except action list - is this correct?

https://i.imgur.com/vdXXohJ.png

Since they are track-related, you should check context menu of tracks (first position).

Your wet knobs look broken. Like their image file lost transparency.

[Funkybot]

Originally Posted by Fergler

Visual track spacer is cool, are there going to be right click actions for adding them though? Couldn't find anywhere except action list - is this correct?

For now, just customize your menus to add them. I created a Track Separator sub-menu in the TCP menu, with various separator options.

[_Stevie_]

Originally Posted by schwa

If your project file is C:\artist\album\song.RPP, and you are rendering to C:\renders\, then wildcards will resolve like this:

$directory => C:\renders\album.wav
$directory2 => C:\renders\artist.wav
$directory2-$directory => C:\renders\artist-album.wav
$directory2-$directory-$project => C:\renders\artist-album-song.wav

I see, so this wildcard is only intended to work for filenames.
I had somewhat hoped this would improve the following situation:



Here I'm using \..\ to go up one directory, but as you can see "Render to" does not reflect that change, instead it just writes out the \..\.
The render itself goes to the right directory, but there is no way to check beforehand.
Can you think of any way to improve that situation?

[schwa]

Originally Posted by Fergler

Visual track spacer is cool, are there going to be right click actions for adding them though? Couldn't find anywhere except action list - is this correct?

Actions to manage spacers are in the default TCP right-click menu. If you don't see them, it's because you previously customized this menu.

[Meo-Ada Mespotine]

Wouldn't it be more logical to make the new wildcards accepted by the directory-field as well?

Edit: maybe even full wildcard support for directories. So you could render todays state of the project in a dedicated directory.
For instance "render all regions into a directory with today's date for easier versioning".

[Klangfarben]

Originally Posted by Meo-Ada Mespotine

Wouldn't it be more logical to make the new wildcards accepted by the directory-field as well?

+1 It doesn't really make sense to have the wildcards work in the file name field and not the directory field. And not just the new ones. $Project/randomfolder/ etc. which works fine in the file name field should work in the directory field as well.

[Edgemeal]

+ Actions: add action to explode items on fixed lane track to one new track per lane

Could the new tracks be auto named to where the items came from?, Something like "Lane C2" , "Track 1 Lane 1", "Lane C1 (Tr3 Drums)" ?
FWIW I made a script to do this 1-2 weeks ago so no big deal if not added, I just thought it would be nice for the native action to identify where the items came from. Thanks for considering.