v7.0pre6 - August 11 2023

[Vagelis]

v7.0pre6 - August 11 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
• + Actions: consistently refer to collapsed folders as 'collapsed' rather than 'compacted'
• + Crossfades: limit overlap and crossfade when splitting at time selection or razor edit [p=2699919]
• + FX: fix issues when per-FX PDC mode is combined with auto-bypass [p=2700214]
  + Media item lanes; draw faint peaks to indicate items in collapsed lanes
• + Media items: store fade-in/fade-out length with greater precision in project files
• + Mouse modifiers: support existing custom actions or scripts that use deprecated "set default mouse modifier for context" actions (actions no longer appear in the actions list, do not support menu/toolbar feedback, and will not support new mouse modifiers)
• + Paste: when pasting into FIPM or fixed lane track, target the y-position or lane of the last mouse click (experimental)
• + Tracks: add preference to not display tracks in a folder when the folder is fully collapsed
• # Fades: fix crossfade behavior with recorded items in some scenarios [p=2699919]
• # Media item lanes: ensure that previous comp areas are preserved when creating new comp lane [p=2700115]
• # Media item lanes: fix mouse editing comp area left edge at project start [p=2699832]
• # Media item lanes: fix some unexpected behaviors when loading projects or after undo
• # Media item lanes: improve some crossfade behaviors when editing comp areas
• # Media item lanes: improve use of space when re-comping multiple media items
• # Media item lanes: prevent mouse changing lanes when lane buttons are not displayed [p=2699834]
• # Media item lanes: simplify lane color menu
• # Media item lanes: update item color during comping [p=2699846]
• # Media item lanes: when automatically creating comp areas, prioritize media items in higher lanes

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

[daxliniere]

Originally Posted by Vagelis

v7.0pre6 - August 11 2023[*] * Includes feature branch: GR metering as embedded UI for third-party VSTs

This is VST3s only, right?

[schwa]

This is supported through VST extensions published by presonus:

VST3: Presonus::IGainReductionInfo
VST2: effVendorSpecific, 'PreS', 'GRdB'

[daxliniere]

@Justin, the crash on loading SSL X-Saturator v5 is back. The last working version I used was v6.81 release. I'm going back through 6.81+DEVs now to see where it started.

EDIT: Can confirm it's present in the very first dev after 6.81 was released.

[daxliniere]

I was previously using 6.78 release, so let's try those:

Broke:
6.78+0330
+0328
+0322
+0319
+0318

Working:
6.78+0317

[Vagelis]

So, I guess this is not possible?

https://forum.cockos.com/showpost.ph...5&postcount=24

[Sexan]

bump vertical zoom offset
https://forum.cockos.com/showpost.ph...8&postcount=46

[MonkeyBars]

Originally Posted by Vagelis

[*]+ Mouse modifiers: support existing custom actions or scripts that use deprecated "set default mouse modifier for context" actions (actions no longer appear in the actions list, do not support menu/toolbar feedback, and will not support new mouse modifiers)

Please publish this list of hidden action command IDs on the forum and in a Reaper documentation web page for reference/archive

[Phazma]

Originally Posted by Vagelis

[*]+ Paste: when pasting into FIPM or fixed lane track, target the y-position or lane of the last mouse click (experimental)

Nice workflow improvement. In FIPM I'd argue it would be more intuitive if the vertical center of the item was placed at the last click position instead of the top left corner.

Also, I know I have already asked a few times, but maybe now the "Insert new MIDI item..." action can be modified to respect the y-position/lane of the last mouse click?

Originally Posted by Vagelis

[*]+ Tracks: add preference to not display tracks in a folder when the folder is fully collapsed

Thanks, this is nice Can we please also have a preference to toggle only between normal size and fully collapsed, skipping the minimized state inbetween?

Also, edits should not be possible when tracks are invisible. That can lead to accidental edits which can cause trouble if they go unnoticed. As an example of the behaviour, here I am selecting and splitting an invisible item:

[Mercado_Negro]

Originally Posted by Phazma

