@Oli-Ullmann Yes, I do exactly like that

Ah yes this is exactly what is supposed to be adressed with the HISE asset manager - it‘s basically a poor man‘s git submodule to load in / include another HISE project.

@Anhuarcin It could be possible that there are code paths generated for runtime dispatch, so that if the CPU detection shows AVX support, then it will branch to use that - I can imagine that IPP does stuff like that to squeeze out performance.

@dannytaurus so i got hise to build with juce 8, but ive missed a step i think. when trying to export a plugin and build an audio unit i get this error:

Desktop/HISE/JUCE/modules/juce_core/system/juce_TargetPlatform.h:177:8: "Building for OSX 10.10 and earlier is no longer supported!"
177 | #error "Building for OSX 10.10 and earlier is no longer supported!"

im looking in the projucer and it says it set for macos deployment target of 11.0

anyone run into this error?

what is Building for OSX 10.10 coming from?

@JulesV My solution is to use a flag. If the plugin is being initialized, load a specific preset that has my settings. if the plugin isn't being initialized, it doesn't do anything special.

@sletz Another Faust + MCP project by Yann Orlarey: https://github.com/orlarey/faustforge

@ustk ok got it working. Is it possible to update the .preset file without using Engine.saveUserPreset ?

@Daanyoo I just tried to reproduce it on a empty project on WIN, it worked there and all of the sudden it worked in the regular project as well... I am so confused haha

But at least its fixed, thank you guys for your help!!

@David-Healey & @dannytaurus thank you guys. I'll update.

@Straticah Yea I suspect this is your culprit:

https://forum.juce.com/t/br-webview-freezes-daw/64917

Do you have enablePersistence set to true?

Do you get any useful information when running your plugin through pluginval?

@David-Healey Ah that video flew under my radar!

Indeed I do have the same issue, same with the examples in the HISE docs. I've mainly gotten around this just sticking to the old school method of reg variables. I haven't seen many HISE scripts using Lambdas.

Something must be off with my HISE setup in XCode so I'll dig around a bit.

@HISEnberg

Indeed!
I've also got someone after this. But judging from the lack of movement on this, my guess is that it's troublesome to implement

@dannytaurus @Oli-Ullmann @ustk thank you all for the help, all your suggestions work great!

@ustk yeah ill just hide it.

I was gonna have it as part of the interface for the user to see cpu and ram usage, but its not really necessary.

Is there a way to get packages to prompt the user for a location to install a specific component such as samples?

@Casey-Kolb I seem to recall you were doing something like this?

@dannytaurus Oh cool! Bug or not I can at least make my project to work so thanks!

@Bart Wow, that interface is wild! 😮 😂

The synth I'm building is the start of a series, so I'm designing a layout that will work with all of them. Each one will have a couple of unique controls, so they all look slightly different but obviously from the same family.

@David-Healey yes this is what I use… just saying it’s broken too and after looking at the code they both use the same thing, so this explains why

@David-Healey Yeah, me too. But I thought for someone learning how to do the basics of optimising repetitive code into loops, I would just show the basic method.

@goldee What David means, if we're talking about the same thing, is that you can get an array of components and loop through them directly, instead of fetching each one by name.

const panels = Content.getAllComponents("instimg_pnl\\d+"); for (panel in panels) { panel.loadImage("{PROJECT_FOLDER}" + panel.getId() + ".png", "img"); panel.setPaintRoutine(function(g) { var a = this.getLocalBounds(0); g.drawImage("img", a, 0, 0); }); }