@d-healey
Okay, I'll try that too. Thanks. :-)

@jeffd
ok that was my problem.
i needed to set the array for the channelIndexes

@HISEnberg I am abit lost but let me do more research and see if I can implement this

@udalilprofile
I tried to do it in FAUST, then the value in the UI must be made with a global_cable and draw its value in a panel.

import("stdfaust.lib"); //============================================================================== // CORRELATION METER // // A stereo phase correlation meter that outputs a value between -1 and +1 // indicating the phase relationship between left and right channels. // // +1 = fully correlated (mono) // 0 = fully decorrelated (wide stereo) // -1 = fully anti-correlated (out of phase) //============================================================================== // Integration time constant (in seconds) - typical range 10-100ms integration_time = hslider("Integration Time", 0.05, 0.01, 0.2, 0.001); // Small constant to prevent division by zero epsilon = 1e-10; // FAUST has a function for this but I'm lost and would like to close the implementation -.-' // Low-pass filter cutoff frequency based on integration time lpf_freq = 1.0 / (2.0 * ma.PI * integration_time); // Basic correlation meter implementation correlation_meter = _ , _ : correlation_calc with { correlation_calc(l, r) = lr_filtered / (sqrt(l2_filtered * r2_filtered) + epsilon) with { // Cross-correlation term (L * R) lr_filtered = (l * r) : fi.lowpass(1, lpf_freq); // Auto-correlation terms (L² and R²) l2_filtered = (l * l) : fi.lowpass(1, lpf_freq); r2_filtered = (r * r) : fi.lowpass(1, lpf_freq); }; }; // Alternative implementation using sum/difference method correlation_meter_alt = _ , _ : correlation_calc_alt with { correlation_calc_alt(l, r) = (sum_power - diff_power) / (sum_power + diff_power + epsilon) with { sum_sig = (l + r) * 0.5; diff_sig = (l - r) * 0.5; sum_power = (sum_sig * sum_sig) : fi.lowpass(1, lpf_freq); diff_power = (diff_sig * diff_sig) : fi.lowpass(1, lpf_freq); }; }; // Algorithm selector algorithm = nentry("Algorithm", 0, 0, 1, 1); // Main correlation calculation with algorithm selection correlation_calc = _ , _ <: (correlation_meter, correlation_meter_alt) : select2(algorithm); // Correlation meter with UI elements - following the vumeter pattern cmeter(l, r) = attach(l, correlation_calc(l, r) : hbargraph("Correlation", -1, 1)), r; // Process function - stereo input, stereo passthrough with correlation display process = cmeter;

Two different correlation calculation:

Direct method using L*R / sqrt(L² * R²) Sum/difference method using (S² - D²) / (S² + D²)

Adjustable parameters:

Integration time (10ms to 200ms) Algorithm selection

Real-time display:

Horizontal bargraph showing correlation value

As for the implementation in HISE (UI) you need to connect the hbargraph in a
global_cable scriptnode and draw the "bar" in a panel - this is more complicated for me 😧

Since I'm still a newbie, it would be a good idea to properly test the implementation before putting it "into production"

@Christoph-Hart
6252a86c-bf97-41c8-9aa1-39fc9d0979fb-image.png

Oh, rightly so, the frequency was too high. It works now—thanks.

@d-healey Oh yeah sorry… but since it’s not that important for instruments anyway

@ustk yep, it's a pain

@Brian said in Lottie animation controlling parameters?:

I am currently experimenting with controlling Lottie animations using sliders, but once I set up the knob to control a parameter I lose the connection with the Lottie animation. I am sure there is a way to have all three of these elements linked but it's beyond my current coding skills.

Here is a test project ( latest Scriptnode build and rLottie DLL needed):
Got it — thanks for explaining what’s happening. From what you describe, it sounds like you’ve successfully set up a slider/knob to control a parameter, but in the process the link to the Lottie animation playback got overridden (likely because only one connection is being made at a time instead of merging them).

What you probably need is a single control signal that both the Lottie animation and your knob/slider can “see.” In Scriptnode (and similar node-based systems), this usually means:

Don’t directly replace the Lottie’s input with the knob.

Instead, use a merge/multiply/mix node (or equivalent) to combine the knob value with the animation’s internal time parameter.

Feed that merged output into the Lottie node, so the animation continues to play but is also scaled/offset by your slider.

Another approach:

Use the knob to control animation progress directly (frame / totalFrames), bypassing “playback.” That way the knob defines where in the animation you are, and you don’t depend on Lottie’s internal clock.

If you want both free playback and manual knob scrubbing, you’ll need logic that chooses between “auto-time” and “knob-time” (for example, a switch or crossfade).

If you share your node setup (or a screenshot), I can suggest the exact node combination to keep all three elements linked.

@DanH It's super secret🤫- It is similar to Serum's

@DanH yes I might have to think about a solution how to address individual subcomponents - maybe I can use the CSS selectors as they are already assigned to most components regardless of whether CSS is used, eg:

const var ft = Content.getComponent("Matrix"); ft.setChildTooltips({ ".search": "A search bar that can be used to filter modulation connections", "#intensity": "Changes the intensity of the modulation connection", ".plotter": "Displays a histogram of the modulation signal for this connection" });

@Christoph-Hart
Great to hear that! 😊

Thanks guys, that's helped a lot!

@Chazrox I reckon nothing aside setvaluepopupdata.

@DanH also the loop mode is really cool, but what is the use case for 'Trigger'?

And what's a nice way to sync the envelope to bpm?

Facebook marketing, Tik/Tok / Reels (free), uploading plugins to partners that will promote for you (Splice, MuseHub) etc, forums, sharing with producers and YouTubers who make 'best of XYZ plugins' lists etc

@ustk The generosity of the man.

@DanH Hahaha, it's so simple, thank you very much for your guidance😙

@pcs800 I'm not sure, effects are not my strong area