v7.03+dev1107 - November 7 2023

[smandrap]

v7.03+dev1107 - November 7 2023

• * Includes feature branch: FX envelope options for AI combining
• * Includes feature branch: ReaSurround support for 128 inputs
• + API: fix accessing metronome, master track state via projectconfig_var_getoffs/projectconfig_var_addr
• + FX Containers: improve display in TCP/MCP FX context menu [t=284678]
• + Lanes: add action to move items up if possible to minimize lane usage
• + Lanes: fix editing vertical edge of razor edit on fixed lane tracks
• + Linux: improve support for ini files which are symlinks [t=283160]
• + ReaScript: get_config_var_string() can now query project state in addition to global state
• + Recording: improve handling of user deleting or reordering tracks while recording [t=284363]
• + Tooltips: improve visibility for some instances e.g. floating toolbars
• # Preferences: preference to limit edge edits to source media content does not apply to click source, LTC, or empty media 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

[smandrap]

Originally Posted by smandrap

# Preferences: preference to limit edge edits to source media content does not apply to click source, LTC, or empty media items

Thanks a lot. Could this also apply to subprojects without a corresponding RPP-PROX file? When scoring to picture and using a master project with subprojects acting as single pieces of music, it would be useful to have the subproject media items not be unaffected by edge limit edits for easier visual referencing.

Even better would be if the subproject items were limited to their =START and =END markers.

[juan_r]

Originally Posted by smandrap

[*]+ Tooltips: improve visibility for some instances e.g. floating toolbars

Maybe a tooltip could be shown for plugin names in the FX list too, considering that in some cases the left pane can't be stretched out to read the full name?

Relevant nitpick:
https://forum.cockos.com/showthread.php?t=284142

[Daodan]

• + FX Containers: improve display in TCP/MCP FX context menu [t=284678]

WOW! Thank you!

[fonolit]

Originally Posted by smandrap

Thanks a lot. Could this also apply to subprojects without a corresponding RPP-PROX file? When scoring to picture and using a master project with subprojects acting as single pieces of music, it would be useful to have the subproject media items not be unaffected by edge limit edits for easier visual referencing.

Even better would be if the subproject items were limited to their =START and =END markers.

What do you mean with "without a corresponding RPP-PROX file"?

I use subprojects exactly for the same reason as you - scoring a picture.
I'm running 7.03+dev1107 and edge limiting DOES APPLY to subproject media items respecting START / END markers (which is good!).

[fonolit]

[*]# Preferences: preference to limit edge edits to source media content does not apply to click source, LTC, or empty media items

Another one on this topic:

When moving item contents with edge limiting turned on, I would expect the media edge to move together with the content or to be trimmed automatically after move content operation.



Further thinking about this... Maybe this could be optional because it is not easily reversible and could bring some confusion (it would change the length of the item and moving content to the original position would not make it longer again).

[smandrap]

Originally Posted by fonolit

What do you mean with "without a corresponding RPP-PROX file"?

A subproject which has not been rendered yet. Rendered subprojects have RPP-PROX as format

Originally Posted by fonolit

I use subprojects exactly for the same reason as you - scoring a picture.
I'm running 7.03+dev1107 and edge limiting DOES APPLY to subproject media items respecting START / END markers (which is good!).

It doesn't if the subproect hasn't been rendered.

[sockmonkey72]

My custom theme is behaving strangely on a retina display. On an external display, the images:

lane_solo_up.png
fixed_lanes_big.png
fixed_lanes_hidden.png
fixed_lanes_one.png
fixed_lanes_small.png
lane_solo_down.png
lane_solo_off_indicator.png
lane_solo_off.png
lane_solo_on_indicator.png
lane_solo_on.png

Look normal, perfect:



On a retina display:



No difference beyond moving the window to the different display -- these images (and only these images AFAICT) are not being autoscaled. Is this a me problem or a you problem? This theme does not have any 150 or 200 assets, these are all images at the top-level; using the corresponding image files from Default 7 does not solve the issue.

[fonolit]

Originally Posted by smandrap

A subproject which has not been rendered yet. Rendered subprojects have RPP-PROX as format

It doesn't if the subproect hasn't been rendered.

I see, makes sense...

[cyril_meysson]

Originally Posted by smandrap

• + FX Containers: improve display in TCP/MCP FX context menu [t=284678]

Works perfectly, thanks a lot!!

[ferropop]

Hi devs, wanted to test something and randomly grabbed a collection of audio files.

One of them is .M4A, and I noticed while comping that this happens specifically with that file :



It's the only non-WAV of the bunch.

[X-Raym]

# Preferences: preference to limit edge edits to source media content does not apply to click source, LTC, or empty media items

+1, makes sense ! Only audio with source is really needed.

+ FX Containers: improve display in TCP/MCP FX context menu [t=284678]

I hope I'm not too off-topic,
but this FR about FX Containers display definitely worth taking a look:

• FX chain design: Tree view and foldable FX containers

Especially to avoid such issue.


I bring that here cause improvements on the TCP/MCP FX Context menu might somehow be related to how it is displayed in the FX chain as well.

Thx!

[DerTonmeister]

Originally Posted by smandrap

v7.03+dev1107 - November 7 2023
[*]# Preferences: preference to limit edge edits to source media content does not apply to click source, LTC, or empty media items

