@dannytaurus Seems to work perfectly

@Nater Looks like you can still get the VS22 installer from TechSpot: https://www.techspot.com/downloads/7493-visual-studio-2022.html

@dannytaurus Excellent, thanks

I would like to give this one a bump. According to everything I read on the JUCE forum, the popup menu is by default opaque, unless you set PopupMenu::backgroundColourId to a colour with an alpha < 1.0.

I've been through all the HISE popup look and feel functions I could find and set this property to transparentWhite but still the combo boxes show a white background.

@Christoph-Hart Any ideas?

@johnmike said in Plugin Shows Sample Installation Panels on Startup Even After Configuration:

how do you only show the "choose sample folder" and not the HR1 install samples one

This is all that should be required. Try it and report back

HISE_SAMPLE_DIALOG_SHOW_INSTALL_BUTTON=0

@johnmike said in Plugin Shows Sample Installation Panels on Startup Even After Configuration:

"ENABLE_APPLE_SANDBOX=0"

The default is 0, so there is never any need to use this. You would set it to 1 if you wanted to enable the sandbox, but I have no idea why you would want that either or exactly what it would do.

@Felix-W said in Multi-shape and multi-colour SVG:

This is an interesting approach, but Base64 SVG doesn't seem to work on the Button component. I've tried a few methods, but they haven't worked. Does anyone have a solution?

Got a snippet?

@mistercw said in Creating a lightweight custom sample player (not using Sampler or AudioLoopPlayer):

is it possible to hide that from the user, giving them a way to add their samples without using the sample mapping interface?

Yes you can tuck it behind whatever interface you choose. All of this is custom behaviour though that you'll have to script, there is no built-in handling for it.

I recommend starting simple with 10 or so samples, then expand out once you have it working.

@daniloprates The result is exactly the same. Export As is the "old way" the Compile Project dialog is the new, more user friendly way, but it's buggy so I just stick with Export As.

@mistercw I'd use the sampler. You have 3 dimensions for mapping - pitch, velocity, RR group. There's also the advanced mapping editor but I don't think it's ready for real projects yet.

You can use scripting to select the sample you want to trigger based on your requirements.

In order to be able to change the start position in real-time I think you'd need to load the entire sample into RAM, so you'll want to set this in the sampler's pre-load settings.

@DJJD12345 Show me

@DJJD12345 said in xcpretty Not Detected After Install on macOS Tahoe M1: Compiling Fails in HISE Export:

hise thinks it's 92x92.

What do you mean by "hise thinks"?

@DJJD12345 said in xcpretty Not Detected After Install on macOS Tahoe M1: Compiling Fails in HISE Export:

Hise keeps thinking they're 92x92

What do you mean?

@daniloprates that's the current method but that's 4 function calls each time i want the position of a control.

@tjrob

That shortcut takes you to the project's App Data folder. This folder is created when you compile and run your plugin. It's used to store plugin data files on the end-user's system. It's unrelated to your HISE project folder.

https://docs.hise.dev/working-with-hise/menu-reference/file/index.html#show-hise-app-data-folder-in-explorer

https://docs.hise.dev/working-with-hise/project-management/index.html

Which shortcut are you using?

We have setPosition but it would be useful sometimes to be able to get the position of a component. I can see that there is already a getPosition function defined in the source which returns a rectangle type, but I can't figure out how to wrap that into a script function.

@Nater Yeah Windows takes a lot of space - I haven't seen a drive that small for years!

@Nater Ok go to the compiling HISE section of the Bootcamp

When you get to the part where I tell you to write git checkout develop. Instead use git checkout 3f4db538e839a58a8c3f91d2b4773f1b453aa2a7

That's the commit hash from the end of November. If it doesn't work you can keep trying older ones until you find one that builds. Christoph will probably fix the develop branch tomorrow though so you won't need to wait long for the latest.

Remember to clean the build and reopen the project from Projucer when switching commits.

@Nater said in Errors in Visual Studio 2025 compiling hise:

So I think I just grab a new git code and paste that in somewhere right?

Have you installed git on your computer?

@Nater That one isn't building for anyone currently. Try the one from the end of November.