I've been living and breathing ScriptNode for a month now, day in, day out. I used it here and there over the past few months but it was for small networks and modulators, usually no more than 10 nodes.

It's ridiculously easy to get most DSP prototypes working in Scriptnode. If you add Faust to the mix, it really is a superweapon ready for the future. Global cables as well as external slots make it easy to communicate the data out to the UI.

I'm currently working with massive, interconnected networks with lots of parameters. I think I loaded every node at least once.

For some context: I have a decent amount of experience using Unreal Engine Blueprint and writing complex animation blueprints and state machines in Unreal (putting together designer-friendly AAA-level non-replicated locomotion systems and character blueprints up until UE5.2).

I've been vocal about ScriptNode lately in various threads and have posted numerous bug reports as well. I figured collecting my feedback in this thread will make it easier to discuss.

---

Issues

There's a number of issues lurking, many of which have been only made apparent in my attempts to scale this thing to megacity-levels (200+ nodes and counting).

Unique IDs

The biggest design flaw in ScriptNode is that connections are tied to IDs, which are user-facing and user-editable, and the repercussions of messing with this are not audible until you reload the network (e.g. close and re-open HISE).
I've elaborated on this here. https://forum.hise.audio/topic/9835/scriptnode-prevent-renaming-a-node-id-when-attempting-to-use-one-that-already-exists

