@ulrik Screenshot_2026-09-08_at_8.08.09_PM.png now what
Hise Forum
forum.hise.audio ↗NodeBB-Forum auf Englisch. 6 beobachtete Rubriken: Blog Entries, ScriptNode, General Questions, Bug Reports, Scripting und C++ Development.
- Diskussionen pro Tag
- 5
- Eingesammelte Diskussionen
- 164
- Beiträge pro Tag
- 20
- Rubriken
- 6
- Beobachtete Quellen
- 7
- Software
- NodeBB
Neueste Diskussionen
Alle 4 Stunden aus dem öffentlichen Feed des Forums eingesammelt. Wiedergegeben werden nur Titel, Link und der Anfang der Nachricht; jeder Link führt zur Quelle zurück.
@David-Healey Great info. Thanks!
It looks a lot like UVI Falcon
For those looking for solutions without coding Empire VST - Professional VST Plugin Creation Create professional VST instruments and effects for Windows and Mac, compatible with all major DAWs — without writing a single line of code. Démo : https://www.youtube.com/watch?v=B9K0ArLb_JY
@Christoph-Hart Great, thanks. Where do I get a copy of the current licence? I was never sent one when I started paying.
@resonant - I think Dave's right there are not any real problems these days getting the plugin into the "system" folders on a Mac (but its been a while since I've done it as Im nearly exclusively on Tracktion these days) so caveat emptor... but every other problem (locations and content) are still there which is what the CR Setup componentry is there to resolve.
@dannytaurus said in No-argument sort() is a no-op on strings - bug? : So you think the docs are wrong, rather than it being a bug? Could be either
@David-Healey Done 👍 ABSOLUTE RULES now has a MINIMAL CODE COMMENTS entry. It says to comment only what is non-obvious, contradictory, or missing from self-documenting code, to keep needed comments to one line, and to point at the forum topic or GitHub issue/PR for more context. Comments & Documentation under Code Style carries the detail with three examples. The FL Studio comment from PR 1040 and the instrument-plugin note beside the confusingly named macro in PR 1039 are listed as good comments. The multi-line host-echo paragraphs from PR 1037 are listed as too much, with the one-line-plus-reference guidance. It also bans comments that restate code, narrate control flow, mark edits, or leave investigation notes behind.
@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.
164 Diskussionen eingesammelt seit 2 September 2026. Dieses Forum nach Stichwort beobachten →