@Orvillain ditch the smoothed parameter, you don't need that with the fix_delay node, then it should work (the smoothing is already embedded into the node itself).

@Orvillain

Yep that'll be it.

I actually wish it worked differently, but currently scriptnode c++ synth nodes only call process() per active voice. So if there are no voices it won't call process (or subsequently process frame).

Additionally say there are 3 voices playing, that will mean your process script gets called 3 times as frequently... Each voice will run it's own process.

You can check which voice the process() is currently running for, using polydata, which allows you to do different processing per voice

I ended up piping data through a global cable and plotting it to a scriptPanel - it is pretty good actually!!!

But I would like to know how to utilise the display buffers directly on the node.

@Christoph-Hart

🤣

Cool thanks! I'm still figuring out how all of this interfaces, but getting there and making good progress!

@Orvillain Right no... I get it. Use two cables. Dohhh.

@Orvillain

To avoid aliasing you need to be able to control which harmonics are present in the signal either using FFT or a Filter. You'll need to be able to do upsampling in good quality which is why filter design is important I'm not talking about biquads, rather FIR filters. If you can process a signal with FFT in C++ and back again, and you can use FIR filters to do oversampling then you should be able to do a WT engine.

Here is a good resource

@Orvillain

Oh yeah yeah, I found faults with the provided script too. I had to do some casting. I think that's correct.

@Christoph-Hart Lovely stuff!! Thanks for letting me know!

I'm working in HISE right now. Let me pull the latest develop branch and see how I get on. Will report back.

EDIT: Yep. All good here!!

@d-healey Doh. No, I totally forgot. It is fine now.

smacks wrist

@Orvillain said in Accessing midi processor name from within connected script:

I'm fairly confident this will enable me to have my generic script,

That's how I do it

@d-healey Oh! Nice one Dave! I hadn't spotted that thread, doh!

@d-healey said in How do I load a midi script programmatically?:

@Lindon said in How do I load a midi script programmatically?:

{PROJECTS}\mysub\yoursub\afile.ext

You don't need a slash after the wildcard, and if you use forward slashes only it will work on all systems. Don't know about the lopp player though.

yeah that might work for you but as I say its at the very least unreliable for me, it might be cases of paths without {PROJECT_FOLDER} in them

@Christoph-Hart said in How do I get the pixel data under the mouse cursor?:

@Orvillain I could add a wrapper to Path.contains(), then you can at least create shapes with hit zones using paths and test the hover state with the mouse positions, this relieves you from the burden of weird geometry and a JSON file.

Hey Christoph, that sounds like it would be very useful.

@aaronventure No idea tbh!!

@Orvillain good PSA, thanks!

@Orvillain @aaronventure Good points.

I've reached through the archives. This one -

Phase-aligns two IRs in real-time (guitar chains). Morphs in real-time between those two IRs. (guitar chains). Employs non-linear IRs ( guitar modelling). Print new IRs (linear) of the plugin's current state.

As I recall, the phase alignment made a big difference. I can try to dig this one up some more if that's helpful, but it's not HISE. Here's an early build that shows the IR designer, and some other IR-related stuff.

2b60b223-e357-4e85-8a3b-baea75661952-image.png

This one began wrapping the low-level controls into meta-controls.

43ce3ee5-bd8c-4b5b-a50b-2695cf88dea6-image.png

If you'd like any information on any of this, pls let me know.