@Christoph-Hart Thanks! Just to clarify, is it also free if I want to sell the plugin commercially and have it work with the Pro Tools standard version (not the dev version)?

Hi everyone,
I’m trying to build my plugin in AAX format but the process isn’t entirely clear to me yet. I have a few questions:
• Is a physical iLok dongle required, or is iLok License Manager sufficient?
• Do I need to register as a development partner with Avid, and is there a fee involved?
• What’s the correct procedure to get started with AAX development?
Any help or pointers to the right resources would be greatly appreciated. Thanks!

@WepaAudio Have you find a way to record the midi notes directly on the instrument track?

Hi everyone,
Following up on this thread — I managed to get MIDI recording working on a separate track (see: https://forum.hise.audio/topic/11556), so that part is sorted.

Now I’d like to take it a step further: I want to trigger MIDI notes from UI components — specifically an XY Pad and/or buttons — and have those notes sent out to the DAW for recording, just like a standard virtual keyboard would.

Has anyone implemented something like this? I’d love to see a working example or at least a pointer in the right direction. Any help is appreciated!

@hisefilo Have you solved this ? How could I record midi notes triggered by UI components? Thanks

@rglides have you solved this ?

@David-Healey Thanks, that was exactly the problem. How do I install the images separately? I just can't figure it out.

@David-Healey 60MB (audio + png)

@David-Healey yes

@David-Healey I managed to build HISE successfully, but now when I compile my project I get the following error. On macOS everything compiles fine.

Finished saving: Visual Studio 2022
Finished saving: Xcode (macOS)
Finished saving: Xcode (iOS)
Finished saving: Linux Makefile
Compiling 64bit Instrument plugin STEPS ...
MSBuild version 17.14.40+3e7442088 for .NET Framework
win\Binaries\Source\PresetData.cpp(857098,75): error C1060: compiler is out of heap space [C:\Users\name\Desktop\HISE DEV WIN\Steps 0.1 win\Binaries\Builds\VisualStudio2022\STEPS_SharedCode.vcxproj]
  STEPS_VST3ManifestHelper.vcxproj -> C:\Users\name\Desktop\HISE DEV WIN\Steps 0.1 win\Binaries\Compiled\VST3 Manifest Helper\juce_vst3_helper.exe
!Compilation error. Check the compiler output.

@David-Healey

@David-Healey when I try to open a project form HISE generates 40 pop up windows to select the project folder and then crashes

@pelle I've built it with the submodules but crashes

@David-Healey develop branch ?

@dannytaurus macOS Sonoma 14.4 (M3 pro), Parallels Version 26.2.2 (57373), Windows 11, Visual studio 2022. I've installed HISE 4.0.0 using the installer.I've tried with a simple knob but I have the same result

@dannytaurus When I press any key, the terminal window closes immediately

Hi everyone, I’m trying to compile the Windows version of my plugin on a VM running Windows via Parallels, but at some point the build process prints the following and stops compiling. Can anyone help?

On terminal the last thing that I see was :

@David-Healey Solved! I've simply moved the font outside the font folder and removed the "Font/".

Hi!
I’m trying to compile the same plugin on both Mac and Windows. I’ve noticed that the issue is probably related to path separators — macOS uses  /  while Windows uses  \ . However, when I change it, the code editor throws an error. How can I handle this?

Engine.loadFontAs("{PROJECT_FOLDER}Fonts\BrittiLight.ttf","BrittiRegular");
Engine.setGlobalFont("BrittiRegular");