@Christoph-Hart Nice!

Does a new issue automatically trigger the workflow?

@Lindon I imagined 10+ years of HISE development would've taught you "I know exactly how all this sh*t works". It's all just apps, code directories and config paths at the end of the day.

Although I suppose if all versions of the HSIE app reference the same Application Support files then it could get messy.

OK, I concede!

@Lindon Unless I'm misunderstanding, none of the HISE versions require you to install VS2026.

And I don't understand why you can't have both VS2022 and VS2026 installed, along with 2 versions of HISE (latest version and older version for your older project) with and 2 copies of the source code.

I know we tell beginners to only have one version of HISE but I'm sure you know enough about all this to make sure each version of HISE references the correct source code and VS version.

@DanH I use Claude Opus and Sonnet in the Cursor IDE (desktop app) with he whole HISE repo and it work great.

Cursor is good about sending the right amount of context and caching where it can.

@David-Healey

@PV3679 Ideally you'd only have one copy of the HISE source on your machine.

Also, it might work better if the source is on the C: drive.

Last thing - are you on the latest develop commit, with JUCE as a git submodule?

@Christoph-Hart

Maybe the 32GB RAM on my MacBook Air means there's enough to go around so it's not like typing through syrup.

I interact with Xcode, and now Visual Studio, as little as possible anyway. Launch, press Build keyboard shortcut, wait, quit.

Good news. I have a fully working volume knob plugin in Reaper.

Had to add MSBuild to the PATH because HISE doesn't detect it properly for VS2026 (I'm guessing the snazzy new Setup Wizard will fix that), and wait a painfully long export time of 22 minutes. But it works!

So this is an x64 VST3 running in an emulated x64 version of Reaper, in ARM Windows 11 in Parallels Desktop, on an Apple Silicon M4 MacBook Air.

What a crazy world.

@lloyduss @David-Healey Sorry to necro this, but just wanted to add my experience.

I followed David's Building HISE on Windows video form the HISE Bootcamp course, and it all seems to have worked fine.

I'm running Windows 11 in Parallels Desktop 26.2.2, on macOS Sequoia 15.7.3 on a 2025 M4 MacBook Air.

I installed git and cloned the HISE repo. Then installed Visual Studio 2026 and built both Debug and Release (no Faust) x64 versions of HISE.

HISE launches properly and responds to scripts, UI actions, etc.

I haven't exported a plugin from HISE yet. That's the next step. EDIT: success, see below.

But as far as building x64 HISE on ARM Windows 11 running on Parallels on macOS, it's all good here.

Note: I didn't use IPP or FFTW when building HISE. IPP doesn't work (the clue is in the name) and I can't use FFTW because I'm building closed source. I'm not using convolution anyway (not directly at least) so I don't think that will matter too much.

@David-Healey I see your Rhapsody website says:

OS: Debian 9+, Windows 7+, MacOS 10.14+

Which sounds good to me.

According to Claude, for Windows:

No explicit minimum Windows version is set in the exported plugin templates. The effective minimum depends on the Visual Studio version and Windows SDK used:

• VS2019/2022 default to Windows SDK 10.0
• VS2017 defaults to Latest SDK
• VS2015 defaults to SDK 8.1

And from Google's horrendous AI results:

• VS2026 Supported Target Versions: The minimum supported target operating systems are Windows 10 or Windows Server 2016.
• The MSVC Build Tools version 14.50 (shipped with VS 2026) has officially dropped support for targeting Windows 7, Windows 8, and Windows 8.1

Does this mean if I use VS2022/26 to export Windows VST3, I can only support Win 10.0+? 🫠

All my existing Maize-based plugins are:

Mac: VST2/VST3/AU back to macOS 10.14
Win: VST2/VST3 back to Windows 8.1

Just trying to figure out what I should be targeting now with HISE plugins?

(I already know I can't do VST2, thank goodness!)

@kliin In the button handler use Engine.openWebsite(); with the URL of your web page.

https://docs.hise.dev/scripting/scripting-api/engine/index.html#openwebsite

inline function onButton1Control(component, value)
{
	if (value) Engine.openWebsite("https://hise.dev");
};

Content.getComponent("Button1").setControlCallback(onButton1Control);

@Christoph-Hart Is there a specific reason you used Haiku? It's not the best model for reasoning about code. It's quite lightweight.

I find Opus to be the best, but it's the most expensive I think, and Sonnet is a good balance between cost and performance.

@David-Healey I suggested this snippet in their other post about this, but I've never used it so can't advise on implementation:

https://forum.hise.audio/topic/14397/hihat-open-e-hihat-closed?_=1771175779155

Have you used it?

Other post(s):
https://forum.hise.audio/topic/14397/hihat-open-e-hihat-closed
https://forum.hise.audio/topic/14404/dificuldade-para-o-hihat

@David-Healey said in HISE Transformation to the new age:

It's about time we got back to the master I think.

Agreed!

@Christoph-Hart When I fixed those bugs, and added small features or enhancements, I went for stuff that [1] had small surface area, [2] I was familiar with the feature, and [3] had been mentioned recently.

Bonus if there was a reproducible example included in the issue or a forum post.

It also helped that a lot of them were useful for my current work.

If something started to get complex or far-reaching I backed off and moved on to another issue. If I recall, some of the ScriptNode bugs were like this.

@David-Healey Awesome!

@Lindon

@David-Healey said in HISE Transformation to the new age:

Ok I think I'm seeing the benefit - I get to be lazy :)

By Jove, I think he's got it!

@David-Healey @Lindon Two OG thumbs up is enough for me. Thanks!