@Lindon Firstly, I suggest you change the name and ID of the plugin and re-compile it. As I see you've already done that.

So, are there controls that change the values ​​of the parameters that are isPluginParameter enabled? If yes, you should make them also isMetaParameter. Otherwise AU plugin validation fails. Maybe that could be related to VST3 too.

Other possibility is compiled custom .dll nodes. If the target value and controller value ranges are different each other, that causes crash in DAW. So make sure that parameter ranges (including the middle points) are the same.

@Natan Thanks! I got it, I was just blanking for a bit.

@Fortune Yeah, you can set any properties using the .set() function.

So .set("processorId", "myId");

@yall No idea what FL Studio does, but I'm guessing that the delay parameter marks the maximum msodulation value.

In my experience, waveforms with loops of shorter than about 600 samples are likely to crash HISE, even when loaded into memory. But with waveforms that short, a wavetable synthesizer is the tool to go for, rather than a sampler. Seems to handle it easier.

@Christoph-Hart sweet!

@Adam_G I see what you mean. It seems to be breaking when a MidiPlayer feeds info to connectToPanel and a module at the same time, but that's out of my depth.

You could use 2 floating tiles:

HiseSnippet 959.3ocsV0sbaSDEdW6rErKo+vzG.M4pzYBcjbbRsgKpI1wLdnNwCJT3tLajVGuSj1UrZURLc584wBtGdK3AfK4txYkjsjBlzfGptPi1yORemu8b9VMQI8XwwREB23j4QLD9yHtyE5Y8mQ4BznAH7iHiowZlxJyzAyinwwLeDFW+aLFvM1.kd8mu5.Z.U3wJLgPuQx8XulGx0EVmz6a4AACo9rS3gkhtcuQdRQeYfLAvSchMJh5cA8b1QTSX0HH7CNzmqkJWMUyhQ3MNP5O2cl7JQV7ugGyOKfYV3fbgWTl4gx.eChMVQ8mwC7mrntiQvaYRAKTOiEdFYL2muzdAa7jTGVEYTlOv0pBu5UfmSY3YWBdq.R0JAoOYwFSJjBnyYpTnrIY7nAixLzpBN5mnTLg1k8SIrasej65DEvrk25dsTFcnfBnyurYya+LHT2HVUG3526R04NKUjopFxCXlmKU0ajU0Ok35o3Q5BOlR+gjQBnkbJEJtxEdVrH7uR5Kg.D5WDRufMTAKVlv16aauiEb64eUyoIBOMWJrjhijZ1whsedy21rQy20z51tlNck9LeGkLHfoVoaSCt5tRbaQR3YL0NVWRCRXKCDp+p7K49wudYkco.khQBt93Hl3eq+GkyUvSe+nATME5+v41f3hXJM2.A7.1kvvb19RCx.V7EZYDzq1WFFIEl2.9g57wmrchgARplKN+DX+EwgsnGSJaxAcMTY3mAe44lG7gGth6qmsrSq208lw3mOqP83WNsWN1x.xmmNVb7kLEzpNgJXAnyNegFRiGrnumqYgEVu4ladeUqsLlGLXPp4TR.eD4sMsr1ZIUMxequzZqRybasiw+HgO6ZviS5JPpIPd0OHUWDChWLv9TZPLq46Lz7RZ5Qe.Z5IUoowqfm9uPBat4esy+fDHc519kcZ24Vj.o0dcb1qqy5QB1e.Rn3asqQQqU2861tS6tcsQZ105Br4raGGmc6de5FFBDgK+mSU498eyb8GuZEBIfvszOIfpqplaNBK2ALWVQLwnXHh454Uz89+Rh+9BwmRlv0dyVMFqsBLZN83i.FyOXbSxgSmx7zE.bCxve7iyofnuSlXlAFS0JtYB3njPWnAwiAecAzjazEw0LCCYqsMqMLfKS3mt38vUtSGyZbtSmENQgTOk7TuL0XyQueZpE.Shz+5nA76OvZKGTpBMjGw9E1nPXd6TOOS4+Efn5pyo0ZjytqQNsWib1aMxY+0HmWtF4z4NywH080IZYX13.XXxgYhU3k+ACtN5uwXNp2C

But if you already have it working with just panels, I'd stick with that.

Does anyone have any suggestions for pulling Patch Notes to display on the update GUI? JSON can't handle multi-line strings without /n, or adding a new entry for each line/note. Ideally something like this:

Update v20 Notes * Added a cool change * Added a cooler change * Added an even cooler change

Edit: Okay nevermind, JSON saves the day again

@d-healey Great, thanks!

@Christoph-Hart Makes sense!

@Matt_SF ah I missed that one, thank you :)

@d-healey No, Visual Studio is the IDE (but on Windows only), while VSCode is basically Sublime Text from Microsoft.

@d-healey I'm currently rewriting the SNEX compiler to use another code generation backend - currently it's using ASMJit which is awesome, but I had to manually write the entire code generation logic for x86 CPUs which is the reason why HISE needs to run in Rosetta on macOS (as I don't see myself learning another assembly instruction set...).

The MIR JIT compiler project (which @sletz pointed me to) is a bit more high level since it uses an intermediate language to define the instructions and then generates the CPU instructions for each backend automatically, so this allows me to ditch the entire "HISE has to run in Rosetta" on macOS, which removes a few hiccups.

It's a rather large task though (about 30% of the entire SNEX compiler code has to be rewritten), but this makes it much more future proof as we don't know when Apple is phasing out Rosetta.

I'll also take this as an opportunity to clean up the SNEX code - I realised most things I did for optimisation the compiler output are rather pointless because performance is actually not a critical factor for the SNEX compiler.

@orange this code is impressive! youre a beast

@Steve-Mohican did you ever find a way to link them to the Effect Slots?

@modularsamples Awesome, ill check out the repo!

Im trying with the original way you described. I think Ive fried my brain. I cant for the life of me figure out how to script oninit functions to control scriptnode parameters. Im simply trying to use a button to change the xfade amount. Am I just going mad here?

EDIT: Indeed, I was going mad. I figured it out somehow lol

@musictop
I can't figure it out unfortunately! Would you be so kind to give a short usage example? I do not quite understand how to use it!

Many thanks.

@audiolyf That's awesome. I am happy to know that it was able to give you some clues and that you managed to get it going in the end. 😊

@Christoph-Hart I've solved the first issue and added 8, 12, and 16 bar options. I'll make a pull request later.

For the second issue it seems there isn't a TempoListener in the AudioLooper class. I tried adding getMainController()->addTempoListener(this); but I get an instant crash when adding a loop player. Any suggestions?

Here's a scripted workaround:

const alp = Synth.getChildSynth("audioLoopPlayer0"); const th = Engine.createTransportHandler(); th.setOnTempoChange(false, function(x) { var syncMode = alp.getAttribute(alp.SyncMode); alp.setAttribute(alp.SyncMode, syncMode); });

@d-healey its actually really fun to play with all the expressiveness

@oskarsh Command is Mac speak for the control key. If you press the control key while moving the knob it will do what you want the shift key to do.