I don't see "Export > Export Tools" (is this an AI invention?)
Export Tools is a subsection of the menu, but it might not show up on all platforms.
I don't see "Export > Export Tools" (is this an AI invention?)
Export Tools is a subsection of the menu, but it might not show up on all platforms.
The idea of scriptnode was precisely to be able to customize stuff like this so that I don‘t have to frankenstein every HISE module with fringe use cases.
You can literally rebuild the waveform generator with a few nodes (minus hardsync)
easy job for scriptnode:
HiseSnippet 1455.3oc4X0saaaCEVJNzswKqHcnWrcmuXWjNTDXm5kzfcQb9wIyX0oFQoA6tBFJ5XBKQpIQkDugALfcydE5c60X2sWfALf8hj2fsCojrjhbbs8RSwvb.BDOjT76b9N+Q00WPnAABeCyJmLziZXtLxZHW1eu9XF2n89FlOB0AGHo9UiDs6PObP.01vzrzgJAlKsng920auK1AyIzTQFFmJXD5KYtLYpztM+FliyAXa5IL2LqtQy1DAeOgiHDvSITMCOLY.9b5QX0xV.Y703f9FleAZK5YjFjy5Yi2ZimWqw5aUmtIdyFaQWmPNqgcs5a7b6Mo0dggY4V1Lov2Rhkz.3ktqvdnUewk7nC3TV.6LGpZPcCK3jiDarWelic2DiSfggIpapopTjo5InNLa1H4olrUzSTMcGYMZlKLIHUeFfjYFHsXDjdLxh3y7joynvyGgZyAFrGF3lrPIZsFl+NZOAr.tbMW7.5A9vfQaX0MpU6YUg+8zupWHmHYBdUA+Hgj9J9pOsxOTYoJ+Xkp2bpd8F6bpiwW33P8G6zJ2A+IswU4gtmQ8eV0KvNgzQKDT+71zxSmMkDo0YVnf2lyjuxiFO9.gisxVodtHCXDa1fmdc68wRrhThkAqyi5KYJ3XtO8BHLHhhVBsOMXfT3AABE3OvyQXG5fk4cmTAZwS.1ibbnhn3AL4vrAhyfOVsI5iMsP7wntLIo+3w3BiAifk58AFiiL+XTqd8nDYJ.WDcv2NuggS+wuTxwGEYoyjpO9OKVBWXSqpESCXAT+5SHe5eNs4S8l57oIA7OCMKAW2HG5hSWvUde1LqeLYxJ+AH45cii+GvXyb4+WJAiVLWOGZK9ETGHAjFieBjwoGNzQlHMuWWGAW30WvYjrNZGSk9ryOm5mE6iUg1QJgxzoRdRyioNTbPFOwOu4KYbJ1GrSz4zVL60BGKe8onH3VUEpT8+t4TK8+lbpSxD8PTqqj935uqpMe.XuXns98IzNVDJY7y6fgP2qfVVOJz0Bx8Sn.r3bpC7xQlKn5aIZbM0XEHrnba8f+F9EOYc0Xy3IqmLYlVdNhJuT3OPG8E+Ln1QU6BFUs6MAYq1siii3x8DtdrXWZvqQKqqvYXRRHyEhVQBr2wUDBmXL1SiG10QPFXw9dZhZ.WO3DLyQ8FrBCfl3reE2BdO5ZnlkNk5GnOyGfpsF7GDtbjNgT4CvDf.F1ECkqg3NUeg.OR8WiLhOuccJaDPzMUt80pNujBxQXFTUWk8Tc8FyRY5ZLJmlZD3srfBBKiZGbpZVB1w3TUQZklpempkWJVYTKsLxEJRZjSudjVufB8qomqHri2z+JLVFoywGitJnSgBNDkCeFd6Dr+4TYPbyxbJIxSPSFssUgN9Xtsv0nK1G.FbQDkzGfhdooRUt7Yz4QaKmVuxHsNd1h58nMNKZ9LnOKiDADnCMUBhapSc6qJTlSm.aZxH3pacX7XiYZZ9N3qtgrq21RR8hhERWm0.5kQFibEw2O0XdB8J4IB8y.zu.TN8ghdM2l1Ch.rAjcdzcusBO6PeQnmdPAHE2gQA46DJEtPdM6QtpwrUNiRg3Oe5ZYltHkka2yDsoRs3PuJ41Z6yB7bvC2MDpsEY7yIQ4UClhqRR+0B5P1FtQnd6IoDyQdkyPdUlNxaklEIOfPuUxKNF6Nh6td6ai6LlrpznYAU4W9qapJ+5ae6uUTUZ9yt+w1QeYhC7oeWHjgd3cj97SCZNV8Aj+Nzmq2tH0TaFolk05S0iU4EdeSPWuswr6qMtDES1W6PH589UUdukyKJY68bNu6FNZRJVY8cPuO4HUhzcEhAtXc+ey2W+59naUWLwW7l3N.TomenVBTTfqqirDpiZb05FWbSdQ0KzaHj7upBab84ciOed2Xi4cie47twMl2Mt47twW7t2n5i.EGno51Bhi51JpprYKNFtujtaAi+QDB5ZT
@Oriah-Beats are you using the latest commits? There was an issue with the spectrum analyzer messing up the UI rendering but that's fixed now.
@ustk Alright I fixed the code generation - the fix was surprisingly easy because it already scoped the parameter class types correctly so it was just some inner variables that were acting up.
In a modulation context with that many branches (64 in total). Are all the branches modulated no matter if they are active or just the selected one is modulated behind the scene to save CPU?
The container.branch will selectively process the audio signal with only the selected child element, but if you have multiple connections from eg. an outside peak node, it will send its modulation output to all connected targets, not just the one that's inside the currently active branch child.

I've added a new node control.branch which you can use to send the value to a single target only. This can be used in combination with the container.branch node to limit the CPU usage:

Alright it's merged now, thanks @Dan-Korneff for the contribution! I had to modify the code a little bit to allow the usage of neural networks in compiled effects - the HPF filter setting will be baked into as a compile time constant when you generate the C++ code for the network.
I also added a check that throws an error if you try to use a hardcoded network with a neural network (or global cable, same concept) without creating it first in the scripting initialisation - before it just failed silently but now you get an error message in the hardcoded module's interface.
@d-healey is this new? I didn‘t touch that stuff for a few months.
@Yinxi you didn‘t have to pay for a VST3 license before and the immediate real world consequences for plugin developers are not very substantive unless you have a fringe use case that requires a super permissive license. It is rather interesting from a business perspective and will ensure that they cannot pull stunts like with the VST2 SDK.