v6.78+dev0330 - March 30 2023

[sockmonkey72]

v6.78+dev0330 - March 30 2023

• * Includes feature branch: fixed lane collapsing
• * 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
• + Click source: fix glitch at start of playback with take FX that use PDC [t=277406]
• + FX: avoid audio-thread reset of FX when moving between chains with different oversampling set
• + JSFX: fix loading JSFX from subdirectory of project Effects directory [t=274578]
• + JSFX: support plug-in defined compile-time configuration parameters
• + MIDI: prevent hang on extremely long corrupt midi files
• + MIDI: when creating new items, snap position to PPQ [t=271205]
• + Media item lanes: add mouse modifiers to move or copy comp area and media items on all lanes together
• + Pencil drawing: fix potential unsafe memory access when drawing new MIDI items
• + REX: fix memory leak when exploding items
• + ReaVerb: fix gain issues with resampling of certain impulse response files [t=277406]
• + Super8: support from 1 to 48 channels (default is 8)
• + Track metering: when using pre-fader metering, show meters for muted/unsoloed tracks
• + Zoom: allow mouse-centered vertical zoom to target the interior of a track
• # MIDI devices: fix macOS dark mode appearance issues
• # Media item lanes: automatically play new inserted lane when lanes are collapsed
• # Media item lanes: don't display lane name for unsynced comp areas
• # Media item lanes: ignore "move comp area and media items together" mouse modifier on unsynced comp areas
• # Media item lanes: improve cleaning up bits of media items left behind by comp area edits
• # Media item lanes: treat double-click on lane collapse button as a 2nd click
• # Pencil drawing: optimize CPU/memory use when drawing new MIDI items

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

[Funkybot]

Originally Posted by sockmonkey72

+ Zoom: allow mouse-centered vertical zoom to target the interior of a track

Nice!

[Funkybot]

Originally Posted by sockmonkey72

[*]+ Track metering: when using pre-fader metering, show meters for muted/unsoloed tracks

While making improvements to Track Metering, could we get an action to toggle metering on input monitored tracks from pre to post-fx? Once I set my input level on a given track, it's done. But I often want to tweak the output level of any amp sims, etc. using the same metering scale (versus say, the master, or without creating a folder/bus).

[Vagelis]

+ Media item lanes: add mouse modifiers to move or copy comp area and media items on all lanes together

Thanks! First thoughts on this and maybe the last piece of the puzzle. While this is very useful, i would prefer if this behavior could apply only on the items in comp lane and not in lanes as default. Why? Because the flexibility of lanes compared to the old system is that we can move/edit the comp areas individually. And second I think when editing or moving the item in comp lane with the behavior of this modifier applied, would bring less confusion with edits when only the comp lane is visible. *This modifier could be as an addition to use this behavior in lanes too.

My thoughts and how things could change imo to a better comp system: The items in comp lane could move with the areas while moving all items in lanes without unsyncing, and with the same modifier, when used in lanes, we could move the areas individually.
On the contrary it would be nice to reverse the existing behavior and toggle unsync/sync when we want it with an action/modifier.

Imho this would bring less confusion with unsynced areas, things will be from start always in sync by reflecting the edits from comp lane to lanes and the user could unsync on specific cases. I believe it's better to deal from start with synced areas for comping than having to deal with unsynced ones.

[Vagelis]

# Media item lanes: improve cleaning up bits of media items left behind by comp area edits

I think this fixed the bug with unsynced areas that were deleting the items in comp lane, thanks!!

[tohubohu]

Originally Posted by sockmonkey72

v6.78+dev0330 - March 30 2023[*]+ MIDI: when creating new items, snap position to PPQ [t=271205]

it's better but all the copy-paste doesn't work
and all the 'draw a copy...' in mouse modifiers either
the action 'Insert or extend midi items to fill time selection' does not work either

[souk21]

+ JSFX: support plug-in defined compile-time configuration parameters

Sounds cool! How to use this? I've looked at the updated builtin JSFXs but couldn't find anything.

edit: found it!

config: nch "Channels" 8 1 2 4 8="8 (namesake)" 12 16 24 32 48

And it can be set from the "+" menu (at the right of presets)

[souk21]

I still get an incorrect sorting for the "Status" column of the input list.
But only the input list, the output list seems to behave correctly.




