Powershell, paste this:
irm https://github.com/christophhart/hise-cli/releases/latest/download/hise-cli-setup.exe -OutFile $env:TEMP\hise-cli-setup.exe
& $env:TEMP\hise-cli-setup.exe /VERYSILENT /NORESTART
then start the hise-cli and type in /setup, wait 20 minutes and everything is setup. It will install MSVC, IPP, Faust and clone the HISE repo and all its submodules completely automated.
You're trying to build the Faust build without having installed Faust. Select another Scheme to build that doesn't include Faust (or use the hise-cli for setting this all up).
With the mod matrix system each connection can have a intensity and you should also be able to set it programmatically without the matrix floating tile using the API.
For targets that dont expose a mod chain you can just define a UI knob and give it a matrixTargetId. You‘ll loose the precision of the real mods but if it‘s acceptable then fine.
The modwheel could also be a global source modulator using a control modulator.
@observantsound Use the matrix, you can add / remove connections with API calls that you can hook to combobox callbacks, the matrix / drag stuff is just a readymade solution for the most common synth UX stuff.
https://docs.hise.audio/scripting/scripting-api/scriptmodulationmatrix/index.html#connect
@David-Healey That's fixed now, it now respects the scope of anonymous functions within a namespace like this.
@David-Healey ah yes that's a bit more complicated - the resolver for the first namespace doesn't work so it basically ignores the namespace qualifier and resolves the function call to itself so it creates a recursive loop.
In order to reproduce the faulty behavior without the crash you can do this:
namespace FirstNameSpace
{
const var myFunc2 = 90;
}
namespace SecondNameSpace
{
inline function myFunc()
{
if (isDefined(FirstNameSpace.myFunc))
{
Console.print("exists");
}
else
{
Console.print("doesn't exist");
}
}
}
SecondNameSpace.myFunc();
The suggested fix of passing in the current namespace is not a real fix, it might solve your immediate problem, but the correct option would be to return an undefined expression like this:
match(TokenTypes::identifier);
return parseSuffixes(new Expression(location));
then this code would work as expected (returning "doesn't exist"). However this might silently break existing code that used this construct to falsely refer to non-namespaces data through a namespace qualifier so I'm a bit hesitant to push this.
@HISEnberg why? just use JUCE 6 the reason to switch to JUCE 8 are almost non existent
@David-Healey ah so basically Namespace.nonexistingProperty crashes?
@HISEnberg fftw isn‘t supported yet but the hise-cli should be able to one shot the entire dev setup including faust on macOS and Windows.
@David-Healey normal functions are var declarations in disguise and previously leaked to the global namespace without warning - that‘s one of the reasons why I added the yellow warning stuff
