Default 7.0 Theme Adjuster v.1005

[White Tie]

Be running Reaper v7.0rc7.

Installing & Running the script

DOWNLOAD

- Choose Options > Show REAPER resource path in explorer/finder. Extract content of the zip (the 'Default_7.0_theme_adjuster.lua' file AND the 'Default_7.0_theme_adjuster resources' folder) into the 'scripts' folder there.

- Choose Actions > Show action list. In the bottom right choose New action > Load ReaScript. Choose Default_7.0_theme_adjuster.lua and click Open.

- In the actions list you'll now see Script: Default_7.0_theme_adjuster.lua. Choose it and click Run, or (while using the theme) go to Options > Themes > Theme Adjuster / Color Controls.

Changelog

• User chosen background colour also affects track index area background
• Mixer folder balancing by varying track name height

I missed the RC release (timezones blah blah) so the input heights fixes will come later.

[airon]

The array of options is working very well for me. I've already discovered several workflow enhancing things I can do here on both the TCP and MCP. Thank you very much for these enhancements.

Here is a report on the viability of the parameter knob area design. If this is an inappropriate area to post about this, please tell me and I'll move the post.

7.0 RC7, theme adjuster v.1005
As you well know I automate stuff a lot. Checking the readability of the parameter knobs there are some issues for me.

In this screenshot I'm using the vanilla theme with an adjusted sidebar width (100 instead of 82 pixels). Layout C for the MCP and TCP for some reason though Reaper only indicates the global layout default if checked.

The track is set to Latch Preview. Four parameters are 'touched', as can be seen on the MCP on the left.

The issue is the readability of parameter knob descriptions and the ease with which I can locate the touched parameters at a glance. The backgrounds of the parameter knob descriptions makes this very difficult.


I have no issue with the backgrounds of the parameters of the 'bypassed' effect.

[White Tie]

Above, from your screenshot, is not correct and I can't duplicate it here; the parameters are set to be displayed across two lines, like this:



Could you try temporarily disabling your reaper.ini, or with a portable install, to see if the same thing happens?

[airon]

Here's the result with a fresh portable installation of v7.0 RC7. No tweaks made.

I used ReaEQ to create a bunch of parameter knobs, wrote a little automation and 'touched' a few controls to show off the effect.

https://i.imgur.com/6sx1qnP.png

[airon]

I may have located the culprit.

Windows Scaling.

Mine was set to 125%, since I'm using a 1440p 27 inch screen. When that is switched to 100%, it looks as it does in your screenshot.

Bit of a conundrum. I'll try messing around with the advanced system tweaks in Preferences/General.

The parameter knobs descriptions aren't easy to see. I had some luck changing the colours to better stand out from those two background colours, but it's still a fight.

[White Tie]

Yes, confirmed that 125% is the cause. It shouldn't do that.

[airon]

The 150% C layout of the MCP is a little better.

https://i.imgur.com/lZwvWGt.png

[airon]

Originally Posted by White Tie

Yes, confirmed that 125% is the cause. It shouldn't do that.

On both the clean portable install and my custom v7 installation(scripts,extensions,etc.) they split up to two lines on both the v7 and v6 theme. I reckon they'll be back to non-split on 125% scaling on Windows 10.

[White Tie]

Seems like a Reaper bug, leave it with me.

[airon]

Quick retest on 125% scaling.

The bug does not show up for the MCP layout C 150%. Two line text. Perhaps that helps.

[smandrap]

Quick reminder about making these indicators smaller:



Also found another reason for this. Here i have 4 tracks with default layout B. Track 3 has a compressor: the not soloed indicator is smaller than the others due to the GR indicator.



Now... scale this situation up and:



It looks a little messy in my opinion.

[Mercado_Negro]

Any chance of having background fill for sends?

https://forum.cockos.com/showpost.ph...9&postcount=23

[Thonex]

Originally Posted by White Tie

[size=+2][b][*] User chosen background colour also affects track index area background

Hey WT,

Just FYI... I'm not finding a way to change the Track Index background color with the TCP All Layouts. Or to get them to match in TCP All Layouts.

The only way I can get them to be the same color is if I go to Global and change the Custom Color Strength to 100%


Cheers,

Andrew K

[White Tie]

Originally Posted by smandrap

Quick reminder about making these indicators smaller

I made them dimmer, not smaller. It was a good suggestion that they now look different, but having them much bigger than they were in v6 is a specific user request, for the other side of 'they all look solo'd' vs. 'I didn't realise this track was solo'd', which is I think where we are now.

Originally Posted by smandrap

It looks a little messy in my opinion.

I agree, but that's all automatic Reaper sizing I'm afraid.

Originally Posted by Thonex

I'm not finding a way to change the Track Index background color with the TCP All Layouts. Or to get them to match in TCP All Layouts.

The only way I can get them to be the same color is if I go to Global and change the Custom Color Strength to 100%

This should be what you are seeing : the two areas now have the same underlying colour, as chosen by 'TCP background colour'. Custom colour is applied 100% to the index area, and 'custom colour strength' amount to the rest, the light selected overlay is applied 0% to the index area, and 'selection overlay strength' amount to the rest.