The magnitude of this issue is most apparent when trying to copy/paste nodes which have active connections (it's impossible): https://github.com/christophhart/HISE/issues/546

Suggestions:

• unique IDs for nodes in the back, just a name property for the front. Notes spawn with the default name property without the number, like they currently do.
• if a name of the node is changed from the default name, hovering the node name should show the original node name (the factory path property from right click)

Navigation

I haven't found a way to navigate around a network freely other than with a mouse or a touch pad. It becomes problematic when you want to plug a, say, peak node into whatever parameter of another node two screens away. If you don't have an MX Master, which has a vertical and a horizontal scroll wheel, or a similar peripheral, and the network is too big even for zooming out, your only choice is to exit HISE, edit the XML and reload the project.

Suggestions:

• double clicking on an output pin or parameter enters plug mode: you can now freely scroll by clicking on the scroll sliders or using two fingers on a touchpad
• be able to use arrow keys to scroll the screen instead of jump around node selection
• moving the mouse while holding the drag pin to the edge of the screen scrolls the screen, like in a CRPG/Strategy/MOBA game.

Labeling

When working on a big anything, keeping things organised is paramount. Node comments in a vertical layout are fine. But if you switch to a horizontal layout, they now unnecessarily add to the width by staying on the side, when they could be moved to the top or bottom.
https://forum.hise.audio/topic/9816/put-node-comments-above-below-nodes-when-the-container-is-laid-out-horizontally

Also, once the ID issue is sorted out and the name property becomes just a name, right clicking a node should automatically enable the editing of the node property field so you can immediately type a desired name.

Connection Clarity

Once things get bigger than your screen, and as they grow, it becomes ridiculously hard to keep track of connections.
This has been briefly touched on here https://forum.hise.audio/topic/9819/scriptnode-highlight-incoming-cable-on-hover-when-cables-are-hidden but there's still a long way to go.

• If you right click a source (parameter or output pin), a target will be displayed
• If you right click a target, a source will be displayed only if it's a parameter, not if it's a node (e.g. peak)
• After the feature in the link above was added, the source will now be displayed on hover if you hover a target, but still nothing if you right click it
• There's no mention of the source or target's parent nodes
• The names are direct node IDs, which ties in to the ID issue mentioned above, so you're discouraged from changing the node names, in fear of accidentally ending up with two nodes that share the same name/ID
• If you collapse a node, connections to any of its parameters or child nodes disappear both visually and in the right-click connections tab for the source parameter

Suggestions:

• The new feature that shows a source should always be on
• Remove the tooltip when hovering a parameter which just repeats the visible node ID and parameter ID, that just obscures the new source tooltip
• Show full target hierarchy both on hover and on right click menus as outlined here https://forum.hise.audio/post/81634
• Fix missing source connections from node outputs when right clicking parameters
• Show cables running to and from collapsed nodes; show source/target node names in the connection list
• Have a way to click on a node name in the connection list in parameter properties that will move the viewport to that node

---

Wishlist

Here are the things that I find missing at the moment.

Logic operators and Clamping

Basic < > = operators, as well as unscaled input clamping. Discussed here. https://forum.hise.audio/topic/9844/scriptnode-add-to-control-logic_op/6

Variables

Having variables in scriptnode that can be saved or read. Here's an example from Unreal's Blueprint: https://youtu.be/oKGJECvQJA8?t=88

Suggestion:

• variable creation window, maybe like the parameter toolbar; variable needs an identifier and a default value
• get node (dropdown menu that lets you select the variable to get, output pin)
• set node (dropdown menu that lets you select the variable to set, parameter for writing, writes on change)

The get node avoids the need for a cable mess since you can write to a variable with set, and then just load as many get nodes as needed.

Wrapping Nodes into External Files

Just like you can wrap nodes into a chain, and like you can move selected code into an external file, you should be able to move the nodes to an external file, which will then be available in the Project tab in Add Node, automatically replace the moved nodes and connections. Because DspNetworks need defined parameters if you need input, perhaps this moving into external files should only be possible for chain nodes, as you can add Parameters to it.

Cable Outputs for Embedded Project Nodes

If you create a network, it can always be added as a node to any other network from the Project tab of the Add Node window. Any parameters of the main container are also visible here.

It would be great to also have output pins for any (scaled or unscaled) peak node from within the network, with usual text ("Drag to Modulation Target") being replaced with the name of the peak node. This is the equivalent of adding outputs to a function in Unreal Blueprint; whenever you add that function to any blueprint, it has the configured input/output pins. Scriptnode currently has inputs (parameters), but not outputs like this.

Extended Expr Nodes

Math and Cable.expr nodes are great, I just wish they had more inputs for algos that need more than one input but are small enough that they don't warrant a SNEX file, which limits visibility

SNEX Docs

I gather SNEX is the place for any complex algorithms because it supports variables and is blazing fast, but at this point I have no clue how to get a sound out of it; the examples in the docs either don't compile or crash HISE.

Happy Holidays, folks! Here's my gift to you all. Over the past few months I saw a few threads asking about Kontakt's flex envelope so I gave it shot at recreating it in ScriptNode. It lacks individual point modulation as we can't, as of this date, access them inside the network.

• Use this as a script envelope modulator. It is fully polyphonic.
• Load it in after loading the Table Envelope. Use the Table Envelope for Attacks and Releases. I tried recreating these here as well to have it all in one view, but always ran into problems with clicking. If there was a Table Envelope node like all the other envelope nodes that automatically triggers on note-on/off and kills the voice, it would be great.
• Attack Time should be set to whatever your attack time for the Table Envelope is. There's a ramp that acts as a timer, and once the attack finishes, the flex envelope starts doing its thing.
• It acts like a factor, multiplying the output from the Table Envelope. That way the gain perfectly fades into the flex and out to a release.
• Right click drag on lines to make them into curves. If you decay the Flex to 0, the Release won't play.
• Looping the Flex goes from the end -- you're setting the start point of the loop as the percentage of the table's x axis
• If you need longer timings, open the collapsed node, find the ramps, right click on PeriodTiming and set your desired Min/Max
• Default block size is 32 samples. If you need a different size for faster/slower processing (shorter Flex times and wild patterns will likely require bigger resolution and therefore smaller block size), right click on the fix_blockx node and set your desired block size. At this size the overhead is miniscule and 5-10ms smoothing clears out any zipper noises.
• Unless Funky's got an ace up his sleeve and is sitting on the API for this, the table itself isn't dynamically adjustable. You can use the logic that you see, create additional serial rampings, set your min/max for each point, create more tables and you could get to a point where you can adjust the factors from scripting, but it's gonna be seriously messy. Plus to my knowledge (that I absorbed from the Script Envelope documentation), there's no way to edit the curve amounts anyway. In that case it's easier to just do it in SNEX/Faust.

Copy the XML to your project directory into DspNetworks\Networks.
FlexEnvelope.xml

Or copy the base 64 string to your clipboard, create a new DspNetwork, click somewhere to add a new node and you'll have an option to import FlexEnvelope from your clipboard.

ScriptNode1292.3ocyXssbaTCFVqikSaCzRfBWwvnKo.0icgRatJGbRJgoNMSsobYGYux1ZxtqVzpM0lq30nWv.uF7Pz2EdC.cX8ZoM6l3zbX5dQpk9k9O98eP8PlOA30Xe7PAiO6HrXBvac3PVj.SiH7lCmH+WvA6B7tKb+.xz8hNgDvhIfclEiSRH9.uUfs.8lvdyQXNNjHH7D0dsAGJYcGV.KkC7fd.4WGVXHIR.7pAkGQQOA.77NTqCPkP9H3H5zWOHfM73o.Gk5KrTJqyrPMLL7rD3QbohyETsTqksZl7mFIePxqTTGhC.uBGjJUIuZfBmZM3NJ41i96j4GpN76eD.L2XVwxXVE1GOHf3ZGet1N3rflCUDesPejKfYT21L.cY9oAXAkE0GyGSDZGZGVTDYnZS4UTr6.IigPruOHOHo1ZUnwFTBHVFb2EKvp6qU6j7eor8HexTk57exu8BGP78I95i6QfO4QMy+1ni7Om7B4eN7o+T+c+4mjuN8oNzGs8FCh61ZA8eYC26O5asVC.VnKodkuRZDcoQYghaWGj80EOsvd+6l8DjXcfy5b8Nl7FS3w9jlfmgAmh0amJXgXgNVUCXB2MT2Xc3yYioCQ3Hez1AwSvfyIqxME5rC66yB7MhbQhSMKr1GC2VHvCOFoCJNB99VBNj4ewk8BIVuLI9RbXrqDWSJQNoIWQvUP4rcc3yHBTFG5SCIknCd0Wdz88f84oDzuNgDgjA+kCmuKMIN.OamzQixvUN6HWmg6qCeX6BPvUrffMV.AgvVMaYA+tE7wsZo1ZA569xiztk4q8OrQq1s+w1N.QEOdLvTT5HBmx70NHKfmp7JvRApWsB.gskqM0tdNiE2Sf4BfCwKLmZ.elTOJxD6xRV3jhQlRvlKpFRlFyqBxLAp4gXBAYg7PinQISHIHEZiFM96PTAZL8D4NpSNl8P7DB1GIX50pdXl6I2HQ4KP9L40j2RcA4uZVFR7r6cz.1QYuY9iOC1UZaMGEvX7ulFEmJd.nXejUg6RFjNd9UT1YokxqUJX+VPYRbzXRkn7RK+GlFTwEpr15RgFlylh3SKLPtB6D7+jEAeC0JB7+Fbu.ZHMRxaDmDSDTgL9hNQIUj4pInDS7kSRHBotiXQAyPJuHRvoiGS3De4dYGGIiKpncBZHNgXsuDTz9Aki.V9ZQ2ANWKtQ82Uk.ZoNNt+OM28mSuh.vWAeIIyKVHIZ.YH9R5sVClyNW2UVUlaBuksHbnHk2RMlnyHrZ6ojI.tBaDaOlosCbIaCediXdy2m71PcKwO3ZTdY4UFH9LQekjqXCnLUtchr2AFpZwn1uhT1sjMgNlfRR4DUCQYmtYIHrPm9NfLlFEoZ5kFInA1cTkMSoptokVBr1MacqFvXB93RgzZBUX4eIrCNVnra0ozSiK33njPpn4kbHy4On65d3xq3hSWQU2ZX5j+hTgbjlk+sMm2CZseYy6qxU70Pl25VVJiZ+KvisqUYj3Ct2fl0qOIjwjIzE50eOSdSNwqFWPsKrKXq+ZqBtf+9su8e17Tt.z69y2so40C8z5rrZkt1tE69iF.v2rkqq35OlbW4j6ivoAhkHzrRgTupV3U2tIoyiq6efznuNdd4hxysZ4Tuq5xetu32oHnS+WPQqIaBEMwqkQ.x3PCs2XIslJm6rRaotoJjZ3.jY5fyqs2ovZWRUydxjR7x4oJfq9jw7+2NaurNXqZQNFQwT52qVR+OTfNZfA

Enjoy!

@griffinboy Well it happens, I always look through the forum, the docs, the github docs (way better search than on the docs page) and google with the site: hise forum target, but even then sometimes I'll ask something and David or someone else will pop by and drop a link to the docs.

If every post you made was asking about something that can be easily found in the docs, then I'm sure eventually someone would make a comment about that.

But generally, you're fine. I understand it can be an anxiety thing, I have close people who have dealt with similar stuff all their life, and while it can never go away, it does get easier when you remind yourself of the reasonable take on the whole thing. Which, granted, someone often has to give you first, so in case that's what's up, here's mine.

If you, for just a moment, disregard the whole gift-to-humanity FOSS side of the entire project and look at it from the business side, your posts are good data. You yourself are just one data point, but if everyone else started asking repetitive questions, that could indicate a documentation or some other problem.

You can see this, for example, in the introduction of the export pre-flight checklist that happened a few weeks ago. If you go through the forum, at one point a couple of months ago you'll see a lot of similar posts started appearing on a nearly daily basis: compilation fails, export fails, and most of them caused by the users not actually reading the very first readme right on the github page.

Someone made a video about plugin creation with HISE on youtube, it got some traffic and HISE got an influx of new users. A lot of them just went to the hise.dev webpage, downloaded the binary and attempted to VCR through the whole thing by putting together something in the WYSIWYG editor and clicking export. When it didn't work, the first thing they did was come to the forum.

This gives you a lot of clues about how curious hobbyists think and work, and if your business decision is that there's still potential future developers there (or you're just annoyed with the daily export error posts), you now have data to work off of and make changes.