Also, edits should not be possible when tracks are invisible. That can lead to accidental edits which can cause trouble if they go unnoticed. As an example of the behaviour, here I am selecting and splitting an invisible item:

Agreed!

[sockmonkey72]

• + Mouse modifiers: support existing custom actions or scripts that use deprecated "set default mouse modifier for context" actions (actions no longer appear in the actions list, do not support menu/toolbar feedback, and will not support new mouse modifiers)

Thanks for this solution, well played.

[Edison]

@Devs

Please. Will the name for the .ReaperLangPack file be reaper70pre or reaper70+pre ? I particularly prefer +pre


Best regards,

[Yanick]

Is it possible somehow using the API to take the item lane under the mouse cursor? Otherwise, for now, my script for creating an item under the mouse cursor (primarily with a double click) does not work correctly. Thank you!

[Justin]

Originally Posted by daxliniere

I was previously using 6.78 release, so let's try those:

Broke:
6.78+0330
+0328
+0322
+0319
+0318

Working:
6.78+0317

Grr, it’s probably this:

Windows: update manifest to declare compatibility for new features

does it work if bridged?

[Yanick]

However, in addition to the fact that I need to take the desired item lane at the mouse cursor, I also need to create midi item in the desired item lane so as not to move it, for now using the CreateNewMIDIItemInProj function, the midi item is created in the lower item lane

[daxliniere]

Originally Posted by Justin

Grr, it’s probably this:

Windows: update manifest to declare compatibility for new features

does it work if bridged?

No dice, I'm afraid to say. I tried Separate process and Dedicated process and though neither cause the complete 'poof' crash, they take forever and then load 'offline'.

[Phazma]

Originally Posted by Yanick

Is it possible somehow using the API to take the item lane under the mouse cursor? Otherwise, for now, my script for creating an item under the mouse cursor (primarily with a double click) does not work correctly. Thank you!

I am unaware of your script but I have the same problem with the native action "Insert new MIDI item..." assigned to the double click. For this reason I have requested that they modify the native action. But if it is easier for the devs to make the lane under the mouse cursor accessible for scripts (so you could make this work as a script), then that would also be a great solution.

[Meo-Ada Mespotine]

+ Mouse modifiers: support existing custom actions or scripts that use deprecated "set default mouse modifier for context" actions (actions no longer appear in the actions list, do not support menu/toolbar feedback, and will not support new mouse modifiers)

looks like a good compromise...

[DerTonmeister]

thanks a lot for the hidden children option!!! Could we have a little visual hint for the hidden children? Thinking about an open folder symbol if they are visible and a closed folder in a different color if there are invisible child tracks?

[souk21]

Originally Posted by Vagelis

+ Tracks: add preference to not display tracks

Really nice to have as an option, thank you!

Originally Posted by Phazma

Can we please also have a preference to toggle only between normal size and fully collapsed, skipping the minimized state inbetween?

That would be amazing! Currently I'm using a hacky defer script that checks at each project change if I_FOLDERCOMPACT == 1 for the track under mouse cursor; just so the script can set it to 2.
That works but the result is not smooth and I guess not great performance wise


A couple things I noticed playing around:


The "drop" indicator is a bit hard to see with this color. Especially to differenciate between "tracks are going to go below" or "tracks are going to be children"




Button is still clickable when folder is collapsed




