HI
Been a long time since I looked at this DAW - I can't find any info on automating VSTI parameters: can anyone help?
Thanks.
Flipper.
Automation?
-
original flipper original flipper https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=8999
- KVRAF
- 2544 posts since 14 Sep, 2003 from Essex
-
- KVRian
- 1372 posts since 21 May, 2004 from Serbia
First you must set a target for a track to be a VSTi. You can do this by clicking on the icon in the track header and selecting a VSTi.
Now create a sequence on that track and double click it to open the editor.
Click on the field below the keyboard on the left side and select a parameter you want to automate.
Draw the automation.
Now create a sequence on that track and double click it to open the editor.
Click on the field below the keyboard on the left side and select a parameter you want to automate.
Draw the automation.
-
original flipper original flipper https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=8999
- KVRAF
- Topic Starter
- 2544 posts since 14 Sep, 2003 from Essex
HI
Well I tried that - but I am not seing the VSTI synths parameters shown.
Flipper.
Well I tried that - but I am not seing the VSTI synths parameters shown.
Flipper.
-
- KVRian
- 1372 posts since 21 May, 2004 from Serbia
I made a simple example with TAL Uno 62. Get it here and see if it works for you
-
original flipper original flipper https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=8999
- KVRAF
- Topic Starter
- 2544 posts since 14 Sep, 2003 from Essex
HI
I loaded up your example (many thanks) and did see the VSTI parametres list for TAL Uno 62 - but when I started a new song, loaded TAL Uno 62 into a rack and clicked on the blank area to the bottom left in the piano-roll I am not seing any parameters list.
You must be doing something else that I am not aware of to be getting the parameters up?
I have tried the same procedure with several other VSTI's and get the same results.
Flipper.
I loaded up your example (many thanks) and did see the VSTI parametres list for TAL Uno 62 - but when I started a new song, loaded TAL Uno 62 into a rack and clicked on the blank area to the bottom left in the piano-roll I am not seing any parameters list.
You must be doing something else that I am not aware of to be getting the parameters up?
I have tried the same procedure with several other VSTI's and get the same results.
Flipper.
-
- KVRian
- 1372 posts since 21 May, 2004 from Serbia
Are you sure you are correctly setting the target for a track? You can check it by looking at the icon in the track header - it must be a VST icon. It must be set to the VSTi itself, not to the rack. I don't know what else could be a problem.
-
original flipper original flipper https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=8999
- KVRAF
- Topic Starter
- 2544 posts since 14 Sep, 2003 from Essex
HI
That was where the problem was - because I inserted a VSTI on a particular track I never thought that further 'targetting' would be required!
As I said: I haven't looked at 'Mu' for at least a year - there wasnt even automation then ... if I remember.
My next challenge will be to set up a send FX and how to work with multi-out drum VSTI's.
EDIT: found some docs and tutorials - I'll study them!
After such a long gap between using the beta and now it does seem like a lot of work is required to get pretty basic stuff up and running - I will persevere for a while and see.
Thanks.
Flipper.
That was where the problem was - because I inserted a VSTI on a particular track I never thought that further 'targetting' would be required!
As I said: I haven't looked at 'Mu' for at least a year - there wasnt even automation then ... if I remember.
My next challenge will be to set up a send FX and how to work with multi-out drum VSTI's.
EDIT: found some docs and tutorials - I'll study them!
After such a long gap between using the beta and now it does seem like a lot of work is required to get pretty basic stuff up and running - I will persevere for a while and see.
Thanks.
Flipper.
-
- KVRian
- 1372 posts since 21 May, 2004 from Serbia
I'm glad you got it sorted 
MuLab did evolve a lot and is more complex now, but it's still fairly easy to use once you get used to the logic.
MuLab did evolve a lot and is more complex now, but it's still fairly easy to use once you get used to the logic.
-
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
Some more info:
You don't have to use a track target in order to automate a vst plugin.
Even if you create a sequence part on an 'open' track and select a vst plugin as target for that part (via the Part Property Panel in the top right), then you should see all parameters for that vst plugin in the sequence editor for that part.
Maybe the confusion came from the fact that the part targetted a rack holding a vst plugin instead of of targetting the vst plugin itself.
The sequence editor uses the parameters of the part's target. If that is a rack, you won't see any vst parameters. The part has to target the vst plugin itself.
I understand this might be a bit confusing at first, but in fact it's very logical. Targetting a rack is not exactly the same as targetting the first plugin in that rack.
This behaviour has always been like this.
Not sure why you find it more complex.
If there are workflow bottlenecks which are too complex, please let me know, so i can evaluate and work on it!
You don't have to use a track target in order to automate a vst plugin.
Even if you create a sequence part on an 'open' track and select a vst plugin as target for that part (via the Part Property Panel in the top right), then you should see all parameters for that vst plugin in the sequence editor for that part.
Maybe the confusion came from the fact that the part targetted a rack holding a vst plugin instead of of targetting the vst plugin itself.
The sequence editor uses the parameters of the part's target. If that is a rack, you won't see any vst parameters. The part has to target the vst plugin itself.
I understand this might be a bit confusing at first, but in fact it's very logical. Targetting a rack is not exactly the same as targetting the first plugin in that rack.
This behaviour has always been like this.
Not sure why you find it more complex.
If there are workflow bottlenecks which are too complex, please let me know, so i can evaluate and work on it!