@whoopsydoodle said in Mono to Stereo in 2025:

Is there some other aspect that could be stopping it from being allowed on a mono track?

Well I think there must be...

But I don't know what it is. I think you'll need to start with the test project and build it out until it doesn't work. Or try and figure out what is different between your project and the test project - start with project preferences and make sure they are identical.

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

smacks wrist

@Chazrox Thank you, i will looking into this.

@d-healey thanks.

@Orvillain

Global cable only allows you to send one value.
Search for my posts on the forum about c++ nodes with global cable to see.

I don't think you can send an array via GC, but maybe I'm wrong

@orange said in DAW crashes when re-inserting the plugin:

you had a method to debug the exported plugin using broadcaster.

I don't recall that. It's possible to debug it running in Reaper (or another daw) though through Visual Studio, and I assume it's also possible with xcode.

@mehmethand Have you tested with an empty test plugin?

@Sampletekk 👍

@Orvillain @d-healey Thank you, again (and @d-healey). All set.

Oddly enough, with this envelope, 1ms on the Attack is actually 0ms on the attack. And…you can't set it to zero.

065dd025-a2fb-49ef-8269-183c425f3250-Screenshot 2025-03-22 at 7.55.57 pm.png Screenshot 2025-03-22 at 7.55.57 pm

@griffinboy said in Get Modwheel value? (Callback):

if(Message.getControllerNumber() == 128) // Pitchwheel

There's also a constant for this Message.PITCH_BEND_CC

@d-healey

Lol, thanks. I'm definitely still not used to it!

@d-healey 😮 Well, this seems to be a dangerous approach.Thanks for the reminder

@d-healey Thank you for your detailed response!

I understand that since I started development relatively recently, releasing a VST2 plugin doesn’t apply to me.

To resolve this, I should release my plugin as VST3 and obtain Steinberg’s VST3 license, which is required as a standard step.

Regarding the macOS installer, I learned that an Apple Developer Account is required. However, upon looking into it, I initially thought it was only available for corporations, but now I understand that as an individual plugin developer, I can’t do that part.

Thank you for clarifying!

While developing, I’ve come to realize that every plugin involves a tremendous amount of hard work and dedication.
I’ve also become incredibly aware of how terrifying it is that there are so many people out there who hack programs, :)

@griffinboy I digress.

@d-healey brilliant thank you!

@HISEnberg said in How to optimize Scriptnode Networks?:

How to measure the latency introduced by my Scriptnode network? I imagine driving an impulse through the plugin and recording the output should reveal this (for a DAW specific context). Is this something Plugin Doctor can measure, or does someone have a better methodology?

You can do a Null test in your DAW for this.

One channel will be the dry (unprocessed) signal. The other channel will be the processed signal, that is, the channel where the plugin is.

Make one channel phase invert. If these two channels are identical, the overall result will be silence. Since there is a delay at the sample level in the channel where the plugin is, determine the amount of sample delay required until the result of the combination of these two channels is silence with a sample delay in the dry channel.

The amount of delay you will apply to silence the sound in the dry channel is the amount of delay created by your plugin's DSP.

How to compensate for latency introduced by the Scriptnode network? I see in the API Engine.setLatencySamples, but it is unclear to me what it does. Are we meant to measure the latency of the scriptnode network (for example 32 samples) and this function will broadcast to the host the latency introduced by the plugin (i.e. "this plugin introduces 32 samples of latency, so compensate for that")? What does the host actually do with this information?

If your plugin has a delay of 32 samples, the DAW will play your plugin 32 samples ahead, thus compensating for the delay. Therefore, it is necessary to inform the DAW of this delay value with Engine.setLatencySamples.

@d-healey Thank you! Makes sense, guess I can hardcode the parameter values.

@d-healey You MADMAN—five Monkeys awarded to thee! 🐒🐒🐒🐒🐒

Like Sir David wrote, you need to resize a panel—any panel—and the whole interface will scale, accordingly. Here's code you can cut and paste:

https://forum.hise.audio/topic/6737/feature-request-gui-scaling-with-window-handle/9?_=1670916351897

Important: Only the compiled version will resize—and if you think about it, that makes sense, because you can already resize within the HISE IDE.

@Christoph-Hart Thank you very much,.

@Matt_SF @Morphoice I've been working with Hise for about two years now and never knew how to move around the GUI. Until I found this, this changed my life haha