Last track resize indicator sometimes gets stuck (doesn't disappear) when mouse is in empty tcp area

[dom64]

A small workflow Nit Pick / feature request:




Though it's a small detail, it would be nice if the pan control was present regardless of the height setting of the MCP area. It's always shown in v6 theme, but in v7 them it vanishes after you reduce past a certain height.

[FeedTheCat]

Originally Posted by Phazma

Thanks, this is nice Can we please also have a preference to toggle only between normal size and fully collapsed, skipping the minimized state inbetween?

Yes please. I've never understood what the point of the middle state is. If you want to lock tracks to minimum height you could always just use "lock height" (not that I ever wanted to do this). I'm using a custom button tcp hack to remove the middle state, but I think a lot of people would appreciate an option to skip it (imo this option should even be enabled by default for new users).

Originally Posted by Yanick

Is it possible somehow using the API to take the item lane under the mouse cursor? Otherwise, for now, my script for creating an item under the mouse cursor (primarily with a double click) does not work correctly. Thank you!

You can calculate the lane under the mouse cursor using mouse position and track values such as "I_TCPH" and "I_TCPY". Then you can set the new item to the lane you want using item values such as "F_FREEMODE_H" and "F_FREEMODE_Y". Here are some functions to get you started, but I think there was a thread somewhere with more info:

function GetItemLane(item)
    local h = reaper.GetMediaItemInfo_Value(item, 'F_FREEMODE_H')
    local y = reaper.GetMediaItemInfo_Value(item, 'F_FREEMODE_Y')
    return y / h
end

function SetItemLane(item, lane)
    local h = reaper.GetMediaItemInfo_Value(item, 'F_FREEMODE_H')
    reaper.SetMediaItemInfo_Value(item, 'F_FREEMODE_Y', lane * h)
end

I think I speak for every scripter here that at some point we'd really like some API functionality that simplifies working with lanes. Won't be long until people start asking the "Can you update this to make it work with lanes" question.

[FeedTheCat]

Originally Posted by dom64

Though it's a small detail, it would be nice if the pan control was present regardless of the height setting of the MCP area. It's always shown in v6 theme, but in v7 them it vanishes after you reduce past a certain height.

I agree with you, but we're supposed to use the theme adjuster to hide elements in order to see the pan control at lower heights.

Btw, nothing has changed with the default MCP height, so new users installing REAPER v7 for the first time will see this:

[dom64]

Sure, it's going to be easier when theme adjuster is fully integrated, but either way, I think a mixer control panel does fundimentally need a pan control at all times.

I am very much looking forward to the visual confusion getting easier with v7 theme, but for now, I'm very easily perplexed whenever I look at anything. Little things like this would make it easier. All in good time though!

[strachupl]

* Includes feature branch: Development_Theme theme

ReaLimit - I found out that when track width in mixer is even, for example 80 then it displays okay but when it's odd, for example 81 then last linet of embedded UI of ReaLimit is bugged, also when plugins are shown next to each other then when ReaLimit width is odd then bug also appear. Probably this bug exists from begining of embeding gui in mcp for ReaLimit.

Second, you see on second track that an image for inserting new plugin is off from the mouse cursor in some cases.

Third is pink colors in corners:

[bwsd]

Originally Posted by Vagelis

v7.0pre6 - August 11 2023[*] * Includes feature branch: pooled and unpooled ARA edits
Generated by X-Raym's REAPER ChangeLog to BBCode

Add the action "Moove activ take to new ARA edit pool", Please

[musicbynumbers]

Originally Posted by Gass n Klang

thanks a lot for the hidden children option!!! Could we have a little visual hint for the hidden children? Thinking about an open folder symbol if they are visible and a closed folder in a different color if there are invisible child tracks?

Indeed, that would be great and again, thanks for adding this! Will attempt to try it asap on Monday

Another thing is does it act the same as if the tracks were still there for things like track and item grouping and razor edits that span multiple tracks? Are hidden items included?

[ferropop]

Does the "hidden children" function work separately from the Track Manager hiding? Like, if you manually hide tracks are they blanket hidden/unhidden by the new actions or does it operate differently?

Reason I ask - I use a hidden "last track in folder" track on all my buss folders, which guarantees that when flying tracks into the busses they visually "look" like the last track, but are actually second-last. The hidden last track acts as a buffer that forces things to to the bottom without "acting" like the last track in a folder, which has quirks.

If these actions just blindly unhide hidden children tracks, it'll affect this workflow - only reason I ask

[ktm]

[dangguidan]

+ Tracks: add preference to not display tracks in a folder when the folder is fully collapsed

It is recommended to display the contents of the folder in a thumbnail format, otherwise it may be deleted by mistake.

[klong]

I'd like to know more about the gain reduction metering with 3rd party plugins. How would I enable that, and are many plugins supported? I'm using mostly the UAD native plugins (Spark/UADx) currently..

EDIT: I'm guessing it's the same as with Reacomp etc where you just right click and "Show embedded UI in MCP/TCP". I'm guessing the 3rd party ones I've tried so far don't support this yet.

[ponknasty]

* Includes feature branch: FX containers

I found the Container in the plugins list. Not sure how to use it though or what it actually does?

[ponknasty]

Originally Posted by ponknasty

* Includes feature branch: FX containers

I found the Container in the plugins list. Not sure how to use it though or what it actually does?

Ok I found that each plugin in the container has different input and output settings as well as feedback channels. Very cool

[xpander]

Originally Posted by ferropop

Does the "hidden children" function work separately from the Track Manager hiding? Like, if you manually hide tracks are they blanket hidden/unhidden by the new actions or does it operate differently?

Reason I ask - I use a hidden "last track in folder" track on all my buss folders, which guarantees that when flying tracks into the busses they visually "look" like the last track, but are actually second-last. The hidden last track acts as a buffer that forces things to to the bottom without "acting" like the last track in a folder, which has quirks.

Afais, if you had a hidden child track as a last track in a folder, it will stay as the last track also with this option to not display tracks in fully collapsed folders. So when you e.g. drop other tracks into this folder, they will be second to last tracks and the hidden track will stay as the last track.

Originally Posted by FeedTheCat

If you want to lock tracks to minimum height you could always just use "lock height" (not that I ever wanted to do this). I'm using a custom button tcp hack to remove the middle state, but I think a lot of people would appreciate an option to skip it (imo this option should even be enabled by default for new users).

For me personally toggle to collapsed height is a crucial feature when dealing with dozens of folders with lots of tracks inside. I can get easily with just one click to a height where only essential info and controls are shown. I use it all the time like that.

Track height lock wouldn't work that easy and fast for that end. Instead of a single click on folder collapse button, I'd have to select all the child tracks, adjust their height and then lock them. And when I'd go for the super collapsed state or back to normal, I'd have to first select all the tracks again and unlock them. All that would make the folder handling pretty awkward and slow compared to how smoothly it works now. Locking the tracks heights is exactly what I don't want to do when rotating the folder heights.

As it is, I have no say about the suggested bypass option for the collapsed state.

[bolgwrad]

Originally Posted by ktm

]

