• Filter gain modulation not working correctly

    Bug Reports
    15
    0 Votes
    15 Posts
    763 Views
    David HealeyD

    @Christoph-Hart said in Filter gain modulation not working correctly:

    If you then want a modulation to go from -6db to +6dB, you just leave the knob position at 0dB and add a bipolar modulator with +6dB intensity.

    Little bump and also, would this work for nonsymmetric ranges? I ran into one today where I'd like to go from -12db to +3db.

    Also there is still this bug with artefacts and voices overwriting each other:

  • Projucer issue

    General Questions
    4
    0 Votes
    4 Posts
    6 Views
    David HealeyD

    @paper_lung And the Projucer image you're showing is from the ./JUCE/projucer folder?

  • AAX SDK setup

    General Questions
    5
    0 Votes
    5 Posts
    15 Views
    David HealeyD

    @pelle I think you can use ilok cloud, I'm not sure a physical one is required, I could be wrong though.

    It's free to sign aax plugins but you will need a signing certificate for each OS.

    If interested, I have made some workshops that cover the signing process (they don't cover setting up the SDK). https://audiodevschool.com/course-bundle/packaging-workshop-bundle/

  • 0 Votes
    9 Posts
    101 Views
    voxuer1V

    @Christoph-Hart said in Best practice for Real-Time Metering: How to pass dynamic peak values from RNBO to HISE UI?:

    ah here you hit a real limitation - multiple modulation outputs are not supported for RNBO at the moment.

    According to your screenshot the second one is just a peak hold - if you replicate this in scriptnode you should be able to get by with a single output.

    Ah, ok, yes that´s a good idea, thanx

  • 0 Votes
    13 Posts
    117 Views
    David HealeyD

    @duma It will appear near the top of the list - not in alphabetical order.

    These are custom fonts I've loaded (below Source Code Pro)

    20adaa6a-fa7b-4e6a-921b-2a4e779c37fe-image.png

  • "Relay" Mouse Event to component below [UI]

    Scripting
    3
    0 Votes
    3 Posts
    32 Views
    G

    @David-Healey Well, then it gets way more tedious to adjust the position of each element. But fair, that's probably the easiest solution. Thanks :)

  • 1 Votes
    1 Posts
    28 Views
    No one has replied
  • Matrix modulation connection is broken in exported plugin

    Bug Reports
    42
    0 Votes
    42 Posts
    1k Views
    ustkU

    @Christoph-Hart Any news on this? Could it just be an OS issue? Unfortunately I can't test on windows before next month...

  • Updating an existing RNBO export in HISE 4.1

    General Questions
    5
    0 Votes
    5 Posts
    75 Views
    voxuer1V

    @David-Healey Bildschirmfoto 2026-05-11 um 08.17.22.png

  • Cant get Multichannel Plugins to work in OBS

    General Questions
    1
    0 Votes
    1 Posts
    32 Views
    No one has replied
  • 0 Votes
    13 Posts
    93 Views
    B

    @boim98208 @Christoph-Hart Do Flex AHDSR Envelopes require connecting to a floating tile? The issue I have of Flex AHDSR not triggering the samplers was also an issue when I did a compiled build

  • Full instrument expansion plugin parameters

    Solved General Questions
    3
    0 Votes
    3 Posts
    75 Views
    Christoph HartC

    @David-Healey also don't forget the buddy of HISE_MACROS_ARE_PLUGIN_PARAMETERS:

    HISE_NUM_MACROS. Help text in the upcoming docs:

    HISE_MACROS_ARE_PLUGIN_PARAMETERS

    Publishes every macro control as a dedicated plugin parameter in front of the scripted automation slots.

    Default Hot Reload Auto Config 0 yes no

    When enabled, the exported plugin advertises one plugin parameter per active macro slot before any custom automation slot or scripted plugin parameter, which lets the host automate macros directly instead of routing through a UI component. The plugin parameter index reported to the host changes because the macro slots occupy the first positions, and macro state no longer restores from user presets when the preset system is running in exclusive mode (which matches how plugin parameters are normally managed by the DAW rather than by the preset). Combine this with a reduced macro count to keep the parameter list compact.

    Read at runtime from the Extra Definitions, so no HISE rebuild is required. Pair it with HISE_NUM_MACROS so the number of exposed plugin parameters matches the macros you actually use.

    See also: $API.MacroHandler$ -- macro slots exposed as plugin parameters are the ones managed through this scripting object, $MODULES.MacroModulationSource$ -- every macro slot is mirrored as a front-of-list plugin parameter when this is on, $PP.HISE_NUM_MACROS$ -- determines how many macro plugin parameters the host sees

    HISE_NUM_MACROS

    Number of active macro control slots that the project exposes on the master chain.

    Default Hot Reload Auto Config 8 yes no

    Sets how many macro slots are visible to scripts, to the macro handler, to the Macro Modulation Source synthesiser and to the macro plugin-parameter publishing path. The default of 8 matches the original HISE layout and the UI panels that show a fixed eight-knob strip; values between 1 and the project-wide ceiling let you trim a compact product or scale up to a modular rig with many assignment targets. The value is read at runtime, so changing it in the Extra Definitions and reopening the project is enough to see the new slot count without a HISE rebuild.

    Must not exceed the project-wide macro ceiling of 64, otherwise compilation fails with a hard error.

    See also: $API.MacroHandler$ -- slot count seen by every scripting call that enumerates macros, $API.Engine.setFrontendMacros$ -- setFrontendMacros expects a name list sized to this value, $MODULES.MacroModulationSource$ -- chain count of the macro modulation source synthesiser matches this value, $MODULES.MacroModulator$ -- macro modulator slot index is validated against this value, $PP.HISE_NUM_MAX_MACROS$ -- hard upper ceiling that this value must not exceed, $PP.HISE_MACROS_ARE_PLUGIN_PARAMETERS$ -- determines how many plugin parameters are published when macros become plugin parameters

  • How to add Images to Preset Bank?

    General Questions
    11
    0 Votes
    11 Posts
    160 Views
    David HealeyD

    @duma Use local look and feel instead of global.

    Put your code in code tags so it's easier to read - this button: f5964321-82e0-41c8-a04b-3f6a7a167b37-image.png

    Image.load("{PROJECT_FOLDER}Images/BASSLBL.png");

    This isn't a function. Follow what I showed in the expansion column video for setting up the look and feel object and loading images.

  • 0 Votes
    1 Posts
    25 Views
    No one has replied
  • How to visualize RNBO outports (peak data) in Scriptnode?

    ScriptNode
    2
    0 Votes
    2 Posts
    58 Views
    No one has replied
  • Hise Activate informations

    General Questions
    4
    0 Votes
    4 Posts
    157 Views
    Y

    @Christoph-Hart Hi Christoph,

    The mail has been sent.

    Thank you again

  • 2 Votes
    6 Posts
    309 Views
    David HealeyD

    I think Claude got it this time.

  • Development Diary: My First Sample-Based Piano

    Newbie League
    14
    2 Votes
    14 Posts
    557 Views
    O

    4375aef7-38e1-49d3-8aa2-67876313b26a-image.png

    I've finally finished the UI design for the VST.

    Instead of going with a traditional interface, I decided to aim for a highly stylized fantasy aesthetic.

    The layout is mostly set, featuring the Main, Atmosphere, Tuning and Mix tabs at the top. I've tried to keep the essential performance controls (like Tonal Shift, Lid Position and mechanical noises) easily accessible without cluttering the artwork.

    Would love to hear your thoughts on the design and layout.

  • 0 Votes
    1 Posts
    34 Views
    No one has replied
  • Help for Parametriq EQ and its Spectrum Analyser

    General Questions
    5
    0 Votes
    5 Posts
    152 Views
    J

    @David-Healey Thank you!!! It must get old being "the man" here lol. But wow. That is amazingly simple and it totally works for what I want. I really do learn from these snippets as every other issue in my plugin was fixed just by searching the docs and forums. I forced myself to learn on my own, so I really had to weigh the time I've spent against the "ok, I've looked long enough" thing. Again, many thanks and much appreciation!