v7.0pre10 - August 18 2023

[Edgemeal]

v7.0pre10 - August 18 2023
* Includes feature branch: optionally hide collapsed tracks within a folder
* Includes feature branch: export mouse modifiers as a script
* Includes feature branch: target individual fixed lanes when pasting media items
* 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
+ Navigator: display items correctly in free item positioning tracks
+ Tracks: vertical zoom accounts for the number of track lanes (experimental)
# Media item lanes: another fix for track setting to play only the new recorded lane [p=2702634]
# Media item lanes: if preference enabled to align track controls, allow resizing lane name area from any track
# Media item lanes: update ARA plugins immediately after comp area edits
# Media item lanes: when automatically comping time selection auto-punch, promote the time selection even if the recording does not completely fill it [p=2702798]
# Toolbar: comping button is mapped to momentary (rather than toggle) override of arrange view mouse modifiers for comping
# Tracks: fix various zoom toggle/cycle actions when maximum zoom is less than 100% of arrange view height
# Windows: update manifest to remove Windows 8.1 features [p=2700567]
# Zoom: set default vertical zoom preference back to 100% of arrange view by default

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

[deeb]

+ Tracks: vertical zoom accounts for the number of track lanes (experimental)

its great! but track header and lane "header" gets out of view now with lanes and it will be precious if same logic for keeping the header in view for tracks happens for the zoomed lane also.

[deeb]

# Media item lanes: another fix for track setting to play only the new recorded lane [p=2702634]

Works has expected! great !! 💎💎💎💎💎

Still "play only the new recorded lane" is a very bad setting name and now we need to be able to set it OFF by track default. 🙏

Do Fixed Lanes options can be changed by API already?

[dangguidan]

Although there is no prompt in the update list, I have tested the MIDI Chase fault and it should be fixed. Thank you!

[mpl]

FX container

Everything is pretty slow from UI side.
And API call for changing FX instance inside container freeze REAPER:
https://forum.cockos.com/showpost.ph...&postcount=675

[Punchipum]

The new GR meter doesn't work for compression that is done from within the Container. On the other hand, it would be great if the TCP meters also show the GR.

[Justin]

Originally Posted by mpl

FX container

Everything is pretty slow from UI side.
And API call for changing FX instance inside container freeze REAPER:
https://forum.cockos.com/showpost.ph...&postcount=675

Hmm that script works fine here, how do I get it to freeze? I edited it to use a JS that I had rather than the "basic m/s decoder" etc, is that a vst?

[Vagelis]

Originally Posted by Edgemeal

v7.0pre10 - August 18 2023

+ Tracks: vertical zoom accounts for the number of track lanes (experimental)

Thanks! Yes that's better with a higher number of lanes!

Found a bug which I actually liked
If you zoom and then drop items on lane add area, the track height extends with their number, then if we choose to see only one lane it sets the track height to the size of this lane. If this is a bug which i guess it is, could this be as an option the way it collapse?

[schwa]

Originally Posted by Vagelis

If you zoom and then drop items on lane add area, the track height extends with their number, then if we choose to see only one lane it sets the track height to the size of this lane.

Not sure I understand... in general if you collapse lanes, then the track should resize to the height of a single lane.

[Vagelis]

Originally Posted by schwa

Not sure I understand... in general if you collapse lanes, then the track should resize to the height of a single lane.

Huh? All this time when collapsed to one lane the track height stayed the same as it was before collapse. Which made that one lane look huge. Now I found that the track height is changing to the height of the single lane after collapsing.

[schwa]

+ Tracks: vertical zoom accounts for the number of track lanes (experimental)

With this change, lanes are considered equivalent to non-fixed-lane tracks with respect to calculating track height.

[Vagelis]

Originally Posted by schwa

With this change, lanes are considered equivalent to non-fixed-lane tracks with respect to calculating track height.

So this is also relative with collapsing, because I thought it's only about zooming.
So it's not a bug but a feature, even better! Just finished work and I will test some more soon, because I've noticed some things.

*For a moment I thought that I 've stepped into a black hole Because this is how it was since the previous pre:

[smandrap]

Originally Posted by Edgemeal

# Tracks: fix various zoom toggle/cycle actions when maximum zoom is less than 100% of arrange view height

Thanks, seems fixed

[Zeno]

Originally Posted by Edgemeal

# Windows: update manifest to remove Windows 8.1 features [p=2700567]

@Justin
Any plans to modernize the UI framework used in Reaper to support Dark Mode on Win11 ?

[Funkybot]

Originally Posted by Zeno

@Justin
Any plans to modernize the UI framework used in Reaper to support Dark Mode on Win11 ?

This was asked a few days ago with a reply from JF:

