@griffinboy I'm not at that point yet tbh. Most of what I'm working on right now is audio analysis in realtime and sample playback. I do really want to do a distortion/saturation effect of my own at some point though!

@bendurso yes you're right, if I add a button, it works:

HiseSnippet 1210.3oc6V0saaaCElxwJn1aqaAXO.Dd23NjDXY6j13fg5Dm3Mike7pSKJvvPAsDkEQnHEjnahaQw5ixdF1ivdR1ivteWjcnjrkTsSWBv5cSAHl776GOmCO7LLTZSihjgHipWLKfhL9byQyDJuddDl.M3HjwCMOkDong3DRGNKfDEQcPFFq88ZBFUJih+9qmdHgSD1zLRHzKjLa5ILelJi5vt+Hiy6SbnWv7yIc6tCrkhdRtbJfm0LafBH1WRlPOinEqjI5GHQdHiu0bmlsra67XmlM2YucsI6R2yk35Z0xoc6cexdVs1iz9I6RarCxX8icXJY3HEQQiPFkOT5Lajm7JQhCdAKhMlS0arPi.OmPtuj6nOhZpnddLtyv4ApHDXkgYgs0RBaes4oLG1B5YguuJlANSi7APiREg2ZEfmUd30HG7VAjLxAoxIPZCyQ1gr.UFGMd9LyABHa5Rf7TdnjHKpTPYydRPBgZaexkz9gvlEZTe2FM1DC+6Q6WsJjqhT3WSBwmRrCkmPbweGdtt1gT3HchzlvOQJu7.gSeJkWGz6XwDlftcDUEaapvIV8n5+bsS5edsMw5erp8KZWL2vZoGH3fdiTy3zQdTppdspX3S4gea7B8mKXvsbI9L9rN3CBYD9l3mQmLkSB2egPEkNh8FZGr0iCtd+hLthxl3o5f2oQiLNJ50psHb1DQGrMUGVx3EPbbXhIfwZDbMdm7FbrLzgFt0XoRI8AA.9QRNyA+MMOP+Whjuq5B3ssCI7x3UusZE8O1PxOrCdLGtQrrzbMTWg3W4wTzkDe7T.Fh7hOFr5jP4Tgi1ESWnRsh44CiUrYtz7DppmzOPJfM0qkxOVqz05L2RUAySqEsdetjnf.3ELN05V8QAoh8TAJ+q9iEWFgcmJrULo.KEIH0R6tPIut8besIfJHV7npPPZIejUG1iC2gpGKJ9o3ZI4hZ3NvRcRTCwJ4BF2KEeG.3OVnFB.ZalB8dDNWmIq+gmI84N2A9Lohdtnd7AqJTW7grbcWIuTiwogqjstWd3GSw5ho9iog4CqZAg9UEaBZd6MAy2i1NItjSPoXffoNOfJtsN2nzfIzvrTJp.QUwsKeXZ6xjPGhAcEqXlFGQwPN+6Zn6g5MWg5OevQDEQ23NER.LCngJlNBXbD80vylIswqXdDM5RkL.b0hB.nOtJ8cmD2lu.M14eoYgZVz0Kb+6+otyxuIE.yeGqPW4gDAkiFOY9ixUVe9A.Zr3mQ8lat48Eo1LOYcaykE9JlixaAR9y2z0Ktk6BJ+lpKJ2It7cHOkcJ6RycJ69qErzCtCoLvRlF+tABMSu3OfE4iBvQ34KGEZ0pk6JhBarwF+8JiB2jLNzRubCyLHcfGsTEGjPOtUJC3hUgWu0uPKhXpY4GG6+roKtqPbCygLks2pwXoUfQ88vOAXLclruv7XWWpsJCfkM6+xOMCfgdlbp9x1oDUHSW6b1T+QPl1lBdW.WhzM1LJoabjrugduNBLBtqEuQWPjxzRu2Hko0blHe8UxWYmz4QO02Cho.XRDOgroIL5zxMa7gAPekscQyrPo00JYce0BFF++03V0POx+ASgY8RtEfPmN73398FFGKHPAUbwG5e.MToxAC

I'll take a look, but it shouldn't be a problem to recursively set the classes with the method.

Slightly off topic question, but doesn't the sampler kill active voices and cause an audio dropout when you adjust a samples parameters like the start/end for the sample or the loop region???