It's a good deal. Chris provides a place to talk, in return he gets QA and customer support.

You're asking good questions. The talk we had about the dynamic continuous event modulation yesterday was a good talk. These are new features in HISE, and it's good to test the general audience's understanding of these by bringing it up, which, as you saw in my snippet, requires a decent understanding of HISE in order to implement properly. People will surely benefit from it. If even one person does, it's worth it. I am where I am in life because of selfless contributions of countless people of many forums and those who created, maintained and moderated them, allowing me to search, browse and read days, months or years after these talks took place and benefit from the information.

Even this topic, silly as it may seem in hindsight, is framed very well and is a very SEO friendly question. A few weeks from now, whether someone attempts to search it here, search it on google, or it gets swallowed by some LLM and someone asks there, i'll easily be the thing that comes up first.

So your questions are good. You're not being a jerk, you're not forcing political themes or sexualizing other forum members. You're talking about HISE and instrument development practices and workflows. It's all on topic, and you're even actively contributing, like with the C++ tutorial. So all's good. Keep talking, that's what the forum is for.

Could we please get the rest of the math notes in ScriptNode as well? Cos, tan, acos, asin, atan, min, max, log etc.?

Before you say "use the expr node", it unfortunately does not support multiple inputs (you already addressed this as not happening), and keeping the expressions tucked each in its own SNEX or Faust node is a mess to keep a track of and debug.