https://www.askjf.com/index.php?q=6824s

[Vagelis]

Originally Posted by Edgemeal

v7.0pre10 - August 18 2023

+ Tracks: vertical zoom accounts for the number of track lanes (experimental)

Here's a bug with the new behavior:



Creating new lanes and then collapsing to one lane works as expected with the new behavior, but if I resize the track height and then collapse again to one lane, the track height doesn't change so it's like the old behavior. As soon as I zoom vertically after and then collapse it returns to the existing behavior.

[ovnis]

Hi!


The area where we have to click to change the solo track is too much little. I have to try again an incredible number of times each time to select a new solo lane. very painful.

[ovnis]

Why numbers are not inside the dot, like before? As intended or bug?



For me, it's a downgrate. Less space for others TCP elements and just ugly/odd.

[deeb]

Originally Posted by ovnis

Why numbers are not inside the dot, like before? As intended or bug?



For me, it's a downgrate. Less space for others TCP elements and just ugly/odd.

i feel that too. Numbers are there but can be renamed , still they take too much space and we have no option to hide them:




Also this buttons take too much space in TCP: (all the extra space this button have is space not available where it matters most - project space ...)

[ovnis]

Why We can't reduce the width like before:





Before :


Now :


Before :


Now (less space for TCP elements):

[Vagelis]

Also I think in this case autoscroll should happen. (after collapsing return the view to the top of the track to see the collapsed lane)

[FeedTheCat]

Apparently there's a difference between track height being set manually (by resizing) vs height being set automatically by zooming.

When set manually, the height doesn't shrink after collapsing. Maybe make it always shrink so that we can give this experimental option a fair shot?



Another thing to note in this gif is that the collapse button disappears, so after collapsing you can't press it again to un-collapse. I agree with Vagelis that it should stay visible at min height (maybe even over a single lane header button)

[schwa]

Originally Posted by ovnis

The area where we have to click to change the solo track is too much little. I have to try again an incredible number of times each time to select a new solo lane. very painful.

Where are your buttons? All I can think of is that your theme does not have lane_solo_on/lane_solo_off images, plus you have defined the theme colors for "track fixed lane button" and "track fixed lane button when this lane plays" to be the same as the background color.

[ovnis]

Originally Posted by schwa

Where are your buttons? All I can think of is that your theme does not have lane_solo_on/lane_solo_off images

I have deleted it. With previous versions, it worked great:



Why did you remove the possibility to reduce the width of the window like before?

plus you have defined the theme colors for "track fixed lane button" and "track fixed lane button when this lane plays" to be the same as the background color.

It seems to does nothing:

[img]https://i.imgur.com/h5KXwcU.gif[/img]

[schwa]

Originally Posted by ovnis

I have deleted it.

Do you maybe have lane_solo_on/lane_solo_off images still in the theme, but they are empty files or fully transparent or something? What happens if you switch to an old theme like the v5 one?

[ovnis]

+ Tracks: vertical zoom accounts for the number of track lanes (experimental)

Do you know how to have the previous behavior? Is there an option?

I don't like this new behavior because the media item lane track takes too much space (height size).

I loved the fact that the previous edia item lane had the same size than other tracks.
If I wanted to enlarge the edia item lane, I zoomed on it. Currently, I have no choice at all. If there are lots of lanes inside media item lane track, it will take lots of space. It's less options and freedom.


Before:

(The black font for the media lanes! :love: )






Now:

[Sexan]

ok little weirdish:


So now track with enabled lanes have minimum height, but when you collapse it goes to another height and when you expand lanes it goes to third height.

BTW not a fan of disappearing lane buttons at some height (since it cannot fit vertically could it change to some horizontal variation?)

And also could the lane collapse/expand button be on top rather than bottom so it does not move all the time when resizing?

[rain]

Compared to v6.81 the v7pre has almost double amount of CPU consumption in
Performance Meter: RT CPU %
just with one VST-Plugin in Monitor FX chain (which is the mathaudio RoomEQ at high resolution setting)
and this also leads to crackles at 128 samples ASIO-Buffer, whereas v6.81 with same plugins does not crackle at 128 samples buffer.

When disabling Monitor FX chain, the high CPU consumption disappears. So somehow the VST-interface or threading code must have changed.

That is a pity. Must go back to 6.81 and can only try portable v7pre because of this.

[ferropop]

Originally Posted by rain

Compared to v6.81 the v7pre has almost double amount of CPU consumption in
Performance Meter: RT CPU %
just with one VST-Plugin in Monitor FX chain (which is the mathaudio RoomEQ at high resolution setting)
and this also leads to crackles at 128 samples ASIO-Buffer, whereas v6.81 with same plugins does not crackle at 128 samples buffer.

