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.

[tonalstates]

Originally Posted by Punchipum

(...) On the other hand, it would be great if the TCP meters also show the GR.

Yeah +1 , I don't understand why they were removed from the TCP they were sooo useful there also. Pleasee :'( I basically only use the TCP </3 a toggle at least

[sosie]

Please add razor edit to midi editor.. A lot of people miss this feature

[ceanganb]

Originally Posted by sosie

Please add razor edit to midi editor.. A lot of people miss this feature

Count me in.

[mschnell]

Originally Posted by sosie

Please add razor edit to midi editor.. A lot of people miss this feature

Off topic (and hence ignored here) regarding v7.0 pre 10 !

This thread -> https://forum.cockos.com/showthread.php?t=281748
seems to be provided for v7.0 pre -> v7.0 release Feature requests.

[mschnell]

This bug (?) has been in former pres as well:

I have a project template that provides a track with lanes.

The first lane recorded is shown named "1"

When I record additional lanes they are automatically named in such terms:
"C4", "C3", "C2", "C1", "1" (again), "2", ...

How can I prevent this ?

in the project file I see

    LANENAME 1 C4 C3 C2 C1 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60

I suppose I can edit this manually ... Yep that works, but that's not a "nice way"
I suppose those names should be exactly 64. Correct ?

I suppose this happened because I used an existing project to create the template and deleted the lanes and renamed the first before saving as a template.

Maybe it would be good to reset the names of deleted lanes to a default. Or is it planned to allow for predefining lane names ? In that case an editor would be needed....

[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?

[sosie]

Originally Posted by mschnell

Off topic (and hence ignored here) regarding v7.0 pre 10 !

This thread -> https://forum.cockos.com/showthread.php?t=281748
seems to be provided for v7.0 pre -> v7.0 release Feature requests.

ok thanks i wrote there

[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

[souk21]

Originally Posted by Punchipum

On the other hand, it would be great if the TCP meters also show the GR.

Yep, I never use the mixer and was loving being able to see GR in TCP. Is there any reason for this deletion ?

[Sexan]

Maybe its not accounting header well yet?


You can see icons scrolling off screen a little on every new lane... but is more of a nitpick than anything.

Hope that selected lane could zoom centered for "last selected" option

[Punchipum]

Originally Posted by souk21

Yep, I never use the mixer and was loving being able to see GR in TCP. Is there any reason for this deletion ?

Yes, it seems that there are several of us who do not use the mixer for almost nothing 🤷

[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?

[deeb]

I had the opportunity to play with an old version of my old DAW and i noticed that scrolling steps are much smaller, and i generally prefer. Altho there is some smart behaviour in reaper now by keeping track headers on top, the other is smoother. Maybe the combination of both can be the best way of scrolling? - or zoom/scroll setting for step value.



VS:

[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 ?

[Edgemeal]

Originally Posted by Justin

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?

FWIW, Script doesn't do anything here, uncommented TrackFX_SetNamedConfigParm lines, then replaced vsts with ReaComp and ReaEQ, still nothing, then added a container to first container (any fx will do I suppose) and REAPER froze when I ran script (tested from IDE only).


Win10_x64 w/Pre9 & Pre10

[Daodan]

Moving left fade breaks comps. Project attached

[Daodan]

And sorry my stupidity but how to move items with comp areas without using Razor when lanes are collapsed?

[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 Daodan

And sorry my stupidity but how to move items with comp areas without using Razor when lanes are collapsed?

Move the comp area instead of the item, but this way you can't move them all. Only with RE. Or you could select with RE and hit that square button which sets one big comp area for all items. Then you could drag the comp area and move all items.

[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:

[deeb]

This button looks strange now. Maybe it could just be visible when all the lanes are on view or collapsed.

[Daodan]

Originally Posted by Vagelis

Move the comp area instead of the item, but this way you can't move them all.

Yes, I found that alt+drag moves area with item. Might be useful but intention is to move or copy whole section (chorus for example) without loosing original takes and comp structure. Not one comp area.

Originally Posted by Vagelis

Or you could select with RE and hit that square button which sets one big comp area for all items. Then you could drag the comp area and move all items.

Sorry, but again intention is to keep comp structure while moving/copying. Creating one big comp area is opposite.


Don't get me wrong RE is great and I use it a lot but usually for such task as just select bunch of items and move/copy them I use old good marquee selection.The inconvenience is that now I have to remind myself "oops, I can't move those items as usual, I need to create RE". Everyone OK with that?

I wish some kind of option like "Move items with comp areas when lanes collapsed" or something better. Or perhaps everything I just wrote does not make sense and I don’t understand something.

[Vagelis]

Originally Posted by Daodan

I wish some kind of option like "Move items with comp areas when lanes collapsed" or something better. Or perhaps everything I just wrote does not make sense and I don’t understand something.

There's no other way at the moment AFAIK, but this is also how the system works. Moving the items in comp lane unsync from their sources, so you can edit them separately without changing the sources. This was requested from many users long time ago. If you want to stay in sync with the comp areas you have to edit only the comp areas.
So can't think of way now to drag areas while dragging the items in the comp lane.
Maybe if there was an option so everything could stay in sync, e.g move items and comps, but then you won't be able to edit the items without editing their sources I guess, except if going out of comp mode each time you want to edit them.

EDIT: Maybe Schwa could add support for using marquee for items+comp areas to move them together in the comp lane if it makes sense.

[deeb]

I am not into comping but about this “ Moving the items in comp lane unsync from their sources, so you can edit them separately without changing the sources. “. Feel like there is no reason to unsync when sources and comp lanes edits all are moving together/collapsed.

[mpl]

Originally Posted by Justin

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?

I commented 2 lines with TrackFX_SetNamedConfigParam reduced_name. Everything except these lines works ok.

I used jsfx kanaka MS decoders encoders (i guess its bundled).

[Vagelis]

Originally Posted by deeb

I am not into comping but about this “ Moving the items in comp lane unsync from their sources, so you can edit them separately without changing the sources. “. Feel like there is no reason to unsync when sources and comp lanes edits all are moving together

Well I didn't decide about this, at start I was the same, but then I got used to it and it definitely has advantages which are visible after spending more time with it. You can switch modes that way by editing items or comp areas without using an option or something similar.
And in the end if you want to stay in sync you can always work in lanes with the sources except comp areas in the comp lane.
This system is the most flexible around which gives us so many ways to work with imo.

[deeb]

I don’t know .. if everything moving together they can stay In sync .. collapsed can mean they move together: comp lane edit and comp lane sources. But I don’t know. When we use RE and move do they unsync? Anyway not my beach for now.

[Vagelis]

Originally Posted by deeb

When we use RE and move do they unsync?

I'm short no but it's a bit complicated. Comp areas and items can stay in sync with RE,it doesn't work the same in comp lane only when all lanes are visible, in this case moving items in comp lane with RE unsync, but it also makes sense in this case because you can do this with the sources as well since are all visible, or select both sources and items in comp lane with comp areas and move them together.

[deeb]

Originally Posted by Vagelis

I'm short no but it's a bit complicated. Comp areas and items can stay in sync with RE,it doesn't work the same in comp lane only when all lanes are visible, in this case moving items in comp lane with RE unsync, but it also makes sense in this case because you can do this with the sources as well since are all visible, or select both sources and items in comp lane with comp areas and move them together.

So if everything is selected then they don’t unsync. Collapsed can be perceived that all of them are selected on the background. So they should not unsync.

[Vagelis]

Originally Posted by deeb

So if everything is selected then they don’t unsync. Collapsed can be perceived that all of them are selected on the background. So they should not unsync.

Yeah this is how it works now with RE. Or else you have to drag the areas in the comp lane to stay in sync without using RE, but not the items.

[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.