Related topic: https://forum.hise.audio/topic/10630/scriptnode-synths-external-data-polyphonic-modulation

Per-Event Modulation From UI with Global Storage.md.zip

Alright something definitely feels fishy here.

The parametric EQ low pass at q=1 behaves exactly like the Pro-Q3 lowpass at 12dB/oct.It's a biquad filter.

I now built HISE with HISE_USE_SVF_FOR_CURVE_EQ=1 and the default lowpass at q=1 now looks like the one from Faust I posted a gif of above.

The svf_eq node in Scriptnode also looks correct

But the standard svf node is fucked just like the Filter module

SVF node allpass looks correct at first

But will straight up attempt to murder you as you move it up
https://github.com/christophhart/HISE/issues/527

You can see the filter stop working after I drive the frequency high enough. The math seems to be wrong and it falls off the edge of the cliff, taking everything with it as it zooms past 20k while the Frequency parameter is nowhere near.

Conclusions:

• SVF in the Filters module and the SVF node are busted
• stay away from the default Allpass like the plague. If you need Allpass right now, get Faust, RNBO or write it yourself in SNEX/C++
• use the SVF_EQ node
• build HISE with HISE_USE_SVF_FOR_CURVE_EQ=1 and enjoy the SVF EQ, just keep in mind that the LP and HP will be more resonant by default, so use Q=0.7071

