@dannytaurus said in Issue compiling HISE on Mac:

44MB compared to 195MB for Debug - is this normal?

Yes, the debug build lacks a lot of optimisations, which makes it larger and should make it faster to build - I think the linking stage is almost completely skipped.

@Dan-Korneff Yes, definitely the same issue. If .setOnBypass is the solution to this problem, good, I will try it immediately. Thanks.

@Lindon I find deleting the build (not Builds!) folder usually fixes this. Then I'll get the proper timestamps on both Debug/HISE Debug.app and Release/HISE.app

Projects > standalone > Builds > MacOSX > builds (delete this folder)

Also, sometimes Xcode builds HISE and the app size is around 100KB so I assume it failed but when I double click the HISE app it opens properly. Very strange.

@Christoph-Hart I wish that the term open source and GPL belong to the identity of my work

@Christoph-Hart Thank you for the information

@d-healey 🙏🌍🌞

I am beginning to understand that if I am able to ask a correct and understandable question, I will get a clear answer. Thank you

@aaronventure Yes, IPP increases performance. It reduces CPU usage, especially in conversion work. I used to use it a lot before, but we received a lot of complaints due to the problem I mentioned. That's why I stopped using it.

@HISEnberg Awesome, sounds good. Thanks heaps for your reply and the time you've taken.

@dane-zone Yes scriptnode is probably the easiest way to go here, and there is an example implementation of a vibrato in ScriptNode here: https://forum.hise.audio/topic/4952/scripnode-101/13
Modulation signals don't produce sound, they modulate an audio signal, so stereo modulation is not possible.

Vibrato is just modulating the pitch, so unless you wanted to modulate the Left and Right channels separately there is no reason to process the channels differently. If you want to do this then follow the vibrato example above, separate the left and right channels, and add independent mod sources and delays on each channel (Left and Right).

@HISEnberg Thanks! this is helpful

I'm going to work on backend first like you said - slot FX looks like exactly what I need

@Lindon yes in an ideal world the script voice start modulator should show the interface designer instead of the scriptnode workspace but that shouldn‘t keep you from slapping one lousy table on the modules interface by scripting.

That makes it three lines of code…

@Christoph-Hart After completing elements such as knobs, buttons, sliders, combo box, panels..etc. +1 cent for the Draggable filter panel

@DanH my thoughts exactly.... I just suggested it to Christoph in another thread. Release curve control seems to be a common demand and would be super useful

@d-healey I'm having the same issues, have we ever figured out a solution to this? did anyone ever build a custom envelope in scriptnode?

@DabDab yes it's because the commits were from the pull request that didn't update the hash counter. It'll be fixed the next time I commit something, so shouldn't take too long...

@pelle thanks

@ustk thanx, for what i read on the link you gave me seems to.be the solution

@Morphoice You can control it through scripting, and you can also flip the polarity and the intensity.

@Christoph-Hart

HiseSnippet 994.3oc6V0saaaCElxIbXwaEaYqO.B8J2kBC4Z4eBJJVp+IMdKN1K1qs.6hBZIJa1HS5HQ4NghBrGj8vrGi8Xr2fsCorsjZb2xLZwtY5BCe34uOdNeGRNLP3PCCEAHihiiWPQFeNdTLWNq8LBii50AYbHNzm4RCVPbtpWXXDE0JdAILj5hLL16oJyLNXej96O91VDeB2gltDB8LAygdNaNSlt5vS9dlu+oDW5X17LVaeROGAusvWDAPZOrERkVxT5EDkYEvnyHgyPFeCttyw0rlPspUqoc0l110sqWyxypp2jl0smTsgcUW6ZUbphL9jttLoHXjjHogHi8aIbiGMS7ZdRBdFKjMwmpDpfFAYNY4SE9tpsnZUT6YLe2gqqUgHHJCSqb6kT4tKtOyksY8zJ3WpUXl5Q1BnQg7vaubvqRV3YkAdaAREx.IbBjNDOxIfsPlpQgmOC2iKoAdDm78xKhlOR2pGB0b.JXCCnkjDATge2.2V.9wkkmSthdZ.HrINkpaY8.S3m6+nhEgNXnzzkHIlO1rKeJiSK6DPg82S3tWRmxBAuRyTGvvRJGMW44RRfYp5JPPVm3oTYaw7EBNHT5dYr4df6YDKGP8nAiE5Pq.RJrzAOeQQkAMoWE+znrQOjIsCocPHe4sUi+2Mrk8Y7qFKVA.uHtijI3lB9EBIc.uz8K9lhGT7sEMeWUddaUmpJDH78oAaUsZRJ3uywR7n4SnAO.pA9QzMFBj47TP76mBlcBwIoojwPAuGmIGrfxeeyMnUcRftZrBUP5kZx5WshrlVUQLfWdGblFKRCcE0TcZgpvhL9Ibc6xvm2QM9goW2L1cb0JChOOdxQKg+1rsXo0CGn0qr531vOUukxHzO1SwgVCW.4vtYAMPxTEJiNzkvYaIyZGf6PCuRJVnscEI8e2l6m2bP3uL9j3TgyNAcams+Z7M3p29YbieEa9+zzOnzzuHOMsqzsyQup0yGzXzjl7kCdsEq0QdW+ztMZ+7Ae2REsqrlF1PQCWN3rtxiO1ab0Z0ae4zqitgb+3yG8eHME9Roond+VVZ59I4Ct7S3F4Sj4uQT8tgUJfleNJp5REdHSFm8cEevtl71BwCwCYRmYaGiE1BFU2.+Q.iqdbwcvc87nNxT.tO9zW7w4kDnKEQRFeZehLfAMar5PC3AYNTH6bN0WetQA0XRhr05CjGQ4tZg+D9VorxlCY.kUVqDMm3DHdoSxvk54KepdE.Sb8S8N.2WIatYVJsNOGdM0KcbxGpa33C2UGqtqNZuqNVaWcr9t5Xic0wl+yNpdr6Shjh4IiMHT+gc0mNYXzkS.Fnlsh9KcGqf1C

@d-healey

Finally, got HISE to start the export process without crashing.

Problem line of code was this:

Engine.loadImageIntoPool("*");

I deleted the above and everything works as expected, except now on export I am getting an IPP error. Will search the forum for resolutions as I know I've seen this error popup in the forum already.