• Two filters in a row, how to compensate for the signal

    16
    0 Votes
    16 Posts
    1k Views
    DanHD

    @Lindon you misunderstand - I mean have HISE as the FX Plugin within your DAW, so you can work on an FX Plugin project in a DAW itself - like the instrument version...

  • Project name issue - Any one can help with this?

    8
    0 Votes
    8 Posts
    660 Views
    Christoph HartC

    @BWSounds The HWM files are supposed to be located in the sample folder next to the .ch1 files, so in the compiled plugin it's supposed to be wherever the end user chooses to copy the samples (might be a different one than what you have set in your HISE project repo).

  • silence in between values during Chorus Width knob change

    1
    0 Votes
    1 Posts
    191 Views
    No one has replied
  • Most useless Plugin built in HISE

    3
    7 Votes
    3 Posts
    667 Views
    FatMitchellF

    @oskarsh brooooo yessss 🤘🏻

  • Release Trigger Time Attenuate

    6
    0 Votes
    6 Posts
    378 Views
    d.healeyD

    @alfaholic

    Will the fix be included in boilerplate as well and when should we expect it?

    The problem is in the compiled binary of Rhapsody so nothing needs to change in the boilerplate. I'm not sure yet when the next update will be but probably in October, there are a couple of little improvements I'm working on.

  • Note release?

    44
    0 Votes
    44 Posts
    3k Views
    R

    @Christoph-Hart said in Note release?:

    @rzrsharpeprod are you using the latest HISE build? I've fixed the issue that was causing the stuck notes in FL Studio.

    I just saw that in the other thread. I will build it and test it in there. Hopefully it solves the issue, much appreciated

  • Back to the Mac - Installer tweaking....

    8
    0 Votes
    8 Posts
    380 Views
    LindonL

    @d-healey said in Back to the Mac - Installer tweaking....:

    @Lindon said in Back to the Mac - Installer tweaking....:

    @Lindon do I need use Hardened runtime too? Any one know? Otherwise its trial and error for me....

    You should be using this any way when you codesign. codesign --deep --force --options runtime...

    oh, I am, I am....

  • Particles FX - JavaScript Library

    18
    0 Votes
    18 Posts
    980 Views
    Christoph HartC

    @aaronventure It might also be a better UX for your users so they can keep using your plugin while reading the docs on another tab / monitor / whatever.

  • Assistance for updateing 3.5 to latest version

    5
    0 Votes
    5 Posts
    380 Views
    G

    @d-healey Nevermind I got it all to work again. Thanks anyway.

  • This topic is deleted!

    7
    0 Votes
    7 Posts
    29 Views
  • BasicSynth project blank GUI

    17
    0 Votes
    17 Posts
    958 Views
    K

    @d-healey

    Thanks David, works perfectly now. Much appreciated!

  • Disable Slider mouse input

    2
    0 Votes
    2 Posts
    102 Views
    d.healeyD

    @oskarsh Place an invisible panel over it.

  • What does this mean?

    5
    0 Votes
    5 Posts
    231 Views
    Christoph HartC

    @ulrik usually unloading and reloading the FX with the new ID with the combobox of the hardcoded FX editor should do the trick.

  • Polyphonic Voice Issue (Bug?)

    2
    0 Votes
    2 Posts
    153 Views
    Christoph HartC

    @Casmat You need to deactivate the HasTail property of the network - if this is true, then the effect is assumed to produce a tail of any sort so the voice will not be killed by the AHDSR envelope. If you want to use HasTail, you will need to add a envelope.voice_killer node that will send a voice kill signal from within the network when the tail has ringed off.

  • Issue with changing SliderPack amount having saved presets previously...

    2
    0 Votes
    2 Posts
    130 Views
    Christoph HartC

    @DanH said in Issue with changing SliderPack amount having saved presets previously...:

    I'm guessing that the slider amount is saved within the preset data.

    Yup, it stores the slider data as float array so if the length isn't the same, it will resize the sliders.

    You can solve this like any other issue related to backwards-compatibilty of presets: assign a preload-callback to the user preset handler where you preprocess the data and add the missing slider.

    Add a SliderPack Create two presets with different amount of sliders (one should be 16, the other one some smaller number for this example) Use this script: const var SliderPack1 = Content.getComponent("SliderPack1"); const var uph = Engine.createUserPresetHandler(); uph.setEnableUserPresetPreprocessing(true, // enable preprocessing true); // unpack complex data (so the slider pack data is available as array) uph.setPreCallback(function(presetData) { // You can check the preset version against the current project version // to avoid preprocessing if the presets are up to date // (this saves a bit of time but isn't 100% necessary...) var oldVersion = uph.isOldVersion(presetData.version); //if(!oldVersion) // return; for(d in presetData.Content) { if(d.id == "SliderPack1") { while(d.data.length < 16) d.data.push(Math.random()); // fill it up with random values so you see the effect } } });
  • Compile for old wavetable approach

    5
    0 Votes
    5 Posts
    184 Views
    LindonL

    @d-healey ahhhhhhh....thanks

  • Multi-Selection in Viewports

    3
    0 Votes
    3 Posts
    113 Views
    CasmatC

    @d-healey thanks!

  • Change keyboard note colours in a Preset within an Expansion

    18
    0 Votes
    18 Posts
    498 Views
    d.healeyD

    @DanH It's the same idea as setting the component properties in the property editor and using those within LAF.

  • Create Tagging UI?

    1
    0 Votes
    1 Posts
    112 Views
    No one has replied
  • RSA Alogrithm

    1
    0 Votes
    1 Posts
    243 Views
    No one has replied

15

Online

2.0k

Users

12.8k

Topics

110.9k

Posts