Forum Replies Created
-
Posts
-
this is done by default the audio buffer is not touched by Ctrlr, what comes in comes out.
Interesting, useful, and gratefully received information. Thanks.
The vst version must route the audio from input to output otherwise it’s not very usable.
This is certainly very important for the majority of use-cases. Hopefully this won’t be too much work to implement…
I though you could load VSTi on FX channels. But if that’s not the case i can add another build type to Ctrlr if that will help.
This would be amazing and very much appreciated! The program already is something special though. Congratulations. 🙂
Some hosts allow VSTi on effects tracks/channels and vice versa, while others are more picky. Maschine being one, where, as zeoka points out, VSTi can only be loaded on the first slot of “Sounds”, but VST (effects) can be loaded anywhere.
In Maschine this is not possible to open a vsti in fx slots but the inverse yes. Why put a ctrlr instance in fx slots ? There is no sound in ctrlr ! Even if ctrlr controls a fx midi device this is not required to add an instance in fx slots i think.
As I said, I want to be able to use ctrlr on the Group level in Maschine not on a Sound, so therefore require it to be a VST “effect”, not an instrument. What it controls, as you say, is (partially) irrelevant and it does not have to be a VSTi instrument instance to control instruments and a VST effect instance to control effects units. However, it is the positioning and location of the ctrlr instance itself that I am interested in, which does require being loaded as a VST effect.
Thanks for your opinion though. 😉