Also, is it possible for these lists to remember their columns width?
Currently they only remember their sorting.
That would be useful because some devices have long names that only differentiate at the end:

[ferropop]

The "copy unsynced to new lane and recomp" action is now not working:

[ferropop]

Inconsistent weirdness with the new Ctrl-Drag "copy comp area and lanes together".



Some areas copy, some areas move destructively. Same modifier.

[ferropop]

Also (please chime in anyone)...

I think the spirit of duplicating Comp Areas from Chorus 1 to Chorus 2 for example, will be done with Razor Edits and not by Ctrl-Dragging comp areas.

Not sure if that's what these new copy actions were for, but it's not adequate for the more essential Razor Edit duplication that will be happening day-to-day when flying stuff around the project with grid-necessary precision.

[ferropop]

^^ especially when collapsed - there's an expectation that if you Razor a bunch of stuff and duplicate, that everything comes along for the ride.

This is how it worked with Item-takes, it'd be important to keep consistent that behaviour imho.

Could be solved by adding options in this menu:



Something like "Razor Edits on Fixed Item Lanes affect all lanes" toggle.

[Thonex]

Bug: Razor breaks synced Comp

Razor functionality seemed to be fixed in the previous Pre-release, but seems broken now. If I razor drag to a new lane, it breaks the synced comp:

[MonkeyBars]

Originally Posted by sockmonkey72

[*]+ Zoom: allow mouse-centered vertical zoom to target the interior of a track

Perhaps while on this code section you might consider enabling marquee zoom also to target track interior. FR here

[Vagelis]

Originally Posted by ferropop

Also (please chime in anyone)...

I think the spirit of duplicating Comp Areas from Chorus 1 to Chorus 2 for example, will be done with Razor Edits and not by Ctrl-Dragging comp areas.

Not sure if that's what these new copy actions were for, but it's not adequate for the more essential Razor Edit duplication that will be happening day-to-day when flying stuff around the project with grid-necessary precision.

I find EXTREMELY useful the copy area modifier, because first we don't need to change modifier aka RE, and second doing so we don't leave any gaps as previously during playback and we can continue comping on different places in the timeline super easy and fast.

[anomar]

Hi,
is there a bug with the command "copy unsynced comp area to new lane and recomp?
Everything is deleted and nothing is copied.

[ferropop]

Originally Posted by Vagelis

I find EXTREMELY useful the copy area modifier, because first we don't need to change modifier aka RE, and second doing so we don't leave any gaps as previously during playback and we can continue comping on different places in the timeline super easy and fast.

Right I'm just saying the Razor Duplication equivalent is also necessary (way more general and less specialized than the above) -- where all the lanes get razor-duplicated along when copy/pasting 1st Chorus to 2nd Chorus for example. Collapsed or not.

[Vagelis]

Originally Posted by ferropop

Right I'm just saying the Razor Duplication equivalent is also necessary (way more general and less specialized than the above) -- where all the lanes get duplicated along when copy/pasting 1st Chorus to 2nd Chorus for example.

I agree yes both are useful for different things

[Thonex]

Originally Posted by anomar

Hi,
is there a bug with the command "copy unsynced comp area to new lane and recomp?
Everything is deleted and nothing is copied.

I can confirm this bug.

I have had buggy behavior with "copy unsynced comp area to new lane and recomp" too.

[Phazma]

Originally Posted by sockmonkey72

v6.78+dev0330 - March 30 2023[*]+ Zoom: allow mouse-centered vertical zoom to target the interior of a track

Thanks so much! Now finally fixed lanes and envelope lanes zoom as expected

Originally Posted by sockmonkey72

[*]# MIDI devices: fix macOS dark mode appearance issues

Thanks for the fix! Small nitpick but would it be possible to fill the Status column for available MIDI devices with something like "Present", maybe in green color?

Filling the status column only for devices which are "not found" or "not present" draws more attention towards those devices than the ones which can actually be used.

[Phazma]

Originally Posted by sockmonkey72

v6.78+dev0330 - March 30 2023[*]+ Zoom: allow mouse-centered vertical zoom to target the interior of a track

Btw I see that the maximum zoom of fixed/envelope lanes is limited so that the total track height doesn't exceed the maximum vertical zoom setting.

Can we please also have the possibility to apply the "Maximum vertical zoom" setting to the interior of a track (even if that makes the actual track bigger than the maximum vertical zoom is set to)?

