@musicayciencia First thing you should do is build HISE form the source.

Ignore the Releases section on GitHub - 4.1.0 is far too old to spend any time debugging it.

Follow the "How to Compile HISE" details further down the repo page.

@39oririn go to + and add VS2022 and then check the path of vs22 in "modules"

so cool my friend!

@griffinboy @lalalandsynth @Chazrox @ulrik @Oli-Ullmann @scottmire thanks everyone! 🤙🏼 😎

@David-Healey Yours always seems to be more generally useful than mine though 😂

This one is pretty niche but I'll likely be using single column preset browsers in most of my plugins, so it's really useful for me.

@dannytaurus Yes, one of the many side effects of AI, reduced interaction.
I asked a friend to come over and teach me proper git procedure could have asked ai , I wont.

:)

@digi @lalalandsynth lol I included the 'Control Token' feature so you can mess around with it and see if its something we should keep. See at the bottom of every 'ARC' layer there is a 'Token Control' toggle. Toggle that one and you can choose between controlling the arc with either a 'GlobalCable' or by connecting it to the components native 'Mod' values. In theory it should work, but I suck at wiring up the mod matrix so I could use some help testing this out. I would not use the GlobalCable mode just yet. I think I have to nail down some of the Hise code gen for this part. Try the 'Native' mode and hook up the knob to a mod source in HISE. I got it to "WORK" as much as seeing the mod source value move the arc knob properly but I still dont know how this will do in actual use case. Lmk what you guys think about that one. 🙏

@ustk Can you please give it a go if you have a minute? I know you're pretty well versed in using modValues.

(at the bottom of each ARC layer properties)
Screenshot 2026-07-27 at 4.40.12 PM.png

@blush It's listed under the PathTypes section here: https://docs.hise.dev/ui-components/floating-tiles/plugin/draggablefilterpanel.html

https://docs.hise.dev/images/custom/filterpathtypes.png

@lalalandsynth It depends on the specifics of what you're doing. If you already have a paint routine or look and feel for the component then it's probably better to include the value/label in that rather than add another component to the UI. But if you're using filmstrips a label might be easier - although you probably still have to add scripting anyway.

I also added a LineSpacing and LetterSpacing to the Markdown renderer so I can style it to match my plugin.

https://github.com/christophhart/HISE/pull/1008

Had Claude fix this bug and also added an optional scaling parameter to the screenshot function: https://github.com/christophhart/HISE/pull/1004

I found when unloading a Full Instrument Expansion the automation xml was getting wiped. Made a little PR to fix it.

@David-Healey I was looking for a simple one-man-band way to get past the windows "smart screen" - but thanks anyway....

@Christoph-Hart That is just way too convenient ! 😲

@lalalandsynth ahh yup. 👍

Update: Claude-generated gist here of the suggested patch: https://gist.github.com/weavermedia/3fc4a419920fcda8de389a89d7aec68d

This is Claude's minimal fix: https://github.com/christophhart/HISE/pull/1003

I've tested it and it appears to work. The fix just closes each file reader after reading the data into the preload buffer.