v7.36+dev0413 - April 13 2025

[matt_t]

v7.36+dev0413 - April 13 2025

• * Includes feature branch: TCP toolbar
• * Includes feature branch: pin tracks in TCP
• * Includes feature branch: region editing preview display changes
• * Includes feature branch: region/marker lanes
• * Includes feature branch: parallel render via master
• * Includes feature branch: multithreaded render postprocessing
• * Includes feature branch: render all selected items or razor edit areas as a single file
• * Includes feature branch: MIDI item reconfiguration on effective timebase change
• * Includes feature branch: phase alignment dialog
• * Includes feature branch: graphical crossfade editor
• * Includes feature branch: playback support for rendered files
• * Includes feature branch: trim leading/trailing silence when rendering
• + Big clock: allow minimum size to be smaller, especially when docked
• + MIDI editor: improve painting note behavior with visually-reduced grid
• + MIDI editor: improve snapping in source beats view
• + MIDI editor: insert notes follows visible grid preference if inserting grid size
• + Region/Marker Manager: fix checkbox theme display [p=2859852]
• + Wildcards: fix $markername/$regionname wildcards
• + Wildcards: fix '$markernumber[N]' and '$regionnumber[N]' when no previous marker/region exists
• # Region/marker manager: display default lane color if set and marker does not have custom color set
• # Track pinning: fix vertical zoom when only the master track is pinned

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

[7thresonance]

Region names are buggy in MIDI Editor. Only the first region's Name is being shown in ME.





Hopefully, have region lanes in MIDI editor as well?

As well as Region lane APIs for scripts?

[FeedTheCat]

I noticed 2 bugs:

1. Peaks are not built after recording:



2. GetTrackFromPoint stops returning valid lane info when you scroll down:

local track, track_info = reaper.GetTrackFromPoint(x, y)
local lane = track_info >> 8

(About GIF: I'm using GetTrackFromPoint in a script that changes how lane buttons are soloed based on layer recording mode. Once you scroll down a bit the returned lane is always 0 which results in lane 1 always being selected)

[7thresonance]

Pinned tracks dont obey Track height lock.

While track height locked, unpinned tracks (which were pinned beofre) dont obey until, untick and tick track height lock again.

[FeedTheCat]

Originally Posted by matt_t

+ Big clock: allow minimum size to be smaller, especially when docked

If it could become a bit smaller, one could now dock it above a master track on the side.

[RobinGShore]

# Region/marker manager: display default lane color if set and marker does not have custom color set

Thanks, this is working well. Could the colored border for markers that don't have a custom color be a little thicker, so that the coloring is more obvious?

[thommazk]

+ MIDI editor: improve snapping in source beats view

On a related note, snapping while moving a MIDI note feels a bit inconsistent. In the GIF, the visible grid doesn't seem to be fully taken into account when determining the mouse position, regardless of the view mode. It looks like it's using the mouse position from the moment you click and hold, rather than the clicked grid itself.

+ MIDI editor: insert notes follows visible grid

Thanks for the improvement! On a related note, could we have a Mouse Modifier option to insert notes that set the length to the visible grid?

The main issue is that when "Drawing or selecting a note sets the new note length" is enabled, you lose that level of control. Personally, I'd love to have a modifier that lets me insert a note based on the visible grid, and another that uses the length of the last selected note.

[vicnest]

This series of Midi improvements, trying to paint or changing MIDI CC event lane feels better. It used to be very hard to paint 0 without clicking the scroll bar below.

[Funkybot]

Originally Posted by 7thresonance

Region names are buggy in MIDI Editor. Only the first region's Name is being shown in ME.

It's not just regions. Same thing happens with Markers in the ME. Only the first named one appears. See below where I was using markers as a pseudo-chord track and regions for the song sections:

[7thresonance]

Originally Posted by Funkybot

It's not just regions. Same thing happens with Markers in the ME. Only the first named one appears. See below where I was using markers as a pseudo-chord track and regions for the song sections:

yeah...

[PhelixK]

# Track pinning: fix vertical zoom when only the master track is pinned

It's fine now, TY!

[Daodan]

Originally Posted by RobinGShore

Thanks, this is working well. Could the colored border for markers that don't have a custom color be a little thicker, so that the coloring is more obvious?

Also I suggest to change marker edge and text color in default theme to neutral like in previous theme or make it follow marker color. Current red works well only for red (default in 7 theme) markers and for other colors it's a bit ugly.

[7thresonance]

idk if its too late to mention this. the 3 dots on the big clock plus. I think it should fade away when not interacting with it.

Can get a clean clock

[Phazma]

Originally Posted by matt_t

v7.36+dev0413 - April 13 2025
[*]+ MIDI editor: improve painting note behavior with visually-reduced grid
[*]+ MIDI editor: improve snapping in source beats view
[*]+ MIDI editor: insert notes follows visible grid preference if inserting grid size

I am a little late, but along with these changes would it be possible to have an option for setting the minimum pixels between grid lines for the MIDI editor, just as we can for the arrange view?

I often would like to zoom out to see the bigger picture while editing and yet be able to do fine edits to the grid, but there are not enough visible grid lines. If I could set a smaller minimum pixel value I could do the same edits more efficiently to the grid without having to zoom in just to see the grid.

Also the changes from +dev0412 regarding dragging tracks into/out of the pinned tracks area are nice. Is there any reason though why it is not allowed to reorder tracks inside the pinned tracks area?

[Justin]

Originally Posted by Phazma

I am a little late, but along with these changes would it be possible to have an option for setting the minimum pixels between grid lines for the MIDI editor, just as we can for the arrange view?

I often would like to zoom out to see the bigger picture while editing and yet be able to do fine edits to the grid, but there are not enough visible grid lines. If I could set a smaller minimum pixel value I could do the same edits more efficiently to the grid without having to zoom in just to see the grid.

I suppose we should make it use the main project grid setting for that, yeah...

[tester558216]

Originally Posted by Justin

I suppose we should make it use the main project grid setting for that, yeah...

That's a good idea. Would it be possible for the midi editor to respect the main project grid setting option "snap to grid at any distance" as well?

[Phazma]

Originally Posted by Justin

I suppose we should make it use the main project grid setting for that, yeah...

Not sure if the same setting feels right if people use the MIDI editor on a different screen with different resolution or viewing distance or simply have a different preference for editing MIDI notes vs media items.. but maybe I’m wrong and in practice it actually works well despite these variables. So if that’s the simplest way to implement it it might be worth a try and see if anyone is unhappy with it.