@HISEnberg Ok, I think it is cleaned up enough to pass along now. If you like we can do a video call or chat to talk about how to adapt it to your project. I'll send you some files in a message.

ohhh interesting! Thanks guys! I'll play around more tomorrow then, see what I can do

@Jambo Alrighty sick! I found the VST and brought it into my daw and it worked!! Thank you both so so much for your patience 🙏🙏🙏

@Christoph-Hart Single time for fade into and fade out of legato sample is fine. Curve has been very important to adjust in the past, but I realize that's always been in the context of typical unaligned legato, where it might play in or out of phase.

So, going on the assumption that the phase-align-o-matic does its job, the crossfade should be linear as it is now, and probably doesn't need to be adjustable.

@Onik-Sisodiya said in Issues when exporting as instrument, however I'm able to export standalone:

@d-healey Yes I did but it resets to no network when I restart the project or xml

did you create your HC FX and then save your project?

@JulesV
I don't remember your snippet exactly, but yes, eqBrdCst.setEnableQueue(true) is important for the logic to work. Christoph gave me this tip when I was writing the script.

@Dan-Korneff i don't see this option, where i can find it?

@bendurso Fixed. The problem was actually caused by my filters script, which overloaded the system with macros.

@Lindon really depends on what sound and modulation possibilities you want to go for. Whipping up comething custom in faust should be straight forward. Habe a look at the boss or moog clusterlis schematics, they are usually among the most recommended flangers. Probably airwindows is another good source to start and easy to turn into a node. I had a thread how to do it now long ago you should find all you need in there

@d-healey There's no setting for that with wavert in my daw

@bendurso It means developer will have to pay Apple in anyway whether developing for Free Plugins or Commercial one.

@rglides legend, thank you!

@d-healey got it working, thanks!

@pcs800 It's something similar to an instrument for Kontakt. You just have one plugin, and then you make instruments (expansions) for it with different images, samples and presets.

You can check here: https://docs.hise.dev/working-with-hise/project-management/expansions/

And David's video: https://www.youtube.com/watch?v=VsQTOxOOd9s

If you're new to HISE, expansions might not be the best place to start :)

@Sawatakashi Lol not really I only set this up last week but I had similar issues.

For the first issue on Windows you have basically solved it. When you build the AAX in Visual Studio (so the one that is in HISE's SDK folder), set it to static release. Each time you build your HISE project it will build against this version and you will be good to go. There is a post about this on the forum somewhere.

When building the AAX SDK on Xcode it was a bit more trial and error for me but I think what happens is HISE is only designed to build for arm64 or Intel slice  x86_64 (depending on what you set in your Projucer). I ended up asking chat gpt for the solution to the universal binary and it gave me the right response. I found the terminal command (option 2) to be more efficient:

Option 1 – Re‑build in Xcode (GUI)

Open the project again
Libs/AAXLibrary/MacBuild/AAXLibrary.xcodeproj

Target & Build Settings

Select the AAXLibrary_libcpp target.

In Build Settings

Architectures → Standard Architectures (arm64, x86_64)
(don’t choose “arm64 only”).

Build Active Architecture Only → No (Debug and Release).

Excluded Architectures → (leave empty)

Choose a universal build destination
In the scheme selector (the drop‑down next to the ▶︎ button) pick
Any Mac (My Mac) or Any Mac (Mac Catalyst) – not “My Mac (Apple Silicon)”.
That generic destination tells Xcode to build all valid slices.

Build (⌘B)
When it finishes, run:

lipo -info "$HOME/HISE/tools/SDK/AAX/Libs/Release/libAAXLibrary_libcpp.a"

Expected output:

Architectures in the fat file: libAAXLibrary_libcpp.a are: arm64 x86_64 Option 2 – One‑liner with xcodebuild (CLI)

From Terminal inside Libs/AAXLibrary/MacBuild/:

xcodebuild -project AAXLibrary.xcodeproj \ -target AAXLibrary_libcpp \ -configuration Release \ -sdk macosx \ ARCHS="arm64 x86_64" \ BUILD_LIBRARY_FOR_DISTRIBUTION=YES \ BUILD_ACTIVE_ARCH_ONLY=NO

This explicitly asks Xcode to build both slices and drops the fat libAAXLibrary_libcpp.a in:

Libs/Release/libAAXLibrary_libcpp.a
Check it with lipo -info as above.