Bonus for the end: biquad node HP thinks it's an SVF

@d-healey 100L to 100R. C in the middle.

Let us use look and feel on the title bar.

This will further push the unified look across the platforms.

In JUCE, it's just this, for example:

MainWindow (juce::String name)
           : DocumentWindow (name,
                             juce::Colour(0xff222222),
                             DocumentWindow::closeButton | DocumentWindow::minimiseButton)
       {
           setUsingNativeTitleBar (false);

This will only show the minimize and close buttons, and disable the native title bar.

Then for look and feel it's this (probably messy as hell given how this is from my first JUCE project but you get the gist, I'm sure).

class CustomLookAndFeel : public juce::LookAndFeel_V4
{
public:

    void drawDocumentWindowTitleBar(juce::DocumentWindow& window,
        juce::Graphics& g,
        int w, int h,
        int titleSpaceX, int titleSpaceW,
        const juce::Image* icon,
        bool drawTitleTextOnLeft) override
    {
        // Fill the title bar background
        g.fillAll(juce::Colour(0xff222222));

        // Create a Typeface from the binary data
        juce::Typeface::Ptr typeface = juce::Typeface::createSystemTypefaceFor(GlobalFontData::Controls, GlobalFontData::ControlsSize);

        // Create a Font from the Typeface
        juce::Font font(typeface);

        // Use the font
        g.setFont(font.withPointHeight(18.0f));

        g.setColour(juce::Colours::white); // Choose an appropriate text color

        // Retrieve the title of the window
        juce::String title = window.getName();

        // Set the area where the title will be drawn
        juce::Rectangle<int> textArea(0, 0, window.getWidth(), h);

        // Draw the title text
        g.drawText(title, textArea, juce::Justification::centred, true);

        // Temporarily draw the text area for debugging
        //g.setColour(juce::Colours::red);
        //g.drawRect(textArea); 
    }

    // Style the close button here, then create a new instance of it in the createDocumentWindowButton() method
    class CustomCloseButton : public juce::Button, private juce::Timer
    {
    public:
        CustomCloseButton(const juce::String& buttonName) : Button(buttonName)
        {
            startTimerHz(60); // Start the timer to update the color 60 times per second
        }

        void paintButton(juce::Graphics& g, bool shouldDrawButtonAsHighlighted, bool shouldDrawButtonAsDown) override
        {
            g.setColour(currentBackground);
            g.fillRect(0, 0, 40, 40); // Draw the background square
            g.setColour(currentColour);
            g.setFont(juce::Font("Arial", "Regular", 22.0f));
            g.drawText("X", getLocalBounds(), juce::Justification::centred, true);
        }

