@ustk sorry, I didn't see that. Thanks for reporting the bug! :)

@d-healey sure I'll do that...

@ustk It worked for me once, but I never used it since then :)

@d-healey yes

@Christoph-Hart Thank you!

Should be good now.

@ustk yup, that's correct :)

@d-healey thanks for your tips. I will reorganize those files before distribution

@d-healey Oh I'm not building universal binaries yet. It's definitely something in those commits not playing nicely with my branch. I was able to compile fine just a week ago without the last week of commits to develop. I ended up just cherrypicking the SFZ import commit from Christoph for now. Thanks for the help!

Link Preview Image External global scripts by davidhealey · Pull Request #316 · christophhart/HISE

favicon

GitHub (github.com)

Ok I fixed the assertion. HISE was looking for external scripts in the ScriptProcessors folder and of course they weren't there, so it was triggering the jassert. But it didn't need to go searching for them anyway because external scripts already have their full path in the Script property of the xml.

So I just skip the entire function if it's an external script - might make loading some projects a little faster too.

The next issue is when you connect a script that's in the global scripts folder HISE was using an absolute path, which obviously isn't good if you decide at some point to move or rename one of the folders in that path.

Now I've set it up so that if you connect an external script from the global scripts folder it will add the {GLOBAL_SCRIPT_FOLDER} wildcard to the path and it also will translate this back to the global path you've assigned in project settings when you reload the project. I've tested this within HISE and as a standalone build and it seems to work without issue.

@RastaChess Try right-clicking. Also make sure the interface designer is unlocked (click the pencil icon).

@d-healey hmm yeah - it's been that way for over 2 years....what is that fella who wrote this thing doing?

@Lindon yeah that fixed it - thanks for your help both of you...

Hello @ustk
How is this whole method works?
Just want to understand the RSA using a dummy License in the plugin.
I'm trying to create just a a demo to get an understanding of how this whole thing works, but there's no documentation and as well as I'm not getting fulfilling inputs here in the forum.
Seems like this method is more effective than the simple copy protection.
Any help is appreciated

@d-healey Logic Pro automatically request and sync the Sample Rate of my Apollo and re initialize the Core audio after any Sample Rate change in the Project, im not using external Clock sources so its not an external problem and in Reaper and Luna works perfectly in any Sample Rate and the problem is only in the audio affected by the Send Container.

@Natan is there a way for the user to interact with this polyshapefx graph?

Issue has been resolved - https://github.com/christophhart/HISE/commit/1b51f15c36d27419712309b279cfde6e097fcc9e