v6.81+dev0728 - July 28 2023

[sockmonkey72]

v6.81+dev0728 - July 28 2023

• * Includes feature branch: support rendering raw PCM data
• * Includes feature branch: Development_Theme theme
• * Includes feature branch: JSFX plug-in defined compile-time configuration parameters
• * Includes feature branch: LV2 non-automatable patch parameter support including atom:Path
• * Includes feature branch: video YUV gamut selection
• * 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: GR metering as embedded UI for third-party VSTs
• * Includes feature branch: media item fixed lanes
• + Project bay: display bridged status in performance column, allow filtering to match this status
• + Project bay: when in FX tab, filtering searches preset, developer, type
• + Project bay: when matching FX, allow words to be matched from different columns
• # Media item lanes: fix mouse modifier to move/copy media items and comp areas together
• # Media item lanes: fix preserving media items outside of comp areas during comp area edits
• # Media item lanes: fix small items potentially left behind after comp area edits
• # Media item lanes: improve razor editing behavior when comping
• # Media item lanes: revert free-overlap behavior of comp areas from previous +dev build
• # Media: remove unnecessary nul character in raw PCM media .rsrc.txt file [t=281217]

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

[akademie]

Nice to see some love for Project bay

There is a feature request of mine in Feature Requests sub-forumn which would fit this dev cycle I believe:
Save with media option in Project Media/FX Bay - (Feature Requests)

Originally Posted by akademie

Adding "Save with media" option in Project Media/FX Bay would be very useful for saving portable (interchangeable) libraries of samples/loops, MIDI clips etc.

Thanks

[akademie]

And also few other useful feature requests for Project Media/FX Bay here:

Add Oversampling to Project Bay FX Tab

Originally Posted by woylie

It would be great to be able to toggle FX oversampling on and off for ALL instances of a particular plugin, without having to manually do it for each instance.

The Project Bay FX tab seems to be a logical place for such a toggle, given you can already use it to globally toggle other plugin features.

-- and --


Project bay window automatically scroll to selected item in arrangement

Originally Posted by Infrabass

Hi Cockos!
...<snip>
Although there is ONE thing I really miss:
the ability for the project bay window to automatically scroll to the (first) selected item. That way, and with the already implemented option to scroll the arrangement to mirror the project bay selection, it would be a strong bidirectional system!
<snip>...

Oh, and then there is also this Bug Report regarding Project Bay:
Project Bay / Automatically retain media - (Bug Reports)

[Vagelis]

Seems that many things were fixed in this build, will test further after work, thank you very much!

[FeedTheCat]

Originally Posted by Vagelis

Seems that many things were fixed in this build, will test further after work, thank you very much!

Yup, so far everything seems to work nicely. Loving the recent simplifications, great job schwa!

Here's an oddity I've stumbled upon but not sure how to reproduce exactly. Sometimes deleting one area deletes all areas. Maybe it has something to do with undo/redo.



I also had the case once, that a single selected item would move all other items on the track (comp lane). Maybe it's related somehow, but I never managed to replicate that.

[FeedTheCat]

This behavior could maybe be improved, I wouldn't have expected the trimming.

[FeedTheCat]

I really like how you can delete single split points. I think it might be nice for consistency if you could also delete the split points between synced areas.



The area on the left side of the split could always be extended to take the space of the right side. If the left side is synced, the combined area becomes synced, etc.

[souk21]

* Includes feature branch: Development_Theme theme

The volume/velocity knob on media items is misaligned:





On a mac with a retina screen

[Vagelis]

Bug: the comp area edge is moving with the edge of the item in fixed lanes.

Though, if the edge of the comp area is at the same place with the edge of the item, then dragging it it doesn't move with the edge of the area.

[Vagelis]

This is still present, the curvature is not updating in the comp lane. Regarding fades in fixed lanes, isn't it possible to happen when the item has the same length as the comp area?

https://forum.cockos.com/showpost.ph...64&postcount=7


And this is still present as well:

https://forum.cockos.com/showpost.ph...9&postcount=18

[Vagelis]

Originally Posted by sockmonkey72

v6.81+dev0728 - July 28 2023[*]# Media item lanes: improve razor editing behavior when comping

