Sorry it is an old topic but,
Yes I can confirm that, setLatencySamples works perfectly in all of the daws except FL Studio.
Weirdly, when I don't use setLatencySamples, FL studio matches the delay compensation perfectly 
So what is the difference that only FL studio doesn't take setLatencySamples correctly? Have anyone solved that?
@d-healey said in Is xcpretty for XCode 10.3 or XCode 8?:
@Steve-Mohican It doesn't it installs it via gem
https://stackoverflow.com/questions/39381360/how-do-i-install-ruby-gems-on-mac
Yes exactly!
First I opened Gem file in the xcpretty download package.
Then sudo gem install xcpretty command in Terminal, worked.
Thank you so much for the help. @d-healey
@d-healey said in Is xcpretty for XCode 10.3 or XCode 8?:
Also for 10.3
Thank you for the clearification Dave.
I've downloaded xcpretty, the downloaded package is in the "Downloads" section. When I type sudo gem install xcpretty , it is not working.
How the Terminal will know that xcpretty is in the "Downloads" directory? I think it is the problem.
Hi guys
I think XCode 10.3 is working with Hise on Catalina.
Do you use xcpretty for mac plugin export, on Catalina with XCode 10.3?
Or xcpretty is only for XCode 8?
Does anyone see the fx plugin crash on Logic Pro X 10.5 - Mojave or Catalina ?
I think it is an Open GL issue. I both built the plugins with Hise master branch and also scriptnode branch.
@Christoph-Hart have you updated the Hise for the new macOS Open GL requirments?
Well, it seems like I must use 2017.
Thank you so much guys!
I've built a new PC. I need to install Visual Studio Community and Intel Performance Primitives, in order to compile plugins with Hise.
Which Visual Studio version should I use now? 2017 or 2019?
Would the latest Intel Performance Primitives will be ok?
Any info appreciated.
@Lindon said in Hise compile error:
@Steve-Mohican what do you mean by "When I save the project in JUCE" do you mean when you save the projucer project file? Post a snapshot..
Yeah I selected "IPP Enabled" and saved the projucer project. That message is coming just after attempting to saving.
@ustk said in Hise compile error:
@Steve-Mohican "Hise-scriptnode_codegen_rewrite" is not a working branch
"Hise-scriptnode" might not work (although I'm not sure). What I'm sure is that it does work until January 20th commit
Currently and until the release of V3, it seems that the most advanced version is @d-healey's fork:
https://github.com/davidhealey/HISE/tree/develop
It's a working scriptnode version with some ameliorations in the waiting for @Christoph-Hart's approval/merge...
Ok now I understand, the scriptnode branch is not compiling too.
Thank you so much for the suggestion, I will try @d-healey's fork.
And also we will wait for v3 
I am trying to compile "Hise-scriptnode_codegen_rewrite" and also "Hise-scriptnode" versions.
When I save the project in JUCE, I am getting this error message:
"At Least one of your JUCE path is invalid."
I can't compile both two Hise versions, should I need to do anything?
@Christoph-Hart said in Scriptnode pitch-shift a signal:
the Degrader and Limiter modules (not the Dynamics) are mda plugins, but I am close to removing them as they don't bring much high fidelity to the table and their functionality can be reproduced with scriptnode modules pretty easily.
If it is ok about license situation, please don't remove them, because I've done lot's of things with them, and will be ready to release, if you remove, all of the work will be trash.