patrickmartin_Setup Multi-Out VST

[PatrickMartin]

Setup Multi-Out VST



Overview

This script adds a VST on a new track and then:

• Creates # of MIDI tracks you specify. Each track input is set to the MIDI device you specify, with each track configured to send data to the VST on a separate MIDI channel (1-16 and 16 for all tracks beyond [project]16[/project])
• Creates same # of audio tracks, each configured to receive audio from the VST track on one of its stereo outputs (1/2, 3/4, 5/6, etc)
• Names the tracks according to abbreviations you specify, or using the full VST name if no abbreviations are specified
• Creates folder tracks for the MIDI and audio channels
• Colors the MIDI and audio tracks to RGB values you specify

Dependencies

None

Configuration

--name of the VST 
--(use name only, i.e. "Omnisphere" not "VSTi: Omnisphere (Spectrasonics) (8 out)"
uc_vst_name = "Omnisphere"

--# of stereo outs on the VST
--This # of audio/MIDI track pairs will be created.
--  * each MIDI track will receive on all channels but send on only 1
--  * tracks above #16 will send on channel 16
--2X this # of channels will be created on the instrument track
uc_vst_stereo_outs = 8

--name of MIDI input device or nil to use all inputs
uc_MIDI_input_device_name = "masterkey 49"

--Optional: Color for MIDI tracks {R, G, B} or {}
uc_track_color_MIDI = {255, 204, 204}

--Optional: Color for audio tracks {R, G, B} or {}
uc_track_color_audio = {229, 255, 204}

--Optional: Track name abbreviations {audio, MIDI}
--Example: {"0S-Out", "OS_MID"} would name tracks as follows:
--  'OS-MID' for folder, 'OS-MID1', 'OS-MID2' ..., 'OS-Out1', 'OS-Out2', ... for child tracks
--Set to {} to use VST name 
uc_track_name_abbreviations = {"O-Out", "O-MID"}

Changelog
07/04/2019 1.1beta
Corrected MIDI channels

06/25/2019 1.0beta
Initial

[X-Raym]

Hi,


Thx for sharing and welcome aboard scripting !

You image link is wrong, you have to paste direct link, ending by .png or .gif :P


Best,

[EpicSounds]

where is the script? I don't understand

[Delucci]

Originally Posted by EpicSounds

where is the script? I don't understand

I saw in ReaPack today.

[hopi]

hmmm got the script and IMO would be a lot better if it would accept user input on the names and numbers as it runs...

really otherwise why not just create track templates and use those?
...been using templates like that for a long time here

Not to take away from the good idea and the effort mind you, just sayin'

[hopi]

Oh also just discovered if the HeDa Track inspector VIP is loaded it totally messes up the track numbering, which messes up the sends and receives...

sorry to report this issue but there it is... HeDa TI is active takes up track #1

[PatrickMartin]

Originally Posted by hopi

Oh also just discovered if the HeDa Track inspector VIP is loaded it totally messes up the track numbering, which messes up the sends and receives...

sorry to report this issue but there it is... HeDa TI is active takes up track #1

Never be sorry to report an issue - that's exactly why I called it 1.0beta. Maybe you can post a screenshot?

Also I thought about prompting for user input for the values but figured people would complain about it

[PatrickMartin]

Originally Posted by EpicSounds

where is the script? I don't understand

I assumed everyone would know where to find it (being new to the forums as I am). In future to avoid confusion I will include something in the description about "where"

[hopi]

Originally Posted by PatrickMartin

Never be sorry to report an issue - that's exactly why I called it 1.0beta. Maybe you can post a screenshot?

Also I thought about prompting for user input for the values but figured people would complain about it

Hi Patrick... well, I would not complain about user inputs... LoL
I think they would be just grand since diff VSTi's would\could be used...
Omni only wants 8 but Kontakt might like 16, and with the names set up also... right?

As to the screen shot... umm it would be a huge mess to really show you... but here is the thing and you can get it for yourself I think..

To do so you would have to 'buy' in to HeDa's VIP stuff for a 6 month subscription... min donation is about 5 bucks... so heck... worth it for the track inspector and the mixer at triple the cost!

Anyway, when his VIP Track Inspector is used, it sets itself up as a hidden track #1... and then when we run your script, all the sends and receives are offset by 1... so what should be send 1, receive 1 becomes 2, etc, etc.

It's not really a life and death prob. for personally because I already have track templates for Omni, Kontakt, ADDrums, etc.

Still, users should be aware of this issue IF they also use HeDa's VIP TI...

I don't know if there is a way around it... I'm not a script guy at all
even though I love using them...

[PatrickMartin]

Originally Posted by hopi

well, I would not complain about user inputs... LoL
I think they would be just grand since diff VSTi's would\could be used...
Omni only wants 8 but Kontakt might like 16, and with the names set up also... right?

I will explore prompting for user input in the next version - as much for my own learning experience as for improvement of functionality