VST3 ?
-
No, not possible. VST 3 is still not broadly accepted by hosts and doesn‘t offer any advantages for instrument plugins which is the core functionality of HISE.
As long as there are no major hosts which only support VST3 I won‘t bother about it.
-
@christoph-hart You know the best, man
:sign_of_the_horns_light_skin_tone: -
I honestly haven’t looked at the code lately but how is VST3 support going? JUCE has been compiling VST3 with no issues for a long time now. I’m willing to jump in to a branch and lend a hand! What are the issues here with juce? There may be some deprecated functions to deal with obviously. It’s definitely time to move on.
-
@orange you can export it, from the projucer file that hise produce when exporting your plug-in within hise. That's how I exports my VST3 plugs
-
@Christoph-Hart I think Midi 2.0 will be the thing to watch next. Not vst3
-
@Jay good to know!!
-
At this point it is more important to get a VST IDE to go with the VSTi IDE we already have, @orange has showed that HISE is capable of creating world class effects now too, so we could really do with a way to preview in context as we build.
-
@Win-Conway said in VST3 ?:
At this point it is more important to get a VST IDE to go with the VSTi IDE we already have, @orange has showed that HISE is capable of creating world class effects now too, so we could really do with a way to preview in context as we build.
We can already do this by running HISE as a VST plugin and developing in that. Or did you mean something else?
-
@d-healey
VST, not VSTi, we have a VSTi, not a VST.
VSTi = Instrument.
VST = Effect.
To develop effects you need an environment that will work as intended, the VSTi that we have now, has no audio inputs, so the only way to test any effect designs (VST) is to load a sampler and use audio from that, we need a compile as VST (Audio inputs and outputs) added to what we have now, VSTi. -
@Win-Conway said in VST3 ?:
@d-healey
VST, not VSTi, we have a VSTi, not a VST.
VSTi = Instrument.
VST = Effect.
To develop effects you need an environment that will work as intended, the VSTi that we have now, has no audio inputs, so the only way to test any effect designs (VST) is to load a sampler and use audio from that, we need a compile as VST (Audio inputs and outputs) added to what we have now, VSTi.Oh now I understand. I wonder if there are any flags we can set in Projucer to enable this, like we can for changing the number of audio outs...
-
This post is deleted! -
@Win-Conway said in VST3 ?:
VST, not VSTi, we have a VSTi, not a VST.
VSTi = Instrument.
VST = Effect.
To develop effects you need an environment that will work as intended, the VSTi that we have now, has no audio inputs, so the only way to test any effect designs (VST) is to load a sampler and use audio from that, we need a compile as VST (Audio inputs and outputs) added to what we have now, VSTi.Agree
-
@d-healey
I'm a complete newb with the compiling side of things, but it would be interesting if we could get a VST going for sure, Making some basic effects would be a great way to learn construction in HISE i think. -
@Win-Conway following
-
@Jay haha...I never thought to try it. Assumed it was broken. Appreciated