        void timerCallback() override
        {
            // Update the color
            currentColour = currentColour.interpolatedWith(targetColour, 0.2f);
            currentBackground = currentBackground.interpolatedWith(targetBackground, 0.2f);
            repaint();
        }

        void mouseEnter(const juce::MouseEvent&) override
        {
            targetColour = juce::Colour(0xffd2d2d2); // Highlighted color
            targetBackground = juce::Colour(0x10ffffff); // Highlighted color
        }

        void mouseExit(const juce::MouseEvent&) override
        {
            targetColour = juce::Colour(0xffbababa); // Mouse off color
            targetBackground = juce::Colour(0x0000000); // Mouse off color
        }

        void mouseDown(const juce::MouseEvent& event) override
        {
            targetColour = juce::Colour(0xffe9e9e9); // Down color
            targetBackground = juce::Colour(0x20ffffff); // Down color
            Button::mouseDown(event); // Pass the event to the parent class
        }

        void mouseUp(const juce::MouseEvent& event) override
        {
            targetColour = juce::Colour(0xffd2d2d2); // Highlighted color
            targetBackground = juce::Colour(0x10ffffff); // Highlighted color
            Button::mouseUp(event); // Pass the event to the parent class
        }

    private:
        juce::Colour currentColour = juce::Colour(0xffbababa); // Initial color
        juce::Colour targetColour = juce::Colour(0xffbababa); // Initial target color
        juce::Colour currentBackground = juce::Colour(0x00000000); // Initial background color
        juce::Colour targetBackground = juce::Colour(0x00000000); // Initial target background color
    };


    // Style the minimize button here, then create a new instance of it in the createDocumentWindowButton() method
    class CustomMinimizeButton : public juce::Button, private juce::Timer
    {
    public:
        CustomMinimizeButton(const juce::String& buttonName) : Button(buttonName)
        {
            startTimerHz(60); // Start the timer to update the color 60 times per second
        }

        void paintButton(juce::Graphics& g, bool shouldDrawButtonAsHighlighted, bool shouldDrawButtonAsDown) override
        {
            g.setColour(currentBackground);
            g.fillRect(0, 0, 40, 40); // Draw the background square
            g.setColour(currentColour);
            g.setFont(juce::Font("Arial", "Regular", 22.0f));
            g.drawText("/", getLocalBounds(), juce::Justification::centred, true);
        }

        void timerCallback() override
        {
            // Update the color
            currentColour = currentColour.interpolatedWith(targetColour, 0.2f);
            currentBackground = currentBackground.interpolatedWith(targetBackground, 0.2f);
            repaint();
        }

        void mouseEnter(const juce::MouseEvent&) override
        {
            targetColour = juce::Colour(0xffd2d2d2); // Highlighted color
            targetBackground = juce::Colour(0x10ffffff); // Highlighted color
        }

        void mouseExit(const juce::MouseEvent&) override
        {
            targetColour = juce::Colour(0xffbababa); // Mouse off color
            targetBackground = juce::Colour(0x0000000); // Mouse off color
        }

        void mouseDown(const juce::MouseEvent& event) override
        {
            targetColour = juce::Colour(0xffe9e9e9); // Down color
            targetBackground = juce::Colour(0x20ffffff); // Down color
            Button::mouseDown(event); // Pass the event to the parent class
        }

        void mouseUp(const juce::MouseEvent& event) override
        {
            targetColour = juce::Colour(0xffd2d2d2); // Highlighted color
            targetBackground = juce::Colour(0x10ffffff); // Highlighted color
            Button::mouseUp(event); // Pass the event to the parent class
        }

    private:
        juce::Colour currentColour = juce::Colour(0xffbababa); // Initial color
        juce::Colour targetColour = juce::Colour(0xffbababa); // Initial target color
        juce::Colour currentBackground = juce::Colour(0x00000000); // Initial background color
        juce::Colour targetBackground = juce::Colour(0x00000000); // Initial target background color
    };


