I just discovered that you can increase the window size when adding automation parameters by clicking on the border and dragging.. as usual.. and guess what? There is a CC# column
That makes it a lot easier to know what all that stuff means
EDIT: As long as you use a separate instrument on each track and open/close them when changing tracks, the Faderport will control the automation parameters on the selected track.
But this is a bit of a pain as I don't want to use a separate Kontakt instance on each track..
I create a separate feature request for this here: https://answers.presonus.com/31536/cont ... instrument
If you need this, then please up-vote and maybe Presonus will notice & implement this at one point.
Just figured out this does not work on a per track basis. I.e. fader for expression on track A will not move expression on track B, if I move the selection of the track.
They should probably pin Johnny Geibs cads on the Faderport right at the top of the FP8/16 section . They've been around since the release of the FP8.
Anyway, as long as the Control link can capture any instrument, or plugin parameter you click on, (the hand symbol will highlight from gray to white) you can control or automate that parameter, as well as be tied to any desired FP vertical fader. This includes buttons as well on the FP. His video covers more on this as to setting up so check that, rather than me writing a novel.
FP8 - using 3rd party plugins
So MIDI cc info as it enters into S1 can be allocated, as long as the Control link see's it. I just see if the MIDI cc is directed towards anything.
For external MIDI CC control, I use a MOTU 8 channel patchbay. That is seen by the control link, so that's my way of making the connection.
Anyway, Johnny's (theMuzic) video should shead some light.
Try contacting him for specifics.
As you said, as long as you have a visible element you can follow Johnny's tutorial and it works fine. For a lot of virtual instruments used for orchestral music this is not always the case. Those expect inputs from CC1, 2, 7 and 11 not linked to a button, slider, or other thing that is clickable in the user interface.
Still did not give up on this, as I really want modulation and expression for every track. However, it seems that without better integration between S1 and Kontakt (or any other sampler) this is not going to work.
FP8 focus was not meant to be used in multi rack setups - for now.
As an experiment I made a new orchestral template that has about 170 tracks, spanning over 140 Kontakt5 instances. I know that it is not supposed to be used this way, but hey.. it works I was actually quite surprised how little RAM this takes. 140 instances with all samples purged takes about 12GB of RAM out of 32, so more than enough left.
It also helps that I took a "template per company" approach. So CC1 is on FP8 fader 1, and this works on all Orchestral Tools VI's the same, without having to configure this per track. The only thing that can spoil this now would be high CPU usage.. so I am writing a song and lets see what happens.
The only other slightly annoying side effects are long load and save times, as S1 cycles through all 140 instances (takes about 15 secs). But OK, I can live with that. Just disable autosave and save regularly on your own.
Apparently, in the latest firmware update (3.x) they added a MIDI CC operations mode.
Have not tested it yet though.
Users browsing this forum: No registered users and 0 guests