easine and usine vsti were performing very well at their time, FL does too, few existing vst allows multiples instances to pass audio/midi flux one to each other (ie izotope neutron2) that would be the top notch solution, but prob more complex.., i would still be happy personally 'manually' wiring those within the host, if usine vst(i) had several audio and midi io available we can do virtually anything then, even in live (while agree bitwig for ex is much beter regarding this) we could route a midi from a track to midi in of usine vsti, same for multiples audio flows ect. this is not meant as full usine replacement (ie not sure multitouch would work) but rather a huge feature extension.
Rewire is nice but is a licensed solution that will cost, the vst has a huge advantage imo is that it is much more daws natively use them, everything is saved in a single centralised file, parameters chunk, automations are in the host, timing is rock solid, pdc is applied ect, its far less pain for maintenance and evolution of the project file. And if we can export crasy vsts and show eveyone usine power that will definitely target a larger audience that is not ready to let down completely their main sequencer, but could potentially later dig in the standalone usine.
Not sure if I understood you correctly. Likely not but here it goes.
There are third party VST's that can open in HH as modules and be able to receive midi and audio from a any source and output to any VST inside HH.
But if HH has a native solution the better.
HH3, what a great program and I am not using it because it is not a VST or a VSTi.
I may look into the older versions that can used a VST's.Statistics: Posted by Vas — 28 Oct 2017, 01:21
]]>