@pcs800 Never mind, I got it working.
I forgot to connect the modulation target
Thanks for the help.

@pcs800 Looks like I may have found my own answer.
File.writeAudioFile(var audioData, double sampleRate, int bitDepth)

@pcs800 Awesome! 🙌

I'm using Activity Watch to track time on an app.
ActivityWatch - Open-source time tracker https://share.google/Edb7SuzvFWQrHf5ZR

Maybe you can borrow some code

@David-Healey Ok, I will keep that in mind

@pcs800 I found two related threads that might help

https://forum.hise.audio/topic/7976/wrap-midi-node-in-compileable-dsp-network
https://forum.hise.audio/topic/4364/snex_node-needs-to-be-wrapped-into-a-compileable-dsp-network

@Christoph-Hart I updated to the latest dev build and the crashing no longer happens

@pcs800 well 95 samples would make hardly any difference at all... whats the measured latency of your plugin?

oh hang on youve already said:

95.9ms, that's great. But how do I get the plugin to report that to the daw?

Go read what @ustk said above.....

@pcs800 said in Text input:

Yes, but you cannot hit enter to move down a line.

f431de1d-b0a3-4a75-8085-8a8271617a26-image.png

@Lindon Makes sense 😀

@resonant Not on happening on my end but, perhaps just interfacing a control.smoothed_parameter can help.

@pcs800 Ah ya it is a little hidden. In scriptnode click the arrows icon next to the parameter (on your compressor). Then right click the parameter and select "Copy range to source" and it will set the Macro control to the same values.

example.png

example2.png

@pcs800 all good then, have fun...

@Lindon I swear I tried that before and it didn't work, but of course now it does :-/
Thanks!

@Lindon Well that was easy. I can't believe I overlooked that. I had copied the code from another project I did a while back. Thanks for pointing it out.;

@pcs800 can you screenshot your property editor for your analyzer?

@pcs800 the pitch shifter node is broken, you can roll your own using Rubberand (or signalsmith or any other license-compatible library)

https://forum.hise.audio/topic/13256/tutorial-real-time-pitch-shifting-with-rubberband?_=1760500331839

FFT-based pitch shifters will always introduce some latency, it's unavoidable

@pcs800 You can right-click any parameter in Scriptnode and change it's settings including the min-max values. There's also a bunch of control-nodes (checkout the control.minmax node) which allows you to map parameters that have different values.

@pcs800 Looks like it is integrated into the HISE source code (included with the JUCE modules), but you would need to add you own API for this to communicate in HISE script, or edit the HISE source code to contain a version of the script you provided:

https://github.com/christophhart/HISE/blob/01b810a9d31f032b30537b4767082732cd96f46e/JUCE/modules/juce_audio_processors/utilities/juce_PluginHostType.h#L38

https://github.com/christophhart/HISE/blob/01b810a9d31f032b30537b4767082732cd96f46e/JUCE/modules/juce_audio_processors/utilities/juce_PluginHostType.cpp#L4