Make HH3 a VST

[Vas]

Hello,

This has been requested before but I thought I would renew the effort in the hope it will get done.

I would love to see HH3 be a stand-alone as it is but to be able to run as a VSTfx or a VSTi in a DAW like Cubase, S1 or Sonar.

FLS Studio runs as a sand-alone and as a VSTfx or a VSTi. This will bring in new buyers of this wonderful program the ones that have been avoiding it because it is not a VST. I am sure it is a lot of work to make HH3 a VST but the rewards justify it.

[23fx23]

+ 100000 :p

[gurulogic]

I would take even a vst capable of loading single patches and perhaps linking / busing flows between multiple instances of the plugin.

[gurulogic]

And I very much agree that having VST option would help HH reach a much larger audience.

[x.iso]

I guess it depends on what you look for in Usine, but I think ReWire support would make more sense. I switched to Usine because it was better for me as DAW and I don't think it's capabilities can be fully translated to VST. For example Usine as VST would not solve crappy routing system in Ableton Live.

[23fx23]

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.

[Vas]

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.

[Vas]

I would be glad if only the audio and midi was made into a VST.
The Video Engine and Artnet/DMX support for me need not be part of the VST package.

I am sure there is a lot of work to make HH3 a VST however the benefits to the users will be substantial as it will allow them to stay with their DAW of choice.
Sensomusic will benefit by attracting new users that love HH and now will purchase it as it is available as a VST. A win-win for all.

[senso]

still in project, but an hard job.

[Vas]

still in project, but an hard job.

Senso,

Fantastic news that a HH3 as a VSTi OR VST fx is in the list of features to be added.
You have the experience of making the earlier versions as VST plugins.
That's a lot of help I am sure to make HH3 a VST.
Ah, but this is why you are saying it is a lot of work!!!
Now I see!
But it will be worth it, in my opinion.

Now I will not put up my HH for sale.