@David-Healey Yeah, might be interesting.

I generally don't participate in marketplaces or use resellers, etc. but more out of an abundance of caution than anything else.

It would be yet another fee on Moonbase's already fairly extensive fee matrix. It would be good if they could simplify that a bit.

@robJ Thank You 🙏

"OK, that's it. Thank you."

@LucaL check what's in that array, I don't know without seeing the rest of your project

@ustk Haha I am launching HISE with the cli most of the time and there it worked so I never bothered…

hise-cli -hise launch

@Morphoice
Ah, no but that is a reason to reset everything!
Under many conditions, changing parameter values all at once can produce monstruous audio. Like, if the DSP effect has feedback, if you don't clear all the buffers, the audio from before the switch, could blow up under the new parameters. There are scenarios that can sound really horrible or blow out your speakers. I mean, let's say the new preset has different reverb parameters, you'll get all the reverb knobs yanked while it's still playing, and get all that washy doppler... Of course that's not a horrible situation, but you can imagine that certain DSP would produce really loud nightmares. Which is why it's quite sane for Hise to send reset() on a preset change, to clear out all the buffers and start from silence. It's the safest thing to do.

But I agree that creatively, there are situations where this is not what you want. But you can understand why Hise went with the blanket solution.

@ustk The man is too good! 🔥 @lalalandsynth 🏆

@aliabr_prod You can see all the latest developments here

Make a bug report at github and link back to this thread so it doesn't get lost.

@ustk thanks mate I will give it a go...I have no idea how to do a "correlation algorithm" but its all an adventure...

@dannytaurus Interesting, looks like they are also phasing out Intel support when they eventually limit the minimum deployment to 27.0 - probably a few years yet.

I'll just stick with my existing build system for now until it no longer works.

@eschirle I don't know, I haven't used the ci method

For anyone curious - it looks like you can get around this by linking the expected path to wherever you have Visual Studio installed

mklink /D "C:\Program Files\Microsoft Visual Studio\18\Community" "C:\Program Files\Microsoft Visual Studio\18\Enterprise"

@Jeetender said in Latency issues..:

@Jeetender said in Latency issues..:

I made a vst everything works fine, but when i open that vst into any daw like flstudio/live/reaper/reason it gives out latency.. how do i compensate the latency automatically?

i did try this.. but nothing worked, BUT i had a dynamic module in the end of the chain, which had a limiter, i removed it and then the latency was gone after compiling the vst..

can u please elaborate, coz iam not much of a DSP coding guy. but i had tha plugin at the end of the chain which already was of no use.. and i dont know why doesn't it report the latency to the DAW automtically, the other plugin ive made do this well and good, no latency with other plugins.. but i am here to learn more about this.

@dannytaurus PACE has added WoA support to Fusion 6 SDK, Eden Tools, and iLok License Support 6.

This indicates that there will be demand for this (though I am not sure exactly how soon) at some point.