[smandrap]

Originally Posted by White Tie

I made them dimmer, not smaller. It was a good suggestion that they now look different, but having them much bigger than they were in v6 is a specific user request, for the other side of 'they all look solo'd' vs. 'I didn't realise this track was solo'd', which is I think where we are now.

Thanks, i understand. So i guess that due to automatic reaper sizing there's no way to achieve a middle ground where the not soloed indicator is always the size of the one with the GR meter, regardless of the presence of the latter, right? This would solve the nitpick shown in the second image in the above post

[Bassman002]

HI

On starting the lua I get an error:

"...attempt to index a nil value, field '?'"


Bassman.

[smandrap]

Originally Posted by Bassman002

HI

On starting the lua I get an error:

"...attempt to index a nil value, field '?'"


Bassman.

Make sure you’re using reaper 7rc7 and using the Default theme

[dangguidan]

The display of the track segmentation line is different on both computers, and the system is both Win8.1. Why?

[PhelixK]

Originally Posted by dangguidan

The display of the track segmentation line is different on both computers, and the system is both Win8.1. Why?

Are you comparing the exact same theme version?
Since rc7, the minimum track height has been slightly reduced in the dev theme (not mentioned in the changelog). This could be the cause of what you're seeing.

[dangguidan]

Originally Posted by PhelixK

Are you comparing the exact same theme version?
Since rc7, the minimum track height has been slightly reduced in the dev theme (not mentioned in the changelog). This could be the cause of what you're seeing.

Yes, the versions of Reaper are the latest V7 rc8, and the themes are all default.

[PhelixK]

Originally Posted by dangguidan

Yes, the versions of Reaper are the latest V7 rc8, and the themes are all default.

Okay, if it really is the same theme release, then I have no idea what the difference could be caused by. Just as an experiment, I would remove the theme and restart REAPER so that the latest theme version is re-installed on both machines.

[Bassman002]

Originally Posted by smandrap

Make sure you’re using reaper 7rc7 and using the Default theme

That's exactly what I have!

Error...(786)

Bassman.

[White Tie]

Originally Posted by dangguidan

The display of the track segmentation line is different on both

Theme Adjuster > Track Control Panels > All Layouts > Divider Opacity

[dangguidan]

Originally Posted by White Tie

Theme Adjuster > Track Control Panels > All Layouts > Divider Opacity

Alright, thank you!

[robgb]

Is there any chance that you'll ever be adding separators to this default theme? This is something I think is really needed.

[Daodan]

Originally Posted by robgb

Is there any chance that you'll ever be adding separators to this default theme? This is something I think is really needed.

Don't like real track spacers?

[smda123]

Is it possible to have a color background for FX Section?

[Subz]

Am I the only one who thinks the MCP Default "Folder Indent" should be 0?

Personally, I have TCP & MCP to 0,

Just a Thought! MCP looks UGLY with folder tracks currently at default settings IMO

Subz

[robgb]

Originally Posted by Daodan

Don't like real track spacers?

Don't track spacers affect ALL the tracks? I want to be able to separate groups of tracks by using a blank separator. Many themes have them. Not sure why the default one doesn't.

Am I misunderstanding how the track spacers work?

[alexnoclain]

Good morning,
First of all, I congratulate you on the dedication and dynamism of your work, which is also made collaborative via this forum.
So I give you my feedback.

I'm bothered by the clarity of the pan button design. The dot indicating its position is not sufficiently visible. Furthermore it seems that its opacity is not 100%, and the fact that it follows the track color makes it even less visible.

You understand my preference, that the attention given to the redesign of the volume fader is the same as that of the pan button.

Thank you for your attention and have a pleasant day

[smandrap]

Originally Posted by robgb

Don't track spacers affect ALL the tracks? I want to be able to separate groups of tracks by using a blank separator. Many themes have them. Not sure why the default one doesn't.

Am I misunderstanding how the track spacers work?

I think Daodan is talking about these:

[Daodan]

Originally Posted by robgb

Don't track spacers affect ALL the tracks? I want to be able to separate groups of tracks by using a blank separator. Many themes have them. Not sure why the default one doesn't.

Am I misunderstanding how the track spacers work?

Right click track > Visual spacers
Insert spacer before or after (or both) selected track

[Daodan]

Originally Posted by smandrap

I think Daodan is talking about these:

Yap. Thanks

[FeedTheCat]

In this case fx/sends etc. are not displayed at min track height:

[Pink Wool]

When the script window is open and not tall enough, this "action" breaks parts of it (on Windows 10) :

[robgb]

Originally Posted by smandrap

I think Daodan is talking about these:

This works fine, but requires me to add the spacer after the fact rather than incorporate it into a project template, unless I include a track with the spacer in the template. I can't open a trackless project template like I can if separators are used. It also doesn't allow me to hide the spacers in the TCP, if I want to.

Not the end of the world, but separators are more practical, IMO.