When disabling Monitor FX chain, the high CPU consumption disappears. So somehow the VST-interface or threading code must have changed.

That is a pity. Must go back to 6.81 and can only try portable v7pre because of this.

This might be connected to my issues with AudioMovers ListenTo that sits in my Monitoring Chain and provides a HQ realtime stream of Reaper's audio for remote sessions. In the last couple pres it has been constantly disconnecting, something I haven't experienced before. I contacted their support but they're having no connectivity issues.

[ferropop]

Schwa crash bug with Melodyne:



1. I have a Fixed Lanes comp, with Melodyne edits
2. I recreate the comp using the old Items/splits method with the same media
3. Putting Melodyne on that track results in an instant a crash.


I came across this because, when Melodyne is on a Fixed Lanes comp there is a significant cut in the audio when changing active takes - which did not used to be the case in item/splits comping. It doesn't even have to involve the currently playing items - you could be on bar 1 and change the active take on bar 45 and the audio will completely drop out for up to a second. It's very jarring and disruptive. So I wanted to compare/contrast that this did not used to be the case in the old takes/splits system with Melodyne - you'd change the active take and it would instantly swap over with no dropout. Couldn't get that far to prove it however lol . But hope you can look at both as they are related.

[inthevoid]

I've been using the loopback MIDI & audio features in these pre-releases quite heavily (sending & receiving ~256ch of audio and on 16 virtual MIDI loopbacks between project tabs) and have occasionally run into an issue when playing back in the subproject where the UI completely freezes (beach ball cursor on Mac).

For reference, I'm also keeping project tabs synced / running in background. I'm hosting all the VSTs in a main project and playing back MIDI from subproject.

When the freeze happens, the subproject keeps playing back fine, but since the UI & key commands are frozen the only solution is to kill the process and saving is also not possible. Waiting it out doesn't work. I haven't seen this happen at all when I'm not using loopback audio & MIDI channels and it seems to only happen at high track counts (e.g. when I'm using my main VST template).

I can't replicate this consistently, apart from that it has only happened when playing back from the subproject, but thought it might be worth mentioning. If I find any consistent behaviour I will upload a test project with the issue.

[mschnell]

Originally Posted by inthevoid

virtual MIDI loopbacks between project tabs

How do you do this ?

[smandrap]

Originally Posted by mschnell

How do you do this ?

[daxliniere]

That's a cool feature. I guess this loopback is inside REAPER only, though, not a system driver. (Not that there aren't plenty of those already.)

[mschnell]

Originally Posted by smandrap

Don't have it in V7.0pre
Is this Mac-only ?
(I did a "Route Midi via GMEM" JSFX for that purpose...)

[machinesworking]

Originally Posted by inthevoid

I've been using the loopback MIDI & audio features in these pre-releases quite heavily (sending & receiving ~256ch of audio and on 16 virtual MIDI loopbacks between project tabs) ......
For reference, I'm also keeping project tabs synced / running in background. I'm hosting all the VSTs in a main project and playing back MIDI from subproject.

OK so first off, I've used Digital Performer forever, and this looks a lot like DP's Chunks and V-racks feature. A project is hosting VSTi's etc. and other projects can access those VSTs etc. The caveat in DP is that the V-Rack (virtual rack) doesn't allow for host/plugin automation, only MIDI notes and CC's etc.

So far being a noob at projects in general I haven't been able to play a MIDI track sending to Loopback 1 and get it to trigger an instance of Diva on a separate Project tab. I'm sure it will happen any pointers are welcome.

The real question though is did Reaper break the wall? Are you able to use plug in automation in the MIDI subproject? As metioned above the biggest limitation with DPs V-Racks are that the MIDI project can't write plug in automation.

[Gass n Klang]

can we have an option to collapse lanes automatically when turning off comping (and vice versa)?

[Gass n Klang]

bug/inconsistency:

some child-tracks (in fixed lane mode) with a parent in one razor edit group. razor editing the child-tracks affects only the lane youre editing in all child-tracks. razor editing the parent affects all lanes of all child tracks.

Shouldn't it affect only the "active" comp lane?

[mschnell]

Originally Posted by Gass n Klang

can we have an option to collapse lanes automatically when turning off comping (and vice versa)?

What exactly does "turn off comping" do ?

[FeedTheCat]

Originally Posted by Edgemeal

+ Tracks: vertical zoom accounts for the number of track lanes (experimental)

Hmm, liking this so far!

If it stays it would be great if at minimum height the lane header buttons stay visible. Afaict it's only off by a few pixels and I guess the header buttons could even be a bit smaller (now that they don't contain text).