administrators group

Christoph Hart

@HISEnberg yup that should fix it - it fixes the webview tutorial on my system, but it's just a hack - I had to delay the webview initialisation in FL. Let me know if it persists in your project.

Christoph Hart

KVR is the 4chan of music forums, don‘t bother…

Christoph Hart

It depends whether you want it to be a static connection or a dynamic modulation routing.

If static, then a control.pma node would be the best candidate - connect the UI knob to the value and the envelope output (either from an extra_mod or an inbuilt scriptnode AHDSR) to the add output, this will combine the two with unipolar modulation mode.

Scales and offsets a normalised modulation signal using a multiply-add formula with clamped output.
The PMA node (Parameter Multiply Add) scales and offsets a normalised modulation signal. It takes a 0-1 input value, multiplies it by a configurable factor, adds a constant offset, and clamps the result to the 0-1 range. This is one of the most commonly used control nodes for adjusting modulation depth, inverting signals, or combining parameters.

Each parameter change triggers an independent output update. If Value, Multiply, and Add all change in sequence, three separate output values are sent to connected targets.

Christoph Hart

I'm not sure whether MIDI tempo information messages makes it through to the Faust node, but the tempo sync node is definitely the way to go. just build your Faust node with a absolute delay time parameter and then connect it to the tempo sync node - it automatically sends the correct time value matching the tempo and reacts to tempo changes etc.

upcoming docs:

Tempo Sync (control.tempo_sync)

Converts a musical tempo value to a duration in milliseconds and sends it as a modulation signal.
Tempo Sync converts a musical time value (such as 1/4 note or 1/8 triplet) to a duration in milliseconds based on the current DAW tempo. The output updates whenever the host tempo changes or any parameter is adjusted, making it suitable for driving time-based effects that need to lock to the beat.

The output is an unnormalised modulation signal carrying the raw millisecond value. If the target parameter expects a different unit (such as frequency in Hz), place a control.converter between this node and the target. When Enabled is set to Off, the node outputs the manual UnsyncedTime value instead, allowing a smooth fallback for standalone operation or manual control.

CPU: negligible, polyphonic.

Signal Path

Pseudo-code - hover highlighted terms for details


// control.tempo_sync - musical time to milliseconds
// BPM + parameters -> ms out (unnormalised)

onParameterChange() {
    if Enabled:
        output = tempoToMs(bpm, Tempo) * Multiplier
    else:
        output = UnsyncedTime
}

onTempoChange(newBpm) {
    bpm = newBpm
    if Enabled:
        output = tempoToMs(bpm, Tempo) * Multiplier
}

Christoph Hart

@HISEnberg this. The structure of the shape FX module is somewhat limited and you can easily create whatever wave shaper + signal flow you want in scriptnode and if you compile it down to C++ it's about as efficient as the inbuilt wave shaper.

Christoph Hart

@David-Healey it counts the number of quotation marks in the text before. if even => add two. there must be some quote char messing up this logic in your code.

Christoph Hart

@nohasm191 haha yes we all do human things as humans. Because we are human and not a robot.

Christoph Hart

@Oli-Ullmann what are you trying to achieve? Not sure if a webview is the solution.

Christoph Hart

I could reproduce the crash - unfortunately I couldn't solve it properly, so the only fix is to delay the initialization for Webviews on FL Studio if the plugin is opened. If I "double click" on the instrument track, it crashes in the FL code, not the destructor of the webview (which I hoped it would).

I'll push the fix tomorrow.

Christoph Hart

@ustk on macOS JUCE6 is already using the native CoreGraphics API which then uses whatever is fastest. Plus you can attach OpenGL, then it will use this for rendering primitives.

You can already switch to JUCE8 and try it the performance gets better. Ask Claude to reenable Direct2D then as I had to disable it to remain consistent with the UI performance of JUCE6 - I discovered some things to get much faster, but some things to get much much more slower, so I decided to disable it by default in the custom JUCE8 branch as this introduces too much of a moving target.

administrators

Posts

Tempo Sync (control.tempo_sync)

Member List