Old 01-13-2019, 09:48 AM   #1
b0se
Human being with feelings
 
b0se's Avatar
 
Join Date: Jan 2019
Location: UK
Posts: 938
Default REQ (donation): named Track Creation (Post fader)

Hi there!

Happy to donate a thanks for anyone willing to create this! I'm an Airwindows Console (summing emulation) user. I've created track templates (see below), but they are created without a name and it's a pain to keep everything organised.

Track creation method (simple routing):

1) Create two tracks, send the first track to the second (it will automatically be set to post fader). Clear the Master send check box on the first track. Audio is now going through the send to the second track and that track is sending to the master. On the second track add the ConsoleChannel plugin, emulating a post fader insert.

2) Highlight both tracks. Open track manager, and on the second track clear the MCP/TCP dots to hide it from view. Go to View -> Track and select 'Save tracks as track templates'. Save as '01'.

3) Bind a shortcut to the 'SWS load track template 01' action.
-----

Easy enough, but every time you create a new track they have no names. Fine for the visible, but the hidden post fader send tracks without names are a pain to maintain. Hence the request!

TL;DR;

Is there a way to create a script that launches a simple popup for entering the track name, then runs the SWS script passing this name through to name the new tracks? <TrackName> and <TrackName>-Hidden perhaps?

I hope that makes sense. It would be amazing for workflow!

Airwindows Console5: https://www.airwindows.com/console5/

Reaper + Console5: http://beatdruid.com/index.php?title...ole#DAW_Setups

Kind regards,
Ross
b0se is offline   Reply With Quote
Old 01-13-2019, 10:00 AM   #2
bFooz
Human being with feelings
 
Join Date: Jul 2010
Location: Slovakia
Posts: 2,588
Default

Hi, I can take a look at this.

What you really want is a script for all steps you are describing, it is much more convenient and I don't know how it would be done using SWS commands.
bFooz is offline   Reply With Quote
Old 01-13-2019, 10:06 AM   #3
b0se
Human being with feelings
 
b0se's Avatar
 
Join Date: Jan 2019
Location: UK
Posts: 938
Default

Quote:
Originally Posted by bFooz View Post
Hi, I can take a look at this.

What you really want is a script for all steps you are describing, it is much more convenient and I don't know how it would be done using SWS commands.
Hey bFooz. That makes sense, and great news! Thank you.

If you'd be creating it from scratch, being able to choose which track template (maybe a drop down?) would be killer! Although happy to manually name the template with a fixed reference if that's much easier.
b0se is offline   Reply With Quote
Old 01-13-2019, 10:13 AM   #4
bFooz
Human being with feelings
 
Join Date: Jul 2010
Location: Slovakia
Posts: 2,588
Default

I did not mean using track templates at all.

What I meant was to create tracks, sends, add FX and all stuff right in the script. Do you think this would be ok for you or do you require track templates?
bFooz is offline   Reply With Quote
Old 01-13-2019, 10:24 AM   #5
b0se
Human being with feelings
 
b0se's Avatar
 
Join Date: Jan 2019
Location: UK
Posts: 938
Default

Quote:
Originally Posted by bFooz View Post
I did not mean using track templates at all.

What I meant was to create tracks, sends, add FX and all stuff right in the script. Do you think this would be ok for you or do you require track templates?
I do use two templates:

01
Track 1: True Iron, Console 1
Track 2: ConsoleChannel

02
Track 1: True Iron
Track 2: ConsoleChannel

Is there a way to choose plugins via script only, or would it always be hard-coded?
b0se is offline   Reply With Quote
Old 01-13-2019, 10:29 AM   #6
bFooz
Human being with feelings
 
Join Date: Jul 2010
Location: Slovakia
Posts: 2,588
Default

It would be basically hardcoded. But you would be able to rewrite plugin names in the script to add different ones.
bFooz is offline   Reply With Quote
Old 01-13-2019, 10:31 AM   #7
b0se
Human being with feelings
 
b0se's Avatar
 
Join Date: Jan 2019
Location: UK
Posts: 938
Default

Quote:
Originally Posted by bFooz View Post
It would be basically hardcoded. But you would be able to rewrite plugin names in the script to add different ones.
Could the script be duplicated, one script per template? Iterative script name or something?

If so, that would work just fine :¬)
b0se is offline   Reply With Quote
Old 01-13-2019, 10:35 AM   #8
bFooz
Human being with feelings
 
Join Date: Jul 2010
Location: Slovakia
Posts: 2,588
Default

Sure, you just copy the script file, rename it as you wish, rewrite plugins as you wish, load it into Reaper and working. You have two actions for two different "templates".

But it will always create two tracks sending one into another.
bFooz is offline   Reply With Quote
Old 01-13-2019, 10:46 AM   #9
b0se
Human being with feelings
 
b0se's Avatar
 
Join Date: Jan 2019
Location: UK
Posts: 938
Default

Quote:
Originally Posted by bFooz View Post
Sure, you just copy the script file, rename it as you wish, rewrite plugins as you wish, load it into Reaper and working. You have two actions for two different "templates".

But it will always create two tracks sending one into another.
As long as the 'post fader insert' routing (with a named hidden track) is in place and I can bind keyboard shortcuts that's fine by me!

Thanks!

Edit: Can you set the track colour also? My templates used a black colour for the hidden tracks so they were easily spotted in track manager.
b0se is offline   Reply With Quote
Old 01-14-2019, 07:06 AM   #10
b0se
Human being with feelings
 
b0se's Avatar
 
Join Date: Jan 2019
Location: UK
Posts: 938
Default

Just want to thank @bFooz for the great script (and communication)!

Cheers bud.
b0se is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 03:48 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.