New version and new Video Demo (please watch it cause a help file is not included)
- you can create your own tags, those will be saved per project, so any project could have a different set of tags
- A “slim edition” of mixer manager that doesn’t take much space
- you can tag tracks as “hidden” so that they don’t show up in the mixer unless you press “show hidden”.
well actually "My" sounds a bit outrageous since I've been "stealing" pieces of code from most of you great coders.
Yet... I made it and it works.
The mixer gets busy quite easily and I don't like folders so now I can let the mixer show only what I need
(ex: just vocals, all the aux channels, drums + drum bus + drum aux channels)
If you want to change de default tags just edit the first 10 lines of code.
So you define tracks in groups, then hide/show them?
Then, it reques too much mess and unnecessary clicking, when you are working on project with 100+ tracks (nowadays it is usual situation). Folders ARE good and they keep project clean and easy to edit. You can easily build/edit a similar script to hide/show tracks in TCP/MCP, based on they parent folder. For sure, better and cleaner improvement.
A track can belong to multiple "groups" at the same time, you can decide it when you name it or whenever, you can move it to another "group" with a click, etc
I find it very convenient and flexible, still I agree that a few more shortcuts could bel welcome
And those labels can be changed, you could make a series of groups for different submixes, etc
simple example is a shared reverb
But you can go further and group all the tracks that have some impact on the low end (could be cellos, electric bass, kick drum) and still have your string section group (with the same cellos + violins etc)
and your kick with the rest of your drums elements, aux and bus. And so on
Simply download the lokasenna gui files (core.lua, slider.lua, etc) and put them in your reaper script folder. Mixer manager should share the same directory (so, again, the script folder).
Something like this is already implemented by Heda in his TrackInspector. A feature called TAGS.
To save some clicks, for tracks like reverbs, you can do automatic detection. Also, you can detect tracks based on e.g. track layout name, track color etc. I have automatic TCP hiding of separators and sends without automation.
Yes heda it s powerful but it requires you to work with it, get deep into it. All I need is some order on the mixer (scrolling it s a pain...). However I m working on it right now adding personal presets per project and a few other things. I ve started lua just 3 days ago so just bare with me )
Then again, i m not sure heda track manager can have multitags per track
Quote:
Originally Posted by bFooz
Something like this is already implemented by Heda in his TrackInspector. A feature called TAGS.
To save some clicks, for tracks like reverbs, you can do automatic detection. Also, you can detect tracks based on e.g. track layout name, track color etc. I have automatic TCP hiding of separators and sends without automation.
If you're loading the library files with reqs() like in the example scripts, Script Compiler should be able to automatically pick those up for you. Let me know if it gives you any trouble.
If you're loading the library files with reqs() like in the example scripts, Script Compiler should be able to automatically pick those up for you. Let me know if it gives you any trouble.
Hi Thx Marcoctn & Lokasenna,
I clicked on your link...Am I supposed to copy all that script into a notepad file and save it to reaper reascript? I'm not sure how to get all these files I need...Sorry I'm a neebie when it comes to scripts...haven't dove it yet (-;
Ok, I've just uploaded the first update (same link on top). It should work without Lokesanna externals.
Let me know how it goes
(major update in a few hours with new features)
Quote:
Originally Posted by onewayout
Hi Thx Marcoctn & Lokasenna,
I clicked on your link...Am I supposed to copy all that script into a notepad file and save it to reaper reascript? I'm not sure how to get all these files I need...Sorry I'm a neebie when it comes to scripts...haven't dove it yet (-;
Ok, I've just uploaded the first update (same link on top). It should work without Lokesanna externals.
Let me know how it goes
(major update in a few hours with new features)
Thx it opens up Perfect!!
I'll let you know how it works...I had a pretty big mix this morning but will now do some video work until I Mst that one and get back to another mix...Looking Fwd to it!!
Hi, the short answer is... I don't know.
Hope there's someone more competent than me reading this question cause I would really like to know if it s easily implementable.
However, a less elegant (but still effective) way could be to have 8 different scripts to load the 8 slots.
So...
1) you open Mixer Manager and you set your tags. Once done you can close it
2) you have in your action list 8 different scripts already assigned to a key or a controller to load the different slots.
I could make it if you are interested.
Quote:
Originally Posted by saastara
Could the script be modified to allow the tags to be triggered via midi / press of a button?
I'm having problems clearing my choices and also when I take trks off mix view and reassign my tags the trks I just took off of mix view still come back when I change my choice...Hope that makes sense...in other words I'm re-choosing lets say drums or buss' or whatever I think I have cleared them but my old choices still come up...
would you mind send me you .rpp file?
it's the best chance I have to figure out what happened
send it to marcoctn at hotmail dotcom
cheers!
Quote:
Originally Posted by onewayout
Thx again marcoctn for this feature!
I'm having problems clearing my choices and also when I take trks off mix view and reassign my tags the trks I just took off of mix view still come back when I change my choice...Hope that makes sense...in other words I'm re-choosing lets say drums or buss' or whatever I think I have cleared them but my old choices still come up...
If you're loading the library files with reqs() like in the example scripts, Script Compiler should be able to automatically pick those up for you. Let me know if it gives you any trouble.
HI Lokasenna,
Hey I've been needing 2 extra boxes on this script for a loooooong time....I tried adding lines of code but I don't know anything about this...Is it possible?
Hey I've been needing 2 extra boxes on this script for a loooooong time....I tried adding lines of code but I don't know anything about this...Is it possible?
Thx. Jeff
Hi Jeff! I am not sure if Lokasenna is active in forum again.
I know he took a break last year... I think Mespotine(Ultrashall)
have been kind to continue the work with the Lokasenna GUI.
Maybe you could ask question in Lokasenna GUI thread?
Hi Jeff! I am not sure if Lokasenna is active in forum again.
I know he took a break last year... I think Mespotine(Ultrashall)
have been kind to continue the work with the Lokasenna GUI.
Maybe you could ask question in Lokasenna GUI thread?
Elements are now generated dynamically based on the elementTable entries in the 'User config section' at the top of the code
The last window position and size is now remembered
Element and label sizes can be adjusted or scaled in the 'User config section'
General code formatting
The Button and Textbox elements are now generated dynamically.
So if fewer or more are needed, you can edit the entries of the elementTable in the 'User config section' at the top of the script code:
Code:
----------------------------------
-- Element table with preset names
----------------------------------
-- Rename your presets as you wish
-- If you need more entries, add a new entry lines to this table
-- If you need fewer entries, remove entries from this table
local elementTable = {
"System",
"Bus",
"Aux",
"Drms",
"Kbs",
"Gtrs",
"Vox",
"Fx",
"Custom 1",
"Custom 2",
}
There you can now also adjust some element and font size values:
Code:
local scaleFactor = 1 -- change this value to scale the element size - default: 1
--------------------------------------------------------------------
-- Base values for adjusting the element and label size and y-offset
--------------------------------------------------------------------
local elementWidth = scaleFactor * 64 -- width of the button and textbox elements - default: 64 (pixel)
local elementHeight = scaleFactor * 20 -- height of the button and textbox elements - default: 20 (pixel)
local yOffset = elementHeight + (scaleFactor * 10) -- offset between the elements on the vertical axis - default: 10
local leftPadding = (scaleFactor * 2) + 25 -- element padding on the left - default: 25 (pixel)
local middlePadding = 30 -- element padding between the two button columns - default: 30 (pixel)
local fontSize = 16 -- font size of the (tab and button) labels - default: 16 (pixel)
Let me know how the modified script works or if I may have accidentally broken something in the code
After thinking about your problem with getting 2 more buttons
I got to thinking of another script called Track Tags - have you
used that? It works a bit like mixer manager but it builds its
button dynamically, so you can have as many buttons you like!
Now I saw also that solger made a new version of Mixer Manager
there you could write in the code how many buttons you like.
Soo.....you have more than one way to go :-) Personally I prefer
the Track Tags, its more flexible to work with, you can select
many buttons to show tracks etc - and you can find it in ReaPack.
The Button and Textbox elements are now generated dynamically.
So if fewer or more are needed, you can edit the entries of the elementTable in the 'User config section' at the top of the script code:
Code:
----------------------------------
-- Element table with preset names
----------------------------------
-- Rename your presets as you wish
-- If you need more entries, add a new entry lines to this table
-- If you need fewer entries, remove entries from this table
local elementTable = {
"System",
"Bus",
"Aux",
"Drms",
"Kbs",
"Gtrs",
"Vox",
"Fx",
"Custom 1",
"Custom 2",
}
There you can now also adjust some element and font size values:
Code:
local scaleFactor = 1 -- change this value to scale the element size - default: 1
--------------------------------------------------------------------
-- Base values for adjusting the element and label size and y-offset
--------------------------------------------------------------------
local elementWidth = scaleFactor * 64 -- width of the button and textbox elements - default: 64 (pixel)
local elementHeight = scaleFactor * 20 -- height of the button and textbox elements - default: 20 (pixel)
local yOffset = elementHeight + (scaleFactor * 10) -- offset between the elements on the vertical axis - default: 10
local leftPadding = (scaleFactor * 2) + 25 -- element padding on the left - default: 25 (pixel)
local middlePadding = 30 -- element padding between the two button columns - default: 30 (pixel)
local fontSize = 16 -- font size of the (tab and button) labels - default: 16 (pixel)
Let me know how the modified script works or if I may have accidentally broken something in the code
Thx solger!
Opens up and customizes GREAT!! We are going away for the weekend and will give it a test run on Tuesday, Thx again and plz let me know if I can buya u breakfast!! (-'
jeff
__________________
Win 10 I9 20 core 48g Ram always on the latest update
After thinking about your problem with getting 2 more buttons
I got to thinking of another script called Track Tags - have you
used that? It works a bit like mixer manager but it builds its
button dynamically, so you can have as many buttons you like!
Now I saw also that solger made a new version of Mixer Manager
there you could write in the code how many buttons you like.
Soo.....you have more than one way to go :-) Personally I prefer
the Track Tags, its more flexible to work with, you can select
many buttons to show tracks etc - and you can find it in ReaPack.
Yes, I was trying the TrackInspector for awhile but it never seemed to stay in my workflow...But so far solger's modification works although I will have to check it out more after the weekend,(-:
__________________
Win 10 I9 20 core 48g Ram always on the latest update
Yes, I was trying the TrackInspector for awhile but it never seemed to stay in my workflow...But so far solger's modification works although I will have to check it out more after the weekend,(-:
Opens up and customizes GREAT!! We are going away for the weekend and will give it a test run on Tuesday, Thx again and plz let me know if I can buya u breakfast!! (-'
jeff
I have been putting the NEW modified script through the test and it seems to work flawlessly as the original, thx again EVERYONE involved!!
__________________
Win 10 I9 20 core 48g Ram always on the latest update
Hello I know that the post is rather old but I find this script great and I am looking for how to change in the code the fact that the interface opens under the mouse by opening it in the doc at a defined postition inside ?
Is it here ?
Returns x,y coordinates for a window with the specified anchor position
If no anchor is specified, it will default to the top-left corner of the screen.
x,y offset coordinates from the anchor position
w,h window dimensions
anchor "screen" or "mouse"
corner "TL"
"T"
"TR"
"R"
"BR"
"B"
"BL"
"L"
"C"
]]--
GUI.get_window_pos = function (x, y, w, h, anchor, corner)
local ax, ay, aw, ah = 0, 0, 0 ,0
local __, __, scr_w, scr_h = reaper.my_getViewport(x, y, x + w, y + h, x, y, x + w, y + h, 1)
if anchor == "screen" then
aw, ah = scr_w, scr_h
elseif anchor =="mouse" then
ax, ay = reaper.GetMousePosition()
end
Hello I know that the post is rather old but I find this script great and I am looking for how to change in the code the fact that the interface opens under the mouse by opening it in the doc at a defined postition inside ?
Is it here ?
Returns x,y coordinates for a window with the specified anchor position
If no anchor is specified, it will default to the top-left corner of the screen.
x,y offset coordinates from the anchor position
w,h window dimensions
anchor "screen" or "mouse"
corner "TL"
"T"
"TR"
"R"
"BR"
"B"
"BL"
"L"
"C"
]]--
GUI.get_window_pos = function (x, y, w, h, anchor, corner)
local ax, ay, aw, ah = 0, 0, 0 ,0
local __, __, scr_w, scr_h = reaper.my_getViewport(x, y, x + w, y + h, x, y, x + w, y + h, 1)
if anchor == "screen" then
aw, ah = scr_w, scr_h
elseif anchor =="mouse" then
ax, ay = reaper.GetMousePosition()
end
Which operating system are you using?
And are you using the original version of the script or my modded version 1.0 (see post #30)?
I'm asking because my modded version remembers the last window position and size.
So if the script window was docked manually once, it should open in the same (docked) position the next time the script is run.
Hello i m using win 10 pro
And 0.2 version
Now v1 modified and realy cool modification thanks
Just a shame not to have the minimal version But that's fine thanks
Last edited by grandfougue; 05-06-2022 at 05:07 AM.
Mixer Manager (my first script)
)
Linear Mode