Example:

- Maximum vertical Zoom: 100%
- Track with 3 fixed lanes

Each lane can only be zoomed to 33% screen size. The requested setting would allow us to zoom a lane to 100% screen size even if that means that the actual track heigth would be 300% screen size.

[akademie]

Originally Posted by sockmonkey72

v6.78+dev0330 - March 30 2023

• + JSFX: fix loading JSFX from subdirectory of project Effects directory [t=274578]
• + JSFX: support plug-in defined compile-time configuration parameters

Great, thanks


When project-specific JSFX topic is on the table, I would like to suggest 2 related features:

- adding an action to automatically compile (copy) JSFX effects to project folder for portability, so no need to do that manually

- adding alternate mode - lets call it "In Project" JSFX Effect which would be the same as effect folder in project folder,
but the JSFX codes would be included directly in RPP project file (absolutely my favorite option) - (Something like with
external .MID files versus "in project" MIDI items)!

Thanks

[tohubohu]

Originally Posted by tohubohu

it's better but all the copy-paste doesn't work
and all the 'draw a copy...' in mouse modifiers either
the action 'Insert or extend midi items to fill time selection' does not work either

the copy/paste with the razor edit and the time selection don't work either...

[Edgemeal]

Add comp area between previous comp area and end of media
Is it not weird that the end of the added comp is equal to the end of the rightmost item on any track and not the fixed lane track we're calling this action from?
Maybe just me, but I don't see why I'd ever want/need this action as is.

[bolgwrad]

This doesn't seem right: fade in the comp lane, dbl-click in the comp lane on the new fade section - the comp is unsynced, correct. Dbl-click on the circle, I would expect the new lane to contain the faded source item at least, but both comp lane and new lane are blank.

[musicbynumbers]

+ Zoom: allow mouse-centered vertical zoom to target the interior of a track

I'm not sure if this is working here and which vertical zoom mousewheel action it's meant to work with? It seems a bit touchy using the mousewheel vertical action I found that wasn't obviously SWS etc

Also, a bug.. when I did manage to get it to zoom into a single fixed lane track. When I then used hand scroll, The fixed lane number bit didn't move but the items on the track did so it put them out of sync with each other visibly

[mschnell]

Originally Posted by sockmonkey72

v6.78+dev0330 - March 30 2023

• + JSFX: support plug-in defined compile-time configuration parameters

Interesting !! how does that work ?
Can such config be used in the <? Macros ? (e.g. to set the number of of sliders shown )

-Michaeĺ

[Justin]

Originally Posted by mschnell

[/LIST]Interesting !! how does that work ?
Can such config be used in the <? Macros ? (e.g. to set the number of of sliders shown )

-Michaeĺ

It can only be use by the <? preprocessor blocks... Check out the updated super8 to see what it does.

any time you change these parameters, it completely re-inits the state, since it's designed for very big changes.

If you want to show/hide sliders dynamically from code, that's been supported for a while (e.g. the loudness meter uses that api).

[ferropop]

Originally Posted by MonkeyBars

Perhaps while on this code section you might consider enabling marquee zoom also to target track interior. FR here

Totally a use case for wanting a single lane to occupy most of the screen, for example. Again, it gets tricky because it's adding new modifiers and not always desirable, so maybe a preference?

It might also be a case for using alt mappings when "in comp mode" vs not, as you'll probably want all the lane-centric stuff while comping and the track-centric stuff when not in comp mode (as you're doing more arrangement or broad strokes stuff).

[dangguidan]

Originally Posted by sockmonkey72

+ MIDI: when creating new items, snap position to PPQ

In practical operations, the left side of an item is often shifted. Currently, the PPQ position reading of MIDI is based on the starting position of the item. Can we change it to starting from the 0 position of the project? This may be more reliable.

[ferropop]

An idea about displaying unsynced areas.

Let's say you move an item and it unsyncs, the source indicator disappears because - it's out of sync.

But : why not just reflect whatever media items are in the comp lane, down to the source lanes - irrespective of size/position? Like if a slice of source is in the comp lane, that slice gets "highlighted" in the source lane - in the same way as desyncs used to look.