    juce::Button* createDocumentWindowButton(int buttonType) override
    {
        // Here you can create your custom buttons. You can check the buttonType to determine which button to create.

        if (buttonType == juce::DocumentWindow::minimiseButton)
        {
            return new CustomMinimizeButton("minimize");
        }
        else if (buttonType == juce::DocumentWindow::maximiseButton)
        {
            // Create your custom maximize button
        }
        else if (buttonType == juce::DocumentWindow::closeButton)
        {
            return new CustomCloseButton("close");
        }

        // Call the base class implementation if you want to keep the default look and feel
        return LookAndFeel_V4::createDocumentWindowButton(buttonType);
    }

};

In HISE, it would be drawTitleBar, register a function to a LAF object and then call something like Content.setTitleBarLookAndFeel (LAF). How would previewing it go, though? Probably a floating tile?

inline function sortByProperty(arr, prop)
{
    arr.sort(function[prop](a, b) 
    {
        if (a[prop] < b[prop]) 
            return -1;
        if (a[prop] > b[prop]) 
            return 1;
        return 0;
    });
    return arr;
}

var array = [
    {"name": "John", "age": 25},
    {"name": "Jane", "age": 22},
    {"name": "Joe", "age": 30},
    {"name": "Jack", "age": 3},
];

Console.print(trace(sortByProperty(array, "age")));

Inspired by the snippet waiting room post, I want to start a similar initiative for the docs. I think a lot of people would have something to say about various methods in the API but the process of both updating the doc files and creating a pull request is a bit convoluted.

At least that's my theory, and I'd like to put it to test here.

The idea is simple: we tackle one API category at a time. Every day, everyone makes an effort to write an example about one method in the category. Post what you know. Post about the kinks you found.

Once it's filled or once a week, @Christoph-Hart can go over it, pick the ones that seem to fit the bill best and update the docs. Snippets welcome, of course. Maybe these snippets can then be arranged into API topic-specific snippets that collect everything, but I'll leave that idea for later; right now let's just do code examples for the API.

If this persists, we should be able to cover the entire API by year's end.

Some formatting ideas:

Second level markdown heading for method names: ## Class.method()
Three underscores in the next line: ___
Single backticks for referring to methods or code bits in the description: `

If you decide to write an entry, it could be a good idea to create an empty post

Class.method()

---

so multiple people don't end up working on the same method. Once you're done, edit it and fill it out.

@d-healey is it just about avoiding one function call in on note or do you have a bunch of logic in on note for it as well?

@Morphoice in your synth's script processor, in the note off callback, just use Message.ignoreEvent(true)

@FPSzky use faust

Theres this https://github.com/azur1s/elysiera/blob/main/

And this https://github.com/thedrgreenthumb/faust/blob/master/shimmer.dsp

@Mighty23 it's probably your array of delay times due to how they're fed into the matrix. Try shuffling them around in the list.

@Christoph-Hart

More on this:

https://learn.microsoft.com/en-us/visualstudio/install/visual-studio-on-arm-devices?view=vs-2022

don't forget you can just feed the transcript into chatgpt and ask about it, though the accuracy will depend on the transcript accuracy which can suffer when acronyms are used or the speakers' english is not very good. If you feed in the transcript with timestamps, you can just ask for a timestamp for specific claims and check it out.

Here’s a summary of Matt Gonzalez’s talk on JUCE Graphics: Past, Present, and Future:

Introduction

• Background: Matt Gonzalez is a veteran audio developer with over 20 years of experience, known for contributions to JUCE 8's Direct2D graphics.
• Focus: This talk discusses the evolution, technical details, and future direction of JUCE's graphics system, particularly in moving from CPU to GPU rendering.

---

The State of JUCE Graphics

• JUCE Strengths:
  • Cross-platform compatibility.
  • Excellent for audio processing.
• Historical Weakness:
  • Graphics performance has been a longstanding pain point for JUCE users.
  • Historically reliant on a CPU-based software renderer, which limits rendering speed and capability.

---

Transition to GPU Rendering

• Direct2D Implementation:
  • Matt reworked JUCE’s Direct2D renderer during the pandemic, enabling GPU-based rendering for JUCE applications on Windows.
  • Direct2D bypasses the CPU for rasterization tasks, utilizing the GPU for significant performance improvements.
  • Demonstrations showed up to a 10x speedup in certain scenarios (e.g., tiling and transforming images).

---

Challenges in Transition

1. GPU-Specific Issues:
   • GPUs are optimized for 3D rendering, so 2D tasks like stroking paths, text rendering, and clipping present challenges.
2. Legacy Compatibility:
   • Ensuring compatibility with existing JUCE components and the software renderer required addressing legacy constraints.
   • Examples:
     • Maintaining support for nested renderers (Direct2D, OpenGL, GDI).
     • Adapting the JUCE image class for GPU-based storage.
3. Conceptual Shifts:
   • Moving graphics tasks to the GPU necessitates new mental models, as GPU rendering involves massively parallel processing.
4. Design Trade-Offs:
   • Balancing ease of use for developers with cutting-edge performance required difficult decisions.

---

Advancing JUCE Graphics

• New Features via GPU Rendering:

  • Mesh Gradients: Advanced gradients with flexible control over color transitions and shapes.
  • Real-Time Effects: Blur, embossing, and shadowing effects executed directly on the GPU.
  • Dynamic Rendering: Procedurally generated UI elements like buttons, eliminating the need for pre-rendered assets.

• Future Goals:

  • Replace the low-level graphics context (LLGC) entirely with GPU-based solutions.
  • Build a cross-platform GPU renderer that works with Vulkan, Metal, and DirectX 12 for all platforms.
  • Shift all rendering logic to shaders for maximum performance and flexibility.

---

Prototype Metal Renderer

• Matt demonstrated a Metal-based renderer for macOS, achieving 4-5x speedups over Core Graphics.
• Key Advantages:
  • Seamlessly integrates with existing JUCE graphics APIs.
  • Opens possibilities for developers to leverage GPU shaders for custom effects and advanced visuals.

---

Community Contributions

• MCAL Module: A new library developed by Matt, providing additional Direct2D features not included in JUCE 8, such as advanced gradients and image processing effects.
• Call to Action: Developers are encouraged to experiment with these tools and provide feedback to shape future development.

---

Closing Thoughts

• JUCE’s transition to GPU rendering marks a significant leap forward, enabling richer, faster, and more visually dynamic UIs.
• Challenges remain in balancing legacy compatibility with innovation, but progress in tools like Direct2D and Metal sets the stage for a modern, cross-platform graphics pipeline.

Resources & Contact

• Recommended resources: Metal by Example and JUCE forums for further exploration.
• Matt encourages discussions and questions through Discord for developers eager to delve deeper.

This talk underscores JUCE’s journey from outdated rendering to modern GPU-based solutions, highlighting exciting new possibilities for developers.

@d-healey another win for the globals!

@Morphoice It does sound the same. Your trackpad sends an instant note on and note off. I can confirm this on trackpads where you tap for click. On macbook's trackpad where you have a haptic press for click, it works fine i.e. like a mouse click.

That's somehow tripping up the internal keyboard. Not even changing the hold time in the envelope improves it.

You can delay your note off for development purposes, just don't forget to remove it once you're not on the laptop with the trackpad.

Message.delayEvent(Engine.getSamplesForMilliSeconds(150));

If you're switching between machines, you can make it so that this delay only happens in HISE and for your laptop only (by using machine id) just in case you forget to comment it out

@VirtualVirgin define an inline function with a g argument, write it and then just pass the function into the setPaintRoutine method call for any panel you want to use it for.

@VirtualVirgin no, just use .setPaintRoutine

The methods are all the same but you don't get an obj, instead you can refer to the panel with this