With my Default V6 Modders' Supplies you've been able to choose from a selection of different elements to make your own mod theme based on the Default 6. Next step onward from that has been to radically increase the range of options and make it straightforward for ordinary users to choose and apply them. So, here is the initial offering of:
Theme Assembler
It is a script I have written that shows how the various options look, and automates the copying of the files into its own theme called 'Assembled_Theme' and updates it, in real time. It can also do some more complex stuff than that, like rewrite values in the rtconfig file (it will do more of that in future) but the key thing is that you don't need to understand what any of that means ...just point and click:
The script itself is very much a work in progress, but the theme it outputs is a fully functional Reaper theme based on the Default 6 theme, with complete 100%, 150% and 200% HiDPI support throughout and the usual theme adjuster.
- Choose Options > Show REAPER resource path in explorer/finder. Extract content of the zip (the 'theme_assembler.lua' file AND the 'theme_assembler' folder) into the 'scripts' folder there.
- Choose Actions > Show action list. In the bottom right choose New action > Load ReaScript. Choose theme_assembler.lua and click Open.
- In the actions list you'll now see Script: theme_assembler.lua. Choose it and click Run.
- First time you run the script, it will ask "Assembled theme not found. Create theme?" Click OK
- Click an element to see what choices there are, click a choice and the script will copy the files over and refresh the theme.
And that's it. Everything it does is just a change to the completely normal 'assembled_theme' that you will find in your color themes folder if you want to have a look, and you can rename that theme and mess with it further if you know how themes work.
If you come up with a combination you like, please do share a screenshot, it'll be fun to see what's working and what direction I should take more elements in!
--------------
Instructions are shown here if you don't like reading:
...thanks Reaperblog!
--------------
Current state (theme_assembler_0110)
The script should not misbehave at all, but in use it may appear pretty janky in places at this point, and its appearance is entirely placeholder to get the functionality working. I'm still new to this coding thing.
I've only done some of the elements. I'm never going to do all the elements.
Something weird going on with some of the shadows.
Limited range of choices, particularly for some elements, at this point. I'll just keep adding stuff as and when I feel the urge.
Some of the light background record arm buttons look bad.
AbFab!! Smashing!! The Moon landing of modern theming!!
Update: Error.
Under Win8x64: It does not create the assembled
theme resources folder at all.
Tried a few things like running Reaper admin rights
etc. but no go. I was going to create the folder myself but I do not know what structure is or what it is supposed to put there. Did everything
correctly triple checked. I will see about Win1022h2 I was just trying it out on my net pc first.
I thought maybe it had something to do with the mix of forward slashes and backslashes in the target path under an older ver of windows because it reads..(in the error msg):
'c:\users\xxx\appdata\roaming/reaper/colorthemes/assembled_resources....' not found, path does not exist.
but I went into terminal, and typed 'cd' and then the path all the way to color themes from root with an odd mix of forward and backslashes, which I have never done even since DOS 3.0 and lo and behold it found the dir no problem so not that, I learned something new.
With my Default V6 Modders' Supplies you've been able to choose from a selection of different elements to make your own mod theme based on the Default 6. Next step onward from that has been to radically increase the range of options and make it straightforward for ordinary users to choose and apply them. So, here is the initial offering of:
Theme Assembler
It is a script I have written that shows how the various options look, and automates the copying of the files into its own theme called 'Assembled_Theme' and updates it, in real time. It can also do some more complex stuff than that, like rewrite values in the rtconfig file (it will do more of that in future) but the key thing is that you don't need to understand what any of that means ...just point and click:
The script itself is very much a work in progress, but the theme it outputs is a fully functional Reaper theme based on the Default 6 theme, with complete 100%, 150% and 200% HiDPI support throughout and the usual theme adjuster.
- Choose Options > Show REAPER resource path in explorer/finder. Extract the zip into the 'scripts' folder there.
- Choose Actions > Show action list. In the bottom right choose New action > Load ReaScript. Choose theme_assembler.lua and click Open.
- In the actions list you'll now see Script: theme_assembler.lua. Choose it and click Run.
- First time you run the script, it will ask "Assembled theme not found. Create theme?" Click OK
- Click an element to see what choices there are, click a choice and the script will copy the files over and refresh the theme.
And that's it. Everything it does is just a change to the completely normal 'assembled_theme' that you will find in your color themes folder if you want to have a look, and you can rename that theme and mess with it further if you know how themes work.
If you come up with a combination you like, please do share a screenshot, it'll be fun to see what's working and what direction I should take more elements in!
--------------
Current state (theme_assembler_0529)
The script should not misbehave at all, but in use it may appear pretty janky in places at this point, and its appearance is entirely placeholder to get the functionality working. I'm still new to this coding thing.
I've only done some of the elements. I'm never going to do all the elements.
Something weird going on with some of the shadows.
Limited range of choices, particularly for some elements, at this point. I'll just keep adding stuff as and when I feel the urge.
YES! (-:
__________________
Win 10 I9 20 core 48g Ram always on the latest update
Hello guys,
Seems pretty awesome but doesn't seem to work with portable reaper install : https://imgur.com/a/DeLngaf
Seems to be the same issue as Fouadsmy
I'm on windows 10 1809, Repaer 6.58 and I've tried 0.530b and 0.529b... any ideas ?
Ok so after some researches and tweaks, it seems the problem comes from path parsing.
May I ask you to try some improvements dealing with something like that :
Code:
-----------------------------------------
--- || PLAYING WITH PATH AND PARSE || ---
-----------------------------------------
--[[
Documentation about debug.getinfo ([thread,] f [, what])
@tparam int threadcall stack of the given thread: level 0 is the current function (getinfo itself); level 1 is the function that called getinfo
@tparam char what
Each character in the string what selects some fields of the structure ar to be filled or a value to be pushed on the stack:
'n': fills in the field name and namewhat;
'S': fills in the fields source, short_src, linedefined, lastlinedefined, and what;
'l': fills in the field currentline;
't': fills in the field istailcall;
'u': fills in the fields nups, nparams, and isvararg;
'f': pushes onto the stack the function that is running at the given level;
'L': pushes onto the stack a table whose indices are the numbers of the lines that are valid on the function. (A valid line is a line with some associated code, that is, a line where you can put a break point. Non-valid lines include empty lines and comments.)
source : http://www.lua.org/manual/5.4/manual.html#pdf-debug.getinfo
]]--
--[[
About require
Each component in the path is a file name containing optional interrogation marks. For each component, require replaces each `?´ by the virtual file name and checks whether there is a file with that name; if not, it goes to the next component. The components in a path are separated by semicolons (a character seldom used for file names in most operating systems).
For instance, if the path is `` ?;?.lua;c:\windows\?;/usr/local/lua/?/?.lua `` then the call require"lili" will try to open the following files:
```
lili
lili.lua
c:\windows\lili
/usr/local/lua/lili/lili.lua
```
source : https://www.lua.org/pil/8.1.html
]]--
--[[
Regular expression in LUA, patterns.
- http://wxlua.free.fr/Tutoriel_Lua/Tuto/Strings/strings6.php
- https://learntutorials.net/fr/lua/topic/5829/correspondance-de-motif
]]--
local sep = package.config:sub(1, 1) -- separators depend on operating system, windows = \, linux and osX = /
local script = debug.getinfo(1, 'S').source:sub(2) --absolute path + filename of current running script
local pattern = "(.*" .. sep .. ")" -- every char before sep
local basedir = script:match(pattern) -- rootpath of current running script
local filename_without_ext = script:match("(.+)%.[^%.]+$")
package.path =string.format(basedir.."?.lua")
And if I may add another suggestion, perhaps you should thing about avoiding hard coded path into the code.
Defining a constant at script beginning should avoid you terrible headache !
For example :
I'm pretty new to this DAW thing, I'm pretty janky ;D but eh you've done a great job Bro!!! Nice one, have a great weekend!!!
NB.
I tried my hand at coding and though I enjoyed it, it's too much to keep up with being a bit older, I got my head around it reasonably and I know it can be tricky so eh thanks for your effort, much appreciated! <3
Absolutely fantastic theme, this is what reaper needs as the default.
I am on windows 10 and have found just a couple of issues.
first one, when in the mix window, the faders do not appear.
I am only getting a fader appearing on the master track, on all other tracks the fader does not show/display at all.
I have tried to toggle between the different fader types/options, but still nothing appears.
Second one, in the mix window the track names do not display correctly.
If you double click on the track name, you can see that the track name is correct, however all of the track names do not show the full name correctly, only part of the name.
Other than that everything seems to be working great.
This looks gorgeous; a wonderful and modern flat take on WT's default theme. Great job! Any chance you could please share this theme?
I'd love to once it's finished!
@White Tie ;
There seems to be a problem with the FXlist not showing up if the track tinting (I guess that's the parameter) is set to 0. Mind you, I'm not using the latest release. Just wondering if it's been fixed (or if it's at least in your radar)?
Edit: Never mind! I see it's fixed in later releases! Thanks!
first one, when in the mix window, the faders do not appear.
I am only getting a fader appearing on the master track, on all other tracks the fader does not show/display at all.
I have tried to toggle between the different fader types/options, but still nothing appears.
Second one, in the mix window the track names do not display correctly.
If you double click on the track name, you can see that the track name is correct, however all of the track names do not show the full name correctly, only part of the name.
Yeah. I have both these issues. No faders except on the master. Plus track names just show a fragment of what should be there. If you double click as if to change the track name the proper text is still there. Just not showing when it should.
WT Theme Assembler Script
...just point and click:
Hybrid Mode
