@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 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! 
@lijas90 Also, it could just be a caching issue. Try clearing the AU cache.
I don't like providing destructive terminal commands, especially rm -rf ones, but this one is nice and simple.
AT YOUR OWN RISK!
killall -9 AudioComponentRegistrar
rm -rf ~/Library/Caches/AudioUnitCache
@lijas90 AU identity uses Type, Subtype and Manufacturer.
Type = aumu (for instruments), set by HISE during export
Subtype = Plugin Code in HISE settings, 4 characters
Manufacturer = Company Code in HISE settings, 4 characters
If they're all the same, then Logic, and other AU hosts, will only see one plugin.
To verify, check the Info.plist for each one to see if they're the same in the exported plugins.
@lijas90 Can you expand on this please?
Do you mean only one instance of a specific AU on a single track?
Or one AU of any type on a single track?
Or one instance of a specific AU across multiple tracks?
Of one AU of any type across multiple tracks?
As far as I know, in Logic you can only have one AU instrument on a track.
Here is Logic with three instances of the same AU open on different tracks:
In Reaper, you can put multiple AU instruments on a single track and the MIDI flows through them.
Here is Reaper with three instances of the same AU open on a single track:
@Daanyoo Are you sure the DAW is detecting the new version of the plugin?
My plugin has 3 radio buttons to choose LFO waveform. Works great in the UI but I'm trying to figure out how to automate it.
Logic's Test Tone plugin has a similar situation, where it's a set of radio buttons to select the waveform in the UI but you automate it with a single stepped range called Waveform.
The only way I can think of doing this is with a hidden slider, used for automation only, that sets both the waveform in the LFO module and the state of the UI visible radio buttons.
Or is there a better way?
@David-Healey Right, makes sense.
I'll dig around some other plugins and see where they put their data can assets, to get a feel for it.
@David-Healey said in Mac installer for audio sample libraries best practices?:
Data files (like AudioResources.dat) needs to go in the user's Application Support folder.
Why not the system Application Support folder? /Library/Application Support
@David-Healey I'm still not 100% sure why the need to install to both system and user spaces on Mac. Can you explain?
As far as I understand, it's to install the plugin to the system /Library folder (for all users) and the samples to the user ~/Library folder (for the current user only).
What's the point of installing the plugin to the system folder for all users if the samples are sandboxed to a specific user? Other users on the machine won't be able to use the plugin without the samples.
The only reason I can think of is that DAWs have the system plugin folders set as default (/Library/Audio/Plug-Ins) but not the user plugin folders (~/Library/Audio/Plug-Ins).
Meaning some DAWs might miss plugins installed to the user Plug-Ins folder unless the user updates the search paths.
I don't know for sure what plugin paths DAWs use by default. Would be a good one to look up.
@WillowWolf With Araelium Package Builder, are you able to install to both /Library and ~/Library in a single installer?
Plugin installed in /Library/Audio/Plug-Ins
Samples installed in ~/Library/Application Support (aka /Users/[USER]/Library/Application Support)
Or are you installing the plugin and the samples to ~/Library?
@EltonFelix There's a snippet for choking MIDI notes here:
https://docs.hise.dev/tutorials/midi/index.html#choke-off-note
@David-Healey said in [URGENT] Build Fail: 66 Errors in SharedCode (math.h, ctype.h missing) - Windows 11 / VS2022:
removing the export option from the precompiled version of HISE
Yes, that would be good. The precompiled version of HISE itself is also a support ticket generator.
@David-Healey Is it being removed or is it getting a makeover, like the installer?
Either is better than the current state. It's basically a support request generator! 
@David-Healey said in HISE Transformation to the new age:
How is it for adding features or fixing bugs in the HISE codebase?
https://github.com/christophhart/HISE/pulls?page=1&q=+is%3Apr+author%3Aweavermedia
All my PRs, except the oldest two, were made in Cursor with Claude.