Yes, the 'Do not display collapsed tracks' option hides items in the 'parent' track.

[musicbynumbers]

Folders - Please allow us the option of also skipping the intermediate step of "collapsed".

This is a step which causes me and people I know more grief then good and I've never had a reason to use it and when zooming it causes issues too.

If we could have an option to only have normal and fully collapsed/hidden then it would take the guessing out of what stage we are in

[musicbynumbers]

Originally Posted by bolgwrad

Yes, the 'Do not display collapsed tracks' option hides items in the 'parent' track.

Yep, I was about to report that too. Definitely need to see those items on the parent track

I use these parent items along with the track grouping to make "fake" folder items in a way that I can edit the child track items how I want and then use a parent item to then move and edit the child items as if it was in a folder.

so need to see the parent items

[_Stevie_]

Originally Posted by musicbynumbers

Folders - Please allow us the option of also skipping the intermediate step of "collapsed".

Yes, please, get's my vote as well!

[musicbynumbers]

Hmm.. Just tested track grouping for making parent folders that can move/copy the child items and realised there are two areas it doesn't work under still

1 - comp lanes, only the top lane is considered part of the track group editing system when it should be optional what is copied

2 - envelope items are not able to be consider real items so get cut up



Any discussions we can have on this stuff? A tick box here and there for making these optional? Or have I missed something?

I know I can use razor for this but would be nice to have these as options

Also.. Loving the reaper 7 theme though! The adjustments we can make are very cool!

[deeb]

Originally Posted by musicbynumbers

Folders - Please allow us the option of also skipping the intermediate step of "collapsed".

This is a step which causes me and people I know more grief then good and I've never had a reason to use it and when zooming it causes issues too.

If we could have an option to only have normal and fully collapsed/hidden then it would take the guessing out of what stage we are in

i would like this too.