Just realised I wrote "Sinppet" 😆
Will just keep that one so much it fits the issue 😆

@Chazrox thanks - yeah I will give a hand-coded version a spin...

Thanks guys much appreciated

@David-Healey Of course! Silly me.....

@David-Healey yeah that seems more comprehensive, its more or less doing under the hood what Im doing in HISEScript... so both approaches have the advantage of getting a result back for the plugin itself (no matter how the user has set up to run it..)

Thanks for looking and confirming what I'd found.

@dannytaurus It working soo fine, I had to put engine.loadaudiofilesintopool earlier

@Orvillain ill give that a try thanks. I don't have claude code though. I cant afford paid services at the moment

@David-Healey It was already default to 500 mb in 4.1

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 }

@HISEnberg @Christoph-Hart I hit a problem with controlling a ScriptNode macro with a UI knob AND an envelope.

New post here: https://forum.hise.audio/topic/14793/control-scriptnode-from-ui-knob-and-envelope

@David-Healey cool cool
I did make just a licensing system with traditional serial keys...so Ill probably just use that for now, and then update.
and I finally actually fininshed making this instrument😁

now just working on some vids and demos and final testing. but ill include some screenshots here.
Its just a sample based synth, where i sampled the f-k out of a LYRA 8 synthesizer..
recorded through some amps and speaker cab impulse responses etc.
Screenshot 2026-05-29 at 2.41.06 PM.png Screenshot 2026-05-29 at 2.41.18 PM.png

@Lurch Not sure if it affects compiling networks

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

@David-Healey I guess you're right. I haven't tested any automation through that method yet. Only midi messages.

@David-Healey

Thank you so much

@dannytaurus Thanks for sharing this! If anyone has questions about the data going into this, or suggestions for the next survey, please let us know! :)

@dannytaurus said in Meta Ads:

Or get someone much younger and more in-touch with social media to make them for me!

Don't know if you know about this, but here is a creator/influencer marketplace built into ad manager where you can hire people to make ads for you. If you hire someone, get them to make 10 3 second intros for each ad. Then you can mix and match the intros with the ads so you get more chances to catch a viewer's attention (Ben Heath's idea).

8dd61f3b-86ad-4008-847a-eae77c41d288-image.png