@d-healey Very interesting. I'm not using any special characters in the names here. The exceptions posted above were traced back to launching HISE in debug mode (without any projects or expansions loaded).
@Casey-Kolb Yes I rewrote some of the monolith file handling stuff to allow split monolith files (for samplemaps that have more than 2GB of samples). This might have introduced this issue.
I'll take a quick look. I second Davids advice that it's not the smartest thing to do but now it's in the open and you don't want every user to reinstall stuff because of that.
@ulrik there鈥檚 loads of possibilities and potential but it鈥檚 also full of headaches and eats up so much time! However I am using it in projects as I need things that are not available anywhere else and it鈥檚 stable (eventually!)
@crd Yes, using target intensities works for the global LFO (and there's a solution for scriptnode) but not the other modulators, but you're right I should have been more precise. I'll edit my post.
Just stumbled upon this the other day, but I don't really use global mods myself.
@Lindon Stuff like this happens when the component must be intransparent. This prevents a repaint of the parent component and increases rendering performance, however if you don't fill the area with a transparent colour, it uses whatever is in the graphics card buffer at the moment.
@BM_FORUM Yeah, I removed almost everything related to 32bit builds in the last days because I think those days are long over. We excluded 32bit from PercX 2 years ago and to this day we haven't received a single request for a 32bit build.
Forum discussion https://forum.hise.audio/topic/5068/au-write-automation-still-broken Commit ecd5f15 Conditions to reproduce the bug OS: macOS HISE: N/A Compiled Project: yes Problem Description AU parameter Write Automation is not worki...