This would take care of both Comp Area sources AND unsynced items. If something is in the comp lane, it's mirroring this fact in the sources. Unsynced or not. Right now when you start editing the Comp Area items, we completely lose the visual connection between comp and source - this could restore that connection in a simple way.

[tohubohu]

Originally Posted by tohubohu

Originally Posted by tohubohu View Post
it's better but all the copy-paste doesn't work
and all the 'draw a copy...' in mouse modifiers either
the action 'Insert or extend midi items to fill time selection' does not work either
the copy/paste with the razor edit and the time selection don't work either...

Razor edit 'split media item at area edges' doesn't work either
razor edit 'move areas' (drag)
razor edit 'copy areas' (left drag)

[mschnell]

Originally Posted by Justin

If you want to show/hide sliders dynamically from code, that's been supported for a while (e.g. the loudness meter uses that api).

I did a JSFX that is based on the preprocessor and now seemingly easy can be enhanced to a variable count. (On top of that hiding unused sliders dynamically could be a further improvement.)

[Hipox]

Originally Posted by Phazma

Btw I see that the maximum zoom of fixed/envelope lanes is limited so that the total track height doesn't exceed the maximum vertical zoom setting.

Can we please also have the possibility to apply the "Maximum vertical zoom" setting to the interior of a track (even if that makes the actual track bigger than the maximum vertical zoom is set to)?

Example:

- Maximum vertical Zoom: 100%
- Track with 3 fixed lanes

Each lane can only be zoomed to 33% screen size. The requested setting would allow us to zoom a lane to 100% screen size even if that means that the actual track heigth would be 300% screen size.

+1

[Hipox]

Originally Posted by musicbynumbers

+ Zoom: allow mouse-centered vertical zoom to target the interior of a track

I'm not sure if this is working here and which vertical zoom mousewheel action it's meant to work with? It seems a bit touchy using the mousewheel vertical action I found that wasn't obviously SWS etc

Also, a bug.. when I did manage to get it to zoom into a single fixed lane track. When I then used hand scroll, The fixed lane number bit didn't move but the items on the track did so it put them out of sync with each other visibly

Gif about misalignment of lanes indicators and lanes itself:

[souk21]

Would it be possible to have syntax highlighting for preprocessor blocks outside of a @section ?
Currently it's quite hard to read/spot because it looks like a comment:



taken from new super8 code

[tohubohu]

Originally Posted by tohubohu

Razor edit 'split media item at area edges' doesn't work either
razor edit 'move areas' (drag)
razor edit 'copy areas' (left drag)

I was wondering :
Won't the 'copy/paste' and the 'Razor edit: split media item at area edges' cause problems with the 'Offset overlapping media items vertically' option or with the audio items?
If we do razor edit: 'split media item at area edges', can't the 'snap position to PPQ' cause the items to shift vertically?
On the other hand, if you 'paste' an audio item, can't the 'snap position to ppq' cause junction problems between audio items?

[souk21]

Found a bug with compile-time config:

config: first First 0 0 1
<?
  first ? printf("config: second Second 0 0 1");
?>

"Second" menu item doesn't show up when "First" is set to 1.
Surprisingly, if I select "First" = 1 in the menu and then do a full recompile/reset, now "Second" shows up, even though "First" is now 0.


edit:
Something else, don't know if it's intentional but:

config: first First 0 1 2

allows to define a default value that's not in the "value list", resulting in no option being selected in the menu by default.

[souk21]

When doing a full recompile/reset, config returns to its default value in the menu but it's not reflected in the preprocessor corresponding variable.
Things get back to normal after a second recompile.

[Sexan]

Maybe I'm getting old, but where how do you activating new zoom ? I changed all options in track vertical zoom behavior and got nothing.
EDIT: Needs increasing zoom level above 100%

Regarding "inserting empty lanes" in collapsed state its cool now that it automagically plays that lane BUT its still little awkward to always go to drop down and select xy lane.
If you just open it and click random one (just to create it and get going with it) You end up with random lanes all over the place: 2 is 3 ,3 is 5, 5 is 1 etc. If you want a nice layout of lanes then it needs thinking and carefully selecting the lane (which is slow operation)

Non collapsed state already has this option (which makes sense since you see all lanes), but in collapsed state it really does not make sense (to me) to choose above which lane you want to add new one since you see only current lane. It should just be "insert above current lane" without drop down list (or add another action above it if you want to keep drop down list)