This is really perfect now except one small thing. Selecting a muted part in fixed lanes with RE and dragging it inside a comp area trims it. I think it should trim it only when there's a comp area with RE in the selection. So in this case RE should trim just the item and not the area.
This wasn't happening before and it was very useful to select muted parts and drop them in some active area. Could this be one last exception? Everything else works perfect though!
Also visually this build is the best ever, the comp areas looks great on both comp lane and fixed lanes!

[Vagelis]

Some improvement on this behavior would be very welcome as well.
Dragging the fade of a crossfade is moving with the edge of the comp area, but when there's no crossfade the area unsync, in this case the left area. And doing this with the opposite fade unsyncs the right area instead of staying in sync.

[OLSHALOM]

Originally Posted by FeedTheCat

I also had the case once, that a single selected item would move all other items on the track (comp lane). Maybe it's related somehow, but I never managed to replicate that.

This comes when doing the first comp in a new lane. After you release the moving areas (and do another selection), it's possible to move single areas again.

[OLSHALOM]

The comp area in lane 2 gets out of sync after reactivate comping, even it was not touched.

after unsyncing a comp area in noncomp mode, wouldn't it make sense:

- The comp area in the takelane area, which is still in sync with the comp lane gets adjusted to what is still in sync.

- The area, which is not present anymore in the comp lane gets marked without the yellow border, as an area, which was used in the comp, but altered ("grey overlay, as it is already").

- The user edit in the yellow line of the comp lane adds the 2 edit points also in the take lane, which it belongs too.

Anyway, at the end of the gif comes a weird behavior, where an untouched comp area of lane 2 gets unintentionally altered to lane 1 by switching lanes in the area next to the mentioned, but it shouldn't.

Hope that helps.

[MasonAmadeus]

I know this is an edge case - but when dragging/dropping a media item from the project bay into a track with fixed item lanes, it lands across all of them - as though lanes weren't enabled. It can be fixed by dragging the item to a different track and then back down.

EDIT: Doesn't seem to *always* happen - haven't figured out what specific property causes this interaction.

Just a small thing - figured I'd mention it because I noticed it.



As someone using Reaper for sound design - I'm loving the item lanes! Even though I'm not using them necessarily as intended haha.

[ferropop]

Settings : Time Selection Punch ON, with Create New Comp Areas for New Recordings While Comping OFF

Situation : super common, "hey sing a few more takes of that phrase" but using Time Selection to auto mute only and not auto-commit.




Issues:

1. Recordings are trimmed to Time Selection, which creates this awkward gap to the L/R of the item when swiping it, because
it's impossible to perfectly swipe to the edges. Then you have to manually resize the items out, create
crossfades, and it's just a whole awkward process.

2. Recordings are trimmed to Time Selection, which I'll insist with my dying breath is the wrong default behaviour. We have lanes!
Let stuff be the length of the recording pass, and we swipe in what we want! And if Auto Comp is on, just promote the Time Selection
slice as normal, but leave the full recording pass in the source lane. I really don't get the pushback on this.


This happens because Time Selection is the shared mechanism for both Auto Mute and Punch In Area. The fact that when I
move the Crossfade/Comp-Area edge it intelligently expands the underlying item is Great, but does this not
suggest that the full recording pass should just be visible to begin with?


Look how much cleaner this is if the punches weren't trimmed to Time Selection:

No nonsense, no edge weirdness, no having to expand items. We have lanes - there is space -
just show the whole recording pass!

[ferropop]

Related to above :



A weird interaction on the right edge, not sure what's up.

[ferropop]

To add to all of the above :

If you swipe an area that is beyond the edges of a source item,
maybe auto expand the edges of the item to fit the Comp Area in the Comp Lane
instead of leaving a problematic gap.

Honestly this suggestion feels kludgy to me but might be a good behaviour to consider nonetheless.
Better imo is to just capture the whole recording like I said above, and it solves 99% of cases.

[Valle]

• Includes feature branch: support rendering raw PCM data

Sooo ... what's this about?

[sockmonkey72]

Originally Posted by Valle

Sooo ... what's this about?

headerless PCM sample data, very much appreciated. Thank you, devs!

[Tale]

# Media: remove unnecessary nul character in raw PCM media .rsrc.txt file [t=281217]

Fix confirmed, thanks!

[nofish]

Originally Posted by Valle

Sooo ... what's this about?

For context:
https://forum.cockos.com/showthread.php?t=281035