@ulrik said in Find the right formula?:

@d-healey This is what I get when using the draggable filter

How do I set the q-factor?

And how do I do with knobs if the User set 8 tiles or 3?

the end user sets the q using the scroll wheel...if you use the draggable eq panel - you wont need ANY knobs, it configs itself...

@Lindon ... hmm,
just came back to this and now the Sampler Retrigger = "do nothing" fix no longer works - has something changed in here recently?

@vewilya my experiments in this seem to show you dont need anything down as low as 20 ms anyway - 50 ms is plenty....

@Christoph-Hart - Ok I think I got that.

So in my case all I need do is add HISE_ENABLE_MIDI_LEARN=1 in my project extensions... and I get MIDI Learn and (obviously) MIDI in for my FX plug-in.

@d-healey said in FX - CC input:

@ulrik Nope, he wants to have MIDI input into his audio effect. But we know how to do that now

Not sure we do know --- perhaps its just me who is confused.

So yes I want to have MIDI input (and MIDI learn) in my effects plug-in (lets say its a chorus of some sort..)

What do I turn on in hi_core for projucer?
What do I turn on in the project extensions?

@d-healey so its the projucer settings above(the ones in hi_core).. I just recompiled with those turned OFF - and it works fine...

@Christoph-Hart ??????????

@d-healey nope nothing - I have an earlier version form Nov which works fine, I've just deleted the whole build folder and rebuilt from scratch - same problem , no sound being generated

@d-healey HISE

I just recompiled HISE - and it now wont make any sound at all - there is no output.

I can see midi notes arriving but even a simple sine wave generator wont make any noise at all...

I inserted a script node and its receiving midi notes - but at the point nothing else happens...no sound generated - and none appearing in the LEDs

@Lindon said in FX - CC input:

Yep confirmed that works - life saver as usual Mr Healey...

Woah spoke too soon -- this broke HISE in a pretty permanent way - it now wont make any noise at all.....

OK so I have a number of VST3 plugins, and I'm getting a small number of users who are having problems with the install process.

My installer lets them put the plugin wherever they like, BUT......

Steinberg and a few other DAW developers insist that the plug in (on windows) goes in

C:/program files/common files/VST3

if its not there then Cubase refuses to see it - as it seems does Studio One and maybe even FL Studio

Sensible democratic DAWs like Reaper seem to not care less about where you put it - just point em at the plugins and they check and install them

So its a pretty simple support call to deal with but any smaller number of support calls is always a good idea.

FINALLY A QUESTION!.....

What's every one else doing about this for their VST3 plugins? Forcing them into the default folder? Putting big "HEY CUBASE USERS!" signs all over the documentation? Qua?

Whats working for you?