@HISEnberg said in HISE pitch shift node introduces 100-200ms delay:
Use Engine.getLatencyInSamples to find it, then use Engine.seLatencyInSamples.
It's Engine.getLatencySamples and Engine.setLatencySamples (no In).
And getLatencySamples doesn't calculate the latency. It just returns whatever you set with setLatencySamples.
Use "Tools > Check latency of signal chain" to calculate the actual latency of the plugin.
@resonant Ah yes, that was the post I was looking for! 
@Straticah Pitch shifting causes latency. Have you tried Tools > Check latency of signal chain?
Also, this post: https://forum.hise.audio/topic/13654/latency-issuewith-fx-pitch_shift?_=1771883682066
@inlandempire I've been spoiled by this simple workflow from Maize Sampler, where I built my first sample-based plugins.
Import an EXS file and it imports all the samples with key ranges, loop points, etc. Lovely!
I'll be on to some sample-based stuff soon. Looking forward to tackling this!
@inlandempire Wow, that's a lot of work! 
We need to be able to simply add an EXS file and it imports everything. If that's not currently possible then I'll certainly start working on it when the need arises for me.
@duma I made the fix on Mac, so yes it does
@JC Good point about the splash screen. It's probably not legally 'clean' to use JUCE 6 and also not have a splash screen. Morally, that's up to you.
As I said before, if you're selling a closed source plugin and you have even moderate success, you'll be on the $40/mo JUCE plan pretty quickly anyway, which makes it legally and morally fine.
@JC Yep, sounds good. A couple of things to consider though:
The JUCE license covers you for use with JUCE 8 and earlier versions, so you can still use JUCE 6 in HISE if you like.
Keep in mind that with even a moderately successful plugin you can hit 20k pretty quickly, and at that point you need to upgrade. And that's gross revenue (before expenses) for ALL your uses of the JUCE code. Meaning, if you have a bunch of free-pay-what-you-want plugins, then the revenue from those counts towards the $20k.
Also keep in mind that this is all based on the honour system, so it's up to you to do the right thing.
@David-Healey Another vote for disabling the Export menu the pre-built HISE.
@David-Healey Assuming that you just want me to load the snippet and open the filter module?
@cassettedeath You can find a lot of brand vector logos on Wikimedia Commons:
https://commons.wikimedia.org/wiki/File:Cubase_6_logo.svg
You don't usually need permission to use the logos but you do sometimes need to attribute them and follow the brand's guidelines.
A blanket statement should be good: "DAW logos are trademarks of their respective owners." as long as you don't imply any sort of affiliation or link with the company.
Safest way is to just use text, no logos, like:
"VST3/AU/AAX versions. Works with Logic Pro, Ableton Live, Cubase, Reaper, Bitwig."
@griffinboy said in MacOS Parallels WIN build fail:
What's odd is that there is no error message above.
Yeah, weird.
@pelle Cool. What versions of macOS, Parallels, Windows and Visual Studio are you on?
Did you build HISE from the latest commit from the develop branch, with JUCE as a submodule?
Does exporting a minimal plugin (like a volume knob) work ok?
@pelle How do you know it stopped compiling?
@inlandempire Yeah, if you bought Logic at any time in the past you'll be able to download the latest version from your Apple account in the App Store on Mac. Free lifetime updates! 
Not sure about the loop points, but I'd be surprised if HISE doesn't already support Logic loop points. And if it doesn't, it needs to because I'll be doing some sample-based plugins soon!