D'accord with click source and ltc. I think there are situations where you want empty media items to be trimmed. E.g. if you use them as markers with large text or so.

[smandrap]

Also happens with audio items. Is this intended? If so i'm surely missing something, why?

[STOP]

Originally Posted by X-Raym

• FX chain design: Tree view and foldable FX containers

Especially to avoid such issue.
Thx!

+1

[Allspice]

This appears to fix this issue:

https://forum.cockos.com/showthread.php?t=284712

[schwa]

Originally Posted by ferropop

Hi devs, wanted to test something and randomly grabbed a collection of audio files.

Fixing, thanks!

[Reflected]

Reaper crashed and I lost my project after using a bit more than 20 nested containers :|

EDIT: I managed to reproduce the crash:

24 nested containers = complete freeze and crash!

[daxliniere]

With the recent changes to collapsed folder views, is there a way I can make it so that when I select a collapsed folder track and insert a new track via action that the new track is placed OUTSIDE of the folder?

[Meo-Ada Mespotine]

Does the change of get_config_vars_string() mean, it returns now the value of all config vars or are some still excluded?

[Kenny Gioia]

Originally Posted by daxliniere

With the recent changes to collapsed folder views, is there a way I can make it so that when I select a collapsed folder track and insert a new track via action that the new track is placed OUTSIDE of the folder?

That's what I'm already getting. What action are you using?

[musicbynumbers]

Didn't have this issue in reaper 6 but I have found that when switching between screens sets (that also have different TCP widths saved within the too). It can make nearly all of the track icons on the TCP (mute, solo, volume slider etc) dissappear until I manually adjust the TCP width. At which point the icons come back.

This only happens when changing screen sets.

Maybe it's because the arrange window also gets moved to a different monitor. I'll try keeping it on the same one later

[bolgwrad]

Originally Posted by Kenny Gioia

That's what I'm already getting. What action are you using?

Yep, Ctrl+T works fine as desired.

[Embass]

[schwa]

Originally Posted by Embass

screencap

Argh, that's an annoying regression in 7.03. Fixing, thanks for the report.

[Embass]

[Stroudy]

This zoom issue with lanes is still persistent.

Big lanes vs Small Lanes

[Stroudy]

I'm still seeing inconsistent lane placement of new items/takes when I record with a pre-roll vs auto-punch time selection. I don't think I've Adequately explained myself in previous posts - I hope this video gets my point across.

[schwa]

Originally Posted by Stroudy

I'm still seeing inconsistent lane placement of new items/takes when I record with a pre-roll vs auto-punch time selection. I don't think I've Adequately explained myself in previous posts - I hope this video gets my point across.

Thanks for the video. As you describe, REAPER is making the lane selection based on the start/end of the raw recording, rather than the start/end after it's trimmed to fit the autopunch area. We'll see if we can improve this behavior.

[sockmonkey72]

Originally Posted by sockmonkey72

My custom theme is behaving strangely on a retina display. On an external display, the images:

lane_solo_up.png
fixed_lanes_big.png
fixed_lanes_hidden.png
fixed_lanes_one.png
fixed_lanes_small.png
lane_solo_down.png
lane_solo_off_indicator.png
lane_solo_off.png
lane_solo_on_indicator.png
lane_solo_on.png

Look normal, perfect:

...

On a retina display:

...

No difference beyond moving the window to the different display -- these images (and only these images AFAICT) are not being autoscaled. Is this a me problem or a you problem? This theme does not have any 150 or 200 assets, these are all images at the top-level; using the corresponding image files from Default 7 does not solve the issue.

This looks like it's related to the version setting. I've attached a toy theme which exhibits the issue on a Fixed Lanes track.

... or maybe it's "use_pngs 1" -- it's enabled automatically at version 5+ apparently. Disabling the version and enabling "use_pngs 1" causes the problem, as well.

Removing the 150 and 200 folders from the Default 7 theme also results in the same behavior, so I'm going to guess that this is simply a bug.

[Stroudy]

Originally Posted by schwa

Thanks for the video. As you describe, REAPER is making the lane selection based on the start/end of the raw recording, rather than the start/end after it's trimmed to fit the autopunch area. We'll see if we can improve this behavior.

Oh, OK. I thought it was something else, as all the recordings in the video were of the same length. I guess the files are marked differently (or something?) depending on whether the source length is longer because of the recording pre-roll or longer because of the play position using auto-punch.

Anyway - thanks for taking a look

[Sexan]

GetLastTouchedFX() not working when in container? Returns 0 always for fx_id for child fx

[Justin]

Originally Posted by Sexan

GetLastTouchedFX() not working when in container? Returns 0 always for fx_id for child fx

From the docs:

Deprecated, see GetTouchedOrFocusedFX

[Sexan]

Originally Posted by Justin

From the docs:

AAAhh... sorry been using xrayms online docs, was not flagged as deprecated sorry

[thommazk]

Originally Posted by thommazk

Still on the v7 MIDI Editor features, this issue was introduced with the new Selecting a single note sets the channel for new events enabled option.


When enabled, clicking and dragging a midi note from the currently selected channel doesn't move it unless I try again.

I just noticed that this still happens if you have Reaticulate opened.

[Buy One]

So did get_config_var_string() supporting project config variables not made the final 7.03 release?

Seems it didn't.