v6.30rc6 - June 25 2021

[xpander]

v6.30rc6 - June 25 2021

* Includes feature branch: render normalization
* Includes feature branch: EEL2 x86_64/SSE
* Includes feature branch: VST3 bridging
+ JSFX: add gfx_ext_flags, to tell plugins that they are embedded in TCP or MCP
# JSFX: hide loudness meter settings button when embedded
# JSFX: improve loudness meter adaptive grid spacing
# JSFX: loudness meter display improvements at small sizes
# JSFX: reduce lag when showing multiple sliders via slider_show()

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

[IXix]

+ JSFX: add gfx_ext_flags, to tell plugins that they are embedded in TCP or MCP

Any more info on that? Can you tell which panel the plugin is embedded in? Is it possible for a plugin be in the TCP but not the MCP? Haven't really looked into the embedding thing yet.

[mschnell]

Originally Posted by IXix

Is it possible for a plugin be in the TCP but not the MCP?

It's either or or none. But not both.

-Michael

[Phazma]

Originally Posted by IXix

Is it possible for a plugin be in the TCP but not the MCP?

Actually it can only be embedded in the TCP or in the MCP, both is not possible. If you for example first embed it in the TCP and afterwards in the MCP, the embedded GUI will disappear from the TCP. I always wondered why it can not be chosen to be embedded in either one or both but surely there is some reason..

Edit: Michael was a tad faster

[Zeno]

Originally Posted by xpander

+ JSFX: add gfx_ext_flags, to tell plugins that they are embedded in TCP or MCP
# JSFX: hide loudness meter settings button when embedded
# JSFX: improve loudness meter adaptive grid spacing
# JSFX: loudness meter display improvements at small sizes

Thanks Devs!
One last thing:
With the embedded loudness meter in the MCP, no meter grid is displayed for tracks and also for the master (depending on font size). Does this have something to do with whether the LUFS scale values displayed to the right of the grid fit the embedded graph? Would it be possible to display the grid line even if no values are visible on the right of the graphic?

[Meo-Ada Mespotine]

In regards of GetSetProjectInfo_String:

When I run the following with an item selected:

Retval, RetString = reaper.GetSetProjectInfo_String(0, "RENDER_STATS", "42437", true)

the function returns the dry-render-stats.

Now, when I rerun the function without an item selected, no dry render happens, which is cool. But: the function still returns stats, but the stats for the first dry render, not the second dry render that I tried but didn't happen.
So it currently gives the impression of a dry-rendering that happend with returned stats where it actually didn't.

So I think, if no dry-render happens, retval should be false and when a dry render happens, retval should be true.
That way I can see, that a dry render didn't happen, so the stats are probably useless to me and I should give a warning to the user of my script that they should set the selection accordingly.

I also noticed the same problem with the other dry-render-actions and returning false as retval in the case of no-dry-render should solve this completely.

Aside from that, I think dry-render and loudness stats is perfectly done from an ReaScript-pov.

[IXix]

Originally Posted by mschnell

It's either or or none. But not both.

Ha, that's the opposite of what I thought it would be! Good that the plugin can know though.

[ferropop]

Weird bug with "Offset overlapping media items vertically":



1. Delete an item while "Offset overlapping media items vertically" is engaged
2. All items randomly shift to the right (!)
3. Undo, turn off "Offset overlapping media items vertically"
4. Delete same item, everything stays intact

Edit: there's absolutely no ripple editing involved

[schwa]

Originally Posted by ferropop

Weird bug with "Offset overlapping media items vertically":

The item lanes feature is not in the RC builds, so this comment is not in the right place. But in any case it's not a bug, the items aren't shifting to the right, they are just resetting their vertical offset because the first overlapping item changed.

[PhelixK]

# JSFX: hide loudness meter settings button when embedded

This is more user-friendly, instead of having to exit the menu to hide the (inactive) settings button.

– it's a pity the Mono indicator is also hidden now. If possible to have just that icon when embedded, I suggest to put it back

[bolgwrad]

+ JSFX: add gfx_ext_flags, to tell plugins that they are embedded in TCP or MCP

That seems to have fixed the text overlap, thanks! Loudness in the Master MCP is a killer function.

[ferropop]

Originally Posted by schwa

The item lanes feature is not in the RC builds, so this comment is not in the right place. But in any case it's not a bug, the items aren't shifting to the right, they are just resetting their vertical offset because the first overlapping item changed.

My bad, I'll save this for the next dev cycle.

Still confused about this behaviour, is that option not strictly a visual thing? Maybe I'm confused by the old behaviour of showing overlapping items in lanes? Regardless, will save for next dev.

[schwa]

Originally Posted by ferropop

My bad, I'll save this for the next dev cycle.

Still confused about this behaviour, is that option not strictly a visual thing? Maybe I'm confused by the old behaviour of showing overlapping items in lanes? Regardless, will save for next dev.

It's strictly visual. Your media items are not moving to the right, they are just swapping which items are above and which items are below.

[MrTsonts]

Originally Posted by ferropop

Weird bug with "Offset overlapping media items vertically":

All items randomly shift to the right (!)

There is no displacement to the right.
Items that are earlier in time are always higher.

[schwa]

Acknowledging again that this isn't the right place for this discussion, that behavior is why we tried to kill off the "show overlapping items in lanes" option, which is now reincarnated as "offset overlapping items vertically" (in the +dev builds, but not in this RC build and not in a release build any time soon). It's easy for the autoarranging to create the visual illusion that items are moving in time.