v6.51+dev0311 - March 11 2022

STOP · 03-11-2022, 12:02 PM

v6.51+dev0311 - March 11 2022

* Includes feature branch: media explorer pitch detection
* Includes feature branch: media explorer user-defined tags
* Includes feature branch: improved peak building
* Includes feature branch: FX chain oversampling
* Includes feature branch: media item fixed lanes
+ Media explorer: improve keyboard accessibility of toolbar on Windows
# Import: improve preview display somewhat
# Media item lanes: move lane header controls back to TCP area
# Media item lanes: respect preference to align TCP controls when fixed lane header controls are displayed

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

benf · 03-11-2022, 01:18 PM

Quote:

Originally Posted by STOP

[*] * Includes feature branch: media explorer user-defined tags

Don't know the purpose of this.
Is it possible to modify that box so we can add columns that permits to modify existing Metadata tags like ID3:APIC_FILE (title image) or ID3_TEXT (lyricist)... ?

Vagelis · 03-11-2022, 03:26 PM

With lane numbers visible on TCP, i think it would look better if the space below numbers had the same color with the right side of TCP, and if it was thinner horizontally like so:

ovnis · 03-11-2022, 04:03 PM

Quote:

# Media item lanes: move lane header controls back to TCP area

An option would be great (header controls in the TCP area or out).

PitchSlap · 03-11-2022, 05:24 PM

Thanks for fixing the issue with the ghosted item preview not being time-stretched. The accuracy of placing items is much better

When dragging an item to the timeline there can still be a discrepancy between the cursor and snapping where the ghosted item shows it being placed beside the existing item, but if the cursor accidentally overlaps it asks to replace. Not a huge deal, just pointing it out in case it wasn't intended.

When choosing overlap in the dialog the items are placed beside each other with no overlap based on the snapping so it seems a bit quirky.
https://forum.cockos.com/showthread.php?t=184239

Pink Wool · 03-11-2022, 08:17 PM

What @PitchSlap said about items "colliding" + 1!

sockmonkey72 · 03-12-2022, 12:24 AM

Bumping this to make sure it's seen:

There's a keyboard regression in the +dev version versus 6.51 on macOS.

* new project
* new track
* open FX window
* add FX dialog
* navigate to a plugin (with mouse or keyboard)
* press return

in 6.51 and earlier, this would instantiate the plugin. In this dev version, it does not.

Maybe related to this in v6.51+dev0307?

Quote:

[*] + macOS: improve return-key behavior with third-party plug-in text entry fields

bolgwrad · 03-12-2022, 05:13 AM

The media lane tabs make more sense in the TCP, but my graphical gripes:

1. The track icon (if used) is between the main controls and the tab - I think the track icon should be on the outermost edge. On R/H TCP display, the tabs are way across on the far side.

2. The tabs IMHO are screaming to be buttons.

Valle · 03-12-2022, 06:05 AM

(Re: dry render/calculate statistics)

AAAARGH!

When did the columns for LUFS-I and LUFS-M swap?

I just now realized. But for how long have I read "M" instead of "I"?

(When exported to browser, it looks like before. That is, "I" is the last column. But in the render dialog, "M" is the last.)

schwa · 03-12-2022, 06:10 AM

Prior to +dev0304, only one LUFS calculation would be displayed in the render output window, preferentially LUFS-I. +dev0304 added an option to not display RMS in the render results window. If that option is enabled, the slot where RMS was previously displayed instead might display LUFS-M depending on what statistics are actually being calculated.

We can change this so the order is always the same as in the browser view, even if the specific displayed columns are different.

bolgwrad · 03-12-2022, 06:28 AM

With the default 6 theme; obv the icon can't go on the outermost edge.

ovnis · 03-12-2022, 08:26 AM

Quote:

Originally Posted by bolgwrad

The media lane tabs make more sense in the TCP

Why?

ovnis · 03-12-2022, 09:17 AM

When lanes tabs are inside TCP, it's less space for plug-ins slots, AUX or plug-ins controls. Less space for TCP buttons. When media lane tabs are outside TCP it doesn't eat usefull space and it's more easy to know what is the number of the fixed lane (because tabs are closer lanes).

Vagelis · 03-12-2022, 09:26 AM

Quote:

Originally Posted by ovnis

Why?

I think i prefer too how the numbers were previously visible on track.
Some other idea is to show the lanes in a folder like this.
So what happens here is that when fixed lanes is on, the item on track is moved to the first lane below with the lane adder visible too. On main track it's visible the sum of all items from lanes with a faint color

xpander · 03-12-2022, 10:03 AM

Quote:

Originally Posted by Vagelis

So what happens here is that when fixed lanes is on, the item on track is moved to the first lane below with the lane adder visible too. On main track it's visible the sum of all items from lanes with a faint color

Two problems with that approach.
1. It takes away from the idea of having fixed item lanes within an individual track.
2. Visually it looks (and behaves) like folder tracks do. Add some real folder tracks and you'll get a confusing mix of the two.

---

Quote:

Originally Posted by bolgwrad

With the default 6 theme; obv the icon can't go on the outermost edge.

I don't think track icons should go to the outer edge in any theme, where fixed item lanes are used. To me track icons serve the function of being visual indicators of the track contents. In contrast, the fixed item lane controls are tied to the features of the individual lanes, so should be as they already are, as close to them as possible.

Unfortunately these ideals fall apart anyway, if TCP is shown on the right side of arrange. But that is another issue for another day, I reckon.

sockmonkey72 · 03-12-2022, 10:05 AM

Looks like the latest dev version isn't notarized (needs a right-click -> manual Open... or xattr removal to run).

Vagelis · 03-12-2022, 10:21 AM

Quote:

Originally Posted by xpander

Two problems with that approach.
1. It takes away from the idea of having separate take lanes within an individual track.
2. Visually it looks (and behaves) like folder tracks do. Add some real folder tracks and you'll get a confusing mix of the two.

1. But they 're still attached to each track separately, they 're just shown inside a folder.

2.I don't think this could be a problem if the color of the lanes is different than track color. Also each lane doesn't have all TCP controls to be confused with tracks in a folder, they will have a number as indicator.

It can have many advantages too though. Like it would be possible to change the size of each lane individually to work cleaner or focus better on the lane you want.

Easily hide the folder lanes and move or edit all items as you want from the main track.

It could be useful later for comping too, for example we could start comping on lanes, and then edit the comping parts from the sum on main track.

No need to take space from other TCP elements.

xpander · 03-12-2022, 10:27 AM

You are describing features which are already there with folder tracks. So what would be the benefit of fixed item lanes for you then?

Vagelis · 03-12-2022, 10:37 AM

Quote:

Originally Posted by xpander

You are describing features which are already there with folder tracks. So what would be the benefit of fixed item lanes for you then?

But folder lanes will not have the same features with folder tracks but the same features with existing media lanes.
The next feature i'm waiting for to be added to fixed lanes is comping. I mentioned above some advantages about this when will be implemented.
Track folder behavior is very different and can be used to group tracks and send fx to all of them and other things than what lanes are meant to be used for.
Folder lanes will still have the same behavior with the existing one, with the lane add area below to add or remove lanes.

xpander · 03-12-2022, 10:59 AM

Well, for the take comping I can surely see the benefit of having a "master" track where the selected parts would be displayed. Then again, fixed lane tracks can already be put into folders to get the visual aspect.

tohubohu · 03-12-2022, 11:40 AM

Quote:

Originally Posted by Vagelis

I think i prefer too how the numbers were previously visible on track.

+ 1000

bolgwrad · 03-12-2022, 11:44 AM

Quote:

Originally Posted by ovnis

Why?

If you look at my second (default theme) graphic, where I've put lane buttons next to the track solo/mute buttons, there's tons of space for lane mute/solo/routing - even lane routing something like the plugin routing pinout, for example. It looks neat, while tabs don't match anything.

I do like the lane tabs as status flags, but not to have a whole set of lane controls in a submenu.

ferropop · 03-12-2022, 11:53 AM

Quote:

Originally Posted by STOP

v6.51+dev0311 - March 11 2022[*]# Import: improve preview display somewhat

Current implementation of dragging-to-new-track and the in-between visual works and looks great, thank u devs.

ovnis · 03-12-2022, 12:31 PM

Quote:

Originally Posted by bolgwrad

If you look at my second (default theme) graphic, where I've put lane buttons next to the track solo/mute buttons, there's tons of space for lane mute/solo/routing - even lane routing something like the plugin routing pinout, for example. It looks neat, while tabs don't match anything.

I do like the lane tabs as status flags, but not to have a whole set of lane controls in a submenu.

With lane tabs inside TCP, in lots of cases/theme, we lost space for lots of elements.

But I don't understand why you don't like when lane tabs are outside TCP. Tabs controls can be outstide the TCP without a submenu... And it can have more space than tabs inside TCP.

Justin · 03-12-2022, 12:54 PM

Quote:

Originally Posted by sockmonkey72

Bumping this to make sure it's seen:

There's a keyboard regression in the +dev version versus 6.51 on macOS.

* new project
* new track
* open FX window
* add FX dialog
* navigate to a plugin (with mouse or keyboard)
* press return

in 6.51 and earlier, this would instantiate the plugin. In this dev version, it does not.

Maybe related to this in v6.51+dev0307?

Thanks, fixing!

bolgwrad · 03-12-2022, 04:08 PM

Quote:

Originally Posted by ovnis

With lane tabs inside TCP, in lots of cases/theme, we lost space for lots of elements.

But I don't understand why you don't like when lane tabs are outside TCP. Tabs controls can be outstide the TCP without a submenu... And it can have more space than tabs inside TCP.

I don't mind lane tabs outside TCP. Will discuss in lane forum in future.