• Exporting plugin with expansions?

    8
    0 Votes
    8 Posts
    631 Views
    LindonL

    @David-Healey said in Exporting plugin with expansions?:

    @filipalex96 said in Exporting plugin with expansions?:

    The actual samples used by those samplemaps are in the MAIN Samples folder

    The expansion's samples should be in the expansion's folder.

    Well..... not the way I do it....you can put the samples in the Linkfile directory - where all your factory samples are, so in your sample map it just looks sorta normal e.g.

    FileName="{PROJECT_FOLDER}fatty_F#4.wav"

    Essentially the sample map tells HISE where the sample data is by using this {PROJECT_FOLDER} token, which means "the folder wherever the end user decided to keep the samples, who's location can be found in the Link file"

    You just need to tell your sampler where the sample maps are.... it already knows about your factory sample maps - they are shipped in the plugin, so you just need to tell it where each expansions maps are...

    So you will need some meta data to differentiate your "factory" maps from each of your expansion maps, so my factory meta data for this location looks like this:

    { "VoiceMapName": "FireBreak" } note theres no actual location data in here, HISE, and your product already know about this map so none is needed.

    whilst my expansion meta data looks like this, for an expansion called AlarmSemaphores:

    { "VoiceMapName": "{EXP::AlarmSemaphores}AS_Absentees" }

    OK so another of these token things.. this time {EXP::expansion folder name}, which tells HISE, and your product to go look in the expansions folder for a sub folder called AlarmSemaphores, and there to look in the SampleMaps folder

    So at this point you only need to set the expansion type to FilesOnly and have a way to place each expansions folder structure, which is entirely empty except for the sampleMaps folder which holds all the sample maps for your expansion.

    So your Expansion installer will need to:

    copy the sample data (.ch1 files) to the Linkfolder

    Create a folder structure in the products Expansion folder
    Here's an example:
    c05bee1c-3a62-45af-be64-e770c392ae99-image.png

    Inside each expansion folder create the std expansion folder structure:
    6cf9a22c-a4ba-4744-bfdd-634d0a309ec4-image.png

    inside the SampleMaps folder add the sample maps:

    34e59a36-b8f8-4049-940d-1a2c2f3e392f-image.png

    Create some meta data file that describes these maps and where they are so your product can find them...

    If all of this is "too hard" then once the Asset Manager is up and running I will add a (for fee) version of this system so getting up and running should be pretty painless...I've been using it on HoriZEN, and now Atmosia 3 for over a year and it seems to work fine.

  • Multichannel Inputs and Outputs

    2
    0 Votes
    2 Posts
    170 Views
    ustkU

    @l4ch standalone doesn’t provide audio inputs. That been said I have made a fork with audio inputs, but I still have some issues when exporting a standalone app on windows (the driver selection freezes the app) but it’s working on mac. If you export a plugin though there should be no issues.

    Another warning is that the audio inputs are directly sent to the output, creating a dangerous feedback if you have a microphone connected and speakers on ! This has to be kept in mind during development

    I’ll try to make this fork available soon when I’m back (not today)

    If you can use the plugin version of Hise, there’s a multichannel projucer project already available

  • Expansion wide preset search

    3
    4 Votes
    3 Posts
    775 Views
    ChazroxC

    @David-Healey Killin it.

  • Building HISE with new JUCE system

    5
    0 Votes
    5 Posts
    360 Views
    David HealeyD

    @l4ch Yeah I try to keep it up to date. I think I'll be updating it again when the setup.hise.dev script is fully tested and has all the features across all platforms.

  • Scriptnode EQ-issue on exported fx-plugin

    Unsolved
    2
    0 Votes
    2 Posts
    688 Views
    VorosMusicV

    Seems like the issue was the high-shelf node.
    The plugin functions fine without, but doesn't seem like a solution for the future to just not use it at all.

  • Regarding expansions

    5
    0 Votes
    5 Posts
    339 Views
    ulrikU

    @David-Healey Thanks!

  • What does this above value means

    5
    0 Votes
    5 Posts
    852 Views
    N

    @dannytaurus thank you so much, dont be sorry lol we are humans and humans make mistakes 😊
    thank you again🤙

  • 10 Votes
    15 Posts
    2k Views
    J

    @Sifres
    The storefront was easy to setup, but
    I have a half finished website. I was just testing it out, but seems to be really great so far.
    ...and I havent tried that JUCE module that can work with License activations.

  • Crash when clicking Parametriq EQ1 in module tree

    6
    0 Votes
    6 Posts
    782 Views
    pcs800P

    @David-Healey I found the issue.
    ParamEQ.setAttribute(band * 5 + 4, bandColors[band]);
    band * 5 + 4 is an invalid attribute index for the CurveEq

  • Absolute Samples - Windows 11

    Unsolved
    5
    0 Votes
    5 Posts
    401 Views
    L

    @David-Healey I had about 16, I just automated the find/replace in VScode and it worked really well. Thank you for the videos on exporting plugins, went back and followed them to the letter and they worked perfectly.

  • JUCE error while exporting VST

    17
    0 Votes
    17 Posts
    2k Views
    J

    @David-Healey said in JUCE error while exporting VST:

    @Jeetender How big is it?

    Content.makeFrontInterface(700, 400);

    const var scriptFx = Synth.getEffect("Script FX1");
    const var buttons = [];
    const var panels = [];

    for (i = 0; i < 5; i++)
    {
    buttons[i] = Content.getComponent("Button" + (i));
    panels[i] = Content.getComponent("Panel" + (i));
    buttons[i].setControlCallback(onButtonControl);
    }

    inline function onButtonControl(component, value)
    {
    if (!value) return;

    local idx = buttons.indexOf(component); local compSwitchValue = idx * 0.25; // Show corresponding panel for (i = 0; i < 5; i++) { panels[i].showControl(i == idx); buttons[i].setValue(i == idx); } scriptFx.setAttribute(0, compSwitchValue);

    }

    //const var scriptFx = Synth.getEffect("Script FX1");
    const var mtbuttons = [];
    const var mtpanels = [];

    for (j = 0; j < 3; j++)
    {
    mtbuttons[j] = Content.getComponent("MtrBut" + (j));
    mtpanels[j] = Content.getComponent("MtrPnl" + (j));
    mtbuttons[j].setControlCallback(onMtrButControl);
    }

    inline function onMtrButControl(component, value)
    {
    if (!value) return;
    local ide = mtbuttons.indexOf(component);
    local compSwitchValue = ide * 0.25;

    for (j = 0; j < 3; j++) { mtpanels[j].showControl(j == ide); mtbuttons[j].setValue(j == ide); }

    }

    const var rm = Engine.getGlobalRoutingManager();
    const var cable = rm.getCable("global_cable");

    const var Knob1 = Content.getComponent("Knob1");

    cable.registerCallback(function(value)
    {
    var dB = Engine.getDecibelsForGainFactor(value);
    dB = Math.max(-60, dB); // Clamp to -60dB
    Knob1.setValue(dB);
    Knob1.changed(); // Update UI
    }, AsyncNotification);

  • Preset browser expansion installer

    2
    5 Votes
    2 Posts
    741 Views
    ChazroxC

    Epic!

  • Mac installer for audio sample libraries best practices?

    32
    0 Votes
    32 Posts
    4k Views
    David HealeyD

    I also emailed the Araelium dev and he said the situation is the same with Package Builder. The limitation is with the Apple installer which all pkg files use.

  • Pro Tools is not recognizing my AAX plugin.

    8
    0 Votes
    8 Posts
    1k Views
    lijas90L

    @svkpowa thanks!

  • how can i create a sin lfo in scriptnode

    3
    0 Votes
    3 Posts
    532 Views
    N

    @ustk thank you so much ill try it
    Thanks again im so happy😄

  • Panel paint routine - different corner radius on same panel?

    13
    0 Votes
    13 Posts
    1k Views
    David HealeyD

    @ustk Nice!

  • Trying to give back in my own small way - KnobForge!

    1
    3 Votes
    1 Posts
    611 Views
    No one has replied
  • Matrix Modulator Smoothing Control

    7
    0 Votes
    7 Posts
    620 Views
    ustkU

    @DanH just set it to zero then you’ll eat as many kinder as you want (pretty sure this sounds weird in German… 😬)

  • Toggle Oversample container in Scriptnode

    3
    0 Votes
    3 Posts
    301 Views
    DanHD

    @ustk Sexy, thanks!!!

  • Handling Latency for Delay-Based Modulation Effects

    2
    0 Votes
    2 Posts
    288 Views
    HISEnbergH

    @Yinxi Good question.

    Just to start, latency refers to a short period of delay (usually measured in Samples in DSP) when an input signal enters the plugin and when it exits the plugin. In many cases that is not desirable so HISE (using the JUCE backend) has a function called Engine.setLatnecySamples. This works by telling the host/DAW: "Hey, this plugin introduces X samples of latency, so adjust the signal so it is X samples further ahead in time".

    An example of this happening in Scriptnode is if you use oversampling, which will generally introduce a few samples of latency. So you need to calculate the amount of latency introduced (Use Tools>Check latency of signal chain) and use Engine.setLatencySamples to adjust it. This function is dynamic, meaning you can adjust the number of samples depending on the latency you are introducing. Example: if you have a knob that adjusts the oversample size from 2x to 4x, this might cause your latency to jump from 1 samples to 2 samples. You can write an if statement to change this and the host will be updated:

    // pseudo-code if (OversampleKnob = 2x) Engine.setLatencySamples(1); else if (OversampleKnob = 4x) Engine.setLatencySamples(2);

    Small note: Each host has a different way of handling the information it receives from a plugin so results may vary here. You need to make sure to update the latency report once when initializing the plugin, and any time after if changes(this is probably updated once per block).

    But returning to your earlier question about vibrato, if you consider that latency is just a delayed signal, that is not necessarily a bad thing. Vibrato is basically just a time-varying delay (delay line modulated by an LFO). The pitch shifting comes from the rate of change of the delay. In other words, the delay(or latency) introduced by the Vibrato is precisely what you want, so there is no reason to adjust for the latency.

    This is all an oversimplification but hopefully clarifies things a bit. You can test this out in a DAW to confirm as well. Run an impulse through your plugin and record the output and see how they line up.

17

Online

3.1k

Users

14.0k

Topics

122.1k

Posts