forum.hise.audio

@Lindon so as a work around you can create a Faust based FX and drop it into a Hardcoded Fx slot, heres the faust code for a simple FM FX (as provided by Gemini): import("stdfaust.lib"); // Modulator Controls modFreq = hslider("Mod Frequency [unit:Hz]", 100, 10, 2000, 0.1); modOctave = hslider("Mod Octave Offset", 0, -3, 3, 1); modDepth = hslider("Mod Depth", 0.2, 0, 1, 0.001); // Calculate the effective modulator frequency using the octave offset effFreq = modFreq * ba.semi2ratio(modOctave * 12); // Modulator oscillator (sine wave oscillating between -1 and 1) modulator = os.osc(effFreq); // Convert depth to a delay modulation amplitude (in samples) // A small maximum delay (e.g., 2ms) keeps the FM effect tight and clean maxDelayMs = 2; maxDelaySamples = ma.SR * (maxDelayMs / 1000); delayMod = (modulator * modDepth + 1) * (maxDelaySamples / 2); // Apply Phase/Frequency Modulation using a fractional delay line fmEffect(x) = de.fdelay(maxDelaySamples, delayMod, x); // Process stereo or mono input process = _,_ : fmEffect, fmEffect;

I stopped trying to push PRs because a lot of us are cross fixing the same stuff over and over before having a chance to see them reviewed and merged, unfortunately...

If your Epson printer driver is unavailable , it may be due to outdated, missing, or incompatible drivers, or even a corrupted installation. This issue can also arise after a system update or if the printer was not properly set up. To fix it, first, uninstall the current driver through Device Manager. Then, visit the official Epson website to download and install the latest driver for your printer model. This should resolve the Epson printer driver is unavailable error and restore full functionality.

@GUJIAN The errors about component missing will always happen on the first compile because the components don't exist at that point. On the second compile the errors should go away. Also Rhapsodist isn't "fixed" yet, so expect breaking changes. Once I've stabilised it I'll make some documentation.

@David-Healey Oh, you mean like this? 😂 CleanShot 2026-08-29 at 13.12.10@2x.png Claude says: It's painting the warning in the wrong tab, and it's a false positive from conservative metadata. The metadata classifies every sendRepaintMessage variant as unsafe wholesale; a finer classification ("warning: fine to call, just don't do it per-sample") would be more accurate. The two points are: (1) ApiDiagnostic needs the callback id so the editor can place the marker in the right tab, and (2) sendRepaintMessage's callScope should probably be "warning" rather than "unsafe". Glad I don't use the HISE script editor anymore. That would confuse the hell out of me! 😜

@dannytaurus agreed about Claude, has become unusable in my opinion, deep dives and minutes of ruminations for simple questions, eats tokens like crazy. I use cursor for everything now.

Correction, and a reproducer with counters I need to correct my own post. The central claim: native slider drag jitters, script writes are smooth. That is wrong. I was judging both by eye. The script path only looked clean because the ScriptPanel handle I was watching spreads the 0–1 range over ~676px, while a rotary knob's pointer covers roughly 35px. The same value wobble is unmistakable on one and sub-pixel on the other. So I replaced the eyeball test with counters. A timer drives the parameter through a strictly monotonic ascending ramp, 400 steps, no mouse involved anywhere. Any decrease is by definition a second writer. The script also counts callbacks against writes, and checks whether the value handed to the callback agrees with getValue() at that instant. Conditions: 48 plugin parameters, a panel repainting at 60fps to load the message thread. HISE: 402 paints, 401 callbacks, 0 backward, 0 skew. Ableton 12.4.3, VST3, same build, three runs: 555 / 562 / 567 callbacks against 401 writes; 153 / 161 / 166 backward; skew 0 / 1 / 0. The excess callbacks and the backward steps track each other almost exactly — nothing is lost or reordered, something is injecting extra writes. Every backward step is exactly one ramp increment: cb 0.007500 -> 0.005000 cb 0.012500 -> 0.010000 cb 0.032500 -> 0.030000 The host returns the previous value while the script writes the next. Skew is 0 or 1 across runs, so these are real writes landing in the store and notifying normally, not display

@David-Healey It seems to have fixed the panel contextual as well! 👍

"OK, that's it. Thank you."

@dannytaurus said in Claude screenshot crashes Hise : so I don't think the recent commits introduced it, they just make the message thread busier so the 1 s timeout trips more often. Yes that's it, in fact it was crashing less before for the mere reason that the project I am working on at the moment is way bigger. UI takes long time to recompile, that's the trigger... So in the end it just needs 2-3000 sec timeout, should be enough for most cases... I'll test and make a PR when I have a minute 😉

@Lindon Sorry yes my typo... Glad you weren't being charged 5% 😂

@ustk have you attached a lambda? I forgot the exact syntax but you can add a void f(double) lambda that